Chartferry

Upgrade or Fork Migration

Move the estate without a lift-and-pray export

Once the path is chosen, the work is the same shape either way: rebuild the platform, move the channels, prove they behave the same, and cut over with a way back.

The two paths

  • Upgrade to a supported commercial Mirth Connect release. For estates that have decided to buy the license, we take frozen 3.x and 4.x environments forward, deal with the Java runtime and database changes along the way, and retire the deprecated behaviour your channels depend on.
  • Migrate to an open fork. For estates that have decided not to buy, we move channels to Open Integration Engine or BridgeLink. We check every extension, connector and script your channels rely on against the target before committing to a date, because a channel export that imports cleanly is not the same thing as a channel that behaves the same.

How we migrate

  1. Freeze and capture. Export channels, code templates, global scripts and configuration from source control or the running server, and capture a representative message set per channel from production message storage, with PHI handled under your BAA and access rules.
  2. Rebuild the environment. New servers, the backing database, Java runtime, TLS material, deployment scripts and backups, built so they can be rebuilt again.
  3. Clean up the code. Refactor JavaScript transformers and code templates where they rely on behaviour that changed, and remove dead channels you no longer need to carry.
  4. Parity test channel by channel. Replay the captured messages through old and new, diff the encoded output, ACKs, destination writes and errors, and keep the harness for regression testing afterwards.
  5. Cut over with a rollback plan. A written runbook per interface or group of interfaces, partner notifications where endpoints change, and a rehearsed path back to the old engine.

What you get

Migrated channels in source control, a reusable regression harness, the runbooks, and an estate that the next upgrade does not have to rediscover.

Chartferry is independent. We are not affiliated with, endorsed by, or a reseller of NextGen Healthcare, and we use the name Mirth Connect only to describe the product we work on.

Tell us what your Mirth Connect estate looks like and what decision is in front of you. A senior engineer replies, not a sales desk.
Talk to an engineer