Blog

Interface Migration projects shouldn’t be disruptive

By margo.ellis@caristix.com | Published: January 7th, 2015

interface migration projects disruption
If you’re selecting a new interface engine, you know you’re in for some pain as the team migrates interfaces from the legacy engine to the new one. But with the right planning and the right interface migration tools, you can minimize disruption and ensure a smooth transition during interface migration projects.

Reducing migration cycle time

That being said, what if we told you that you can cut 90% of the time it takes to code the schema you’re migrating? Or reduce the time it takes to validate the new interface by 66%?

How believable would that be? You’d be right to be skeptical. But that’s exactly what this post explores.  And those are the real results our customers experience when they include Caristix technology in their migration ecosystem.

How to reduce disruption

Let’s start with the typical engine and interface migration process:

  • Start by manually determining and documenting the interface requirements.
  • Include any and all customizations to the vendor spec
  • Build the interface, usually through trial and error
  • Manually validate and test the new interface
  • Move into production

Because this process relies on eyeballing messages and counting pipes, it sticks your team with risk and rework – and disruption.

This is the kind of disruption that means downtime, extended go-lives, and drawn-out testing cycles. So integration managers and leadership get stuck with rising costs for contractors and outsourcing, so they have to trade off budget overruns against the risk of glitch-ridden, fragile interfaces.

But with the right technology in place, you can transform this process so you eliminate disruption and ensure a smooth transition, at a lower cost.

Our customers – including large IDNs – have seen significant reductions in time and cost during migration projects, including the numbers we mentioned above.

Migration workflows

The most effective migration teams don’t stick with the manual workflow described above. They work on incorporating interface management software (such as Workgroup and connectors from Caristix) in order to reduce risk and disruption. We’re now sharing their high-level processes as a series of brief migration workflows for the most common interface engines, including Sun eGate, Orion Rhapsody, Intersystems Ensemble, iNTERFACEWARE Iguana, Mirth Connect, and Microsoft BizTalk.

Contact us to learn more about these migration workflows and ask for our upcoming Migration One-pagers. They’ll walk you through the process of delivering migration projects faster and at lower cost.

Categories : Migration/Conversion