Migrating interfaces between engines is usually a re-platforming project measured in months. MessageFoundry treats it as a code review instead: an AI coding assistant in your editor reads your existing channel logic and drafts the equivalent Connections, Routers, and Handlers in Python — which you review, test, and promote like any other change. It's code-only by construction and governed by a central policy, so nothing leaves your control.
Legacy engines lock integration logic inside proprietary scripts and GUIs — JavaScript channels, Tcl, ObjectScript, XML buried in a database. Porting it by hand means relearning each system and rebuilding interface by interface.
MessageFoundry's configuration is code, so the assistant can do the mechanical translation for you: paste a legacy channel or open its export, and it drafts the matching inbound / outbound Connections, a @router, and the @handler transforms in Python. You stay in control — every line lands as a diff you read, adjust, and approve.
@router that mirrors your channel's filter and routing rules.@handler functions that reproduce field mappings and reshaping as pure Python.Open or paste an existing channel — a Mirth transformer, a Cloverleaf Tcl proc, a Rhapsody filter. That's source code, so it stays within the assistant's code-only scope.
You get Python Connections, a Router, and Handlers that mirror the original's routing, filtering, and field mapping — wired by name, ready to read.
The draft lands as a diff in your editor and your pull request. Adjust, comment, and approve — the migration is now a normal review, not a black box.
Dry-run synthetic, PHI-free messages through the new route and compare before/after. The headless scenario runner keeps the check green in CI.
Promote the verified route to a running engine. Because each interface is independent code, a team can migrate many channels at once instead of serially.
The assistant carries PHI implications, so it's controlled centrally, not per developer. Whoever operates the install sets a single policy — from fully off to PHI-safe — and every workstation honors it.
Migrating doesn't expose patients. Channel logic is code, and code is all the assistant sends. Your historical messages and live PHI never go to a model during a migration — the work happens entirely on the integration logic.
Open, Python, and AI-assisted — migrate off a legacy engine without a re-platforming project.