Skip to main content
Migrate moves healthcare data between systems via FHIR R4 Bulk Data Access (NDJSON per the HL7 IG): export from a source EHR, convert, and load into a successor system. It is built for migration projects, not synthetic data; if you need test populations, that’s Flock. Migrate requires a Pidgeon account sign-in.

​
Before you start

  • Install Migrate (or on macOS) and sign in.
  • You can walk the whole loop against a sample source first. Real source credentials are optional until you’re ready.

​
One loop: preflight, export, reconcile

1

Configure a migration

From the first-run screen, choose Configure a migration. The Dashboard is the working surface: source connection, destination, and output directory.
2

Pass the preflight

The Dashboard shows a preflight checklist before anything runs: engine round-trip validation, source connection test, and output directory selection. A migration does not start until preflight is green. Failures appear as named blockers, not crashes.
3

Run the export

Start the export. Progress streams into the Migration Log dock at the bottom of the window. Optionally enable de-identification so the exported set carries no direct identifiers.
4

Reconcile

When the run completes, review the reconciliation output: resource counts per type on the source side versus the exported set, so you can prove nothing was dropped.
5

Resume if interrupted

If a run is interrupted (machine sleep, network drop), Migrate detects the checkpoint on next launch and offers to resume from where it stopped instead of starting over.

​
When something fails

​
Next steps

  • CLI quickstart
  • Sidebar entries marked Soon (Export Wizard, Mappings, History) are not active in this beta; the Dashboard runs the full loop above.