Planning a Mirth Connect to OIE migration

Inventory more than the channels

Before choosing a cutover date, create an inventory that another engineer could use to rebuild the environment. Our recommended starting point is:

• Channel exports, shared code templates, and configuration maps.
• Engine and Java versions, database version, installed extensions, and external libraries.
• Certificates, secret locations, firewall rules, endpoint owners, and scheduled jobs.
• Message volumes, queue sizes, retention rules, and the interfaces most sensitive to delays.

Rehearse with representative messages

Use an isolated target environment and approved test data. Compare routing, transformations, acknowledgments, and downstream results. Include rejected messages, unavailable destinations, duplicate inputs, and restart recovery. A channel that imports successfully still needs behavior testing. Prevent test traffic from reaching production endpoints or generating duplicate clinical or billing actions.

Define the cutover and rollback

Agree who pauses senders, drains queues, switches endpoints, and confirms delivery. Decide how you will reconcile messages created during the transition. Document a rollback trigger, an owner, and how queued traffic will be handled. Test recovery before scheduling the production move.

Make support part of the handoff

The final handoff should include tested backups, an interface inventory, escalation contacts, and a runbook for common failures. Define what to monitor after launch and who can approve a replay or configuration change. Ask your implementation team to document any assumptions that remain untested.