Migrating from a legacy interface engine
Move interfaces to MessageFoundry one at a time. Translate the configuration, compare results, and keep a rollback path at each cutover. For Mirth Connect, see the migration notes.
Keep the existing engine running while you test each replacement interface. Start in a sandbox and read the Early Access limits before planning a cutover.
1. Inventory your interfaces
Record each channel’s connections, routing rules, transforms, filters, and message volumes. Use the inventory to identify high-risk interfaces.
2. Re-express each interface as Python
Map each channel to inbound and outbound Connections, a Router, and Handlers. Keep the Python in a configuration repository. Optional AI assistance can draft code for review.
3. Validate and shadow
Run the commit gate: python -m messagefoundry check. Run the new interface in parallel with the legacy engine against live traffic and compare outputs. Keep it out of production routing until the results match.
Rehearse the parallel run with the tee relay
The tee relay is a validation tool for test or synthetic feeds only. It is not hardened to carry production PHI. It sits in front of the legacy engine and forwards each message to it unchanged. It then sends a copy to a shadow MessageFoundry instance that delivers nothing.
Dashed arrows are MLLP hops between systems. Solid arrows stay inside the relay.
4. Cut over with rollback
Move one interface at a time, using go/no-go checks at each stage. Keep the legacy engine as a fallback until each interface is trusted. The Adoption & rollout guide covers rollout stages. The Migration guide covers each interface’s migration.
MessageFoundry is open source and self-hosted, with no per-interface license fees. Keep interfaces as Python code you can review and test. See the comparison →
Related guides
Frequently asked questions
Can I migrate to MessageFoundry from Mirth Connect, Corepoint, or Rhapsody?
Yes. Translate each channel’s connections, routing, and transforms into Python configuration. Migrate one interface at a time, with tests and a rollback plan.
Will I have to rewrite my interfaces?
Rewrite each interface as Python Connections, Routers, and Handlers. Keep the code in version control and test it. Optional AI assistance can draft code from existing channel logic for your team to review.
How do I de-risk the cutover?
Validate the configuration, then compare outputs while the new interface runs alongside the old one. Use go/no-go checks for each cutover stage. Keep the legacy engine as a fallback until each interface is trusted.
Can I migrate from Infor Cloverleaf?
Yes. Translate Cloverleaf’s Tcl interface logic into Python. Migrate one interface at a time and validate each against live traffic before cutover. MessageFoundry has no per-interface license fees.
Can I migrate from InterSystems Ensemble or Health Connect?
Yes. Translate the interface logic into Python and use MessageFoundry’s supported databases. Migrate in stages and keep the legacy engine as a fallback. Check your current vendor maintenance terms when planning the schedule.