Skip to content

Browse the knowledge base

Importing Mirth channels

Using the import wizard on Mirth Connect channel XML, what maps automatically, and what to review before you promote.

Last updated August 12, 2026

On this page

The import wizard reads Mirth Connect channel XML and rebuilds each channel as an editable intu-dev project. The result is a visual pipeline you can change, not a read-only conversion report.

Getting the XML

Export the channel from Mirth Connect Administrator as XML. You can export channels individually or in a group; the wizard accepts either.

Running the import

In the app, open a workspace and start the Mirth import from the onboarding wizard or from the project import action. Upload the XML and review the summary before confirming.

The engine CLI equivalent is:

intu import mirth ./channels/adt-inbound.xml

which is the better route for a bulk migration you want to script and re-run.

What maps automatically

  • Source connector — type, port, framing mode and the common connector settings.
  • Destinations — each Mirth destination becomes an intu-dev destination with its own hooks.
  • Filters and transformers — the stage structure maps onto the intu-dev pipeline, with Mirth’s filter and transformer steps landing in the corresponding stages.
  • Channel metadata — name, description and enabled state.

What to review after import

Import gets you the structure. These are the things worth reading line by line before you promote anything:

JavaScript that relied on Rhino specifics. Mirth transformers run on Rhino (ES5). Anything depending on Rhino’s Java interop, or on ES5-only behaviour, needs attention. See Rhino JavaScript to TypeScript.

Channel-to-channel handoffs. If channels chained to each other, check how those edges landed. The channel connector is engine-supported but not yet exposed in the IntuCloud beta.

Global scripts and code templates. Shared code needs a home in the new project rather than being duplicated into every channel.

Database and file connector credentials. Secrets do not travel in the XML. Recreate them as secret references.

Connector types not yet in the cloud beta. If the channel uses a database reader, a file poller or a DICOM listener, it will import, but running it in IntuCloud will have to wait for cloud exposure — or run it on self-hosted intu-dev. See Connector overview.

Test before cutover

Run the imported channel in the sandbox against captured samples from the live Mirth channel and compare outputs. This is the step that makes a migration boring, which is what you want.