Switch to Toro — migrate from any EMR

TIER 1 — DIRECT FHIR MIGRATION

FHIR-to-FHIR. 24–48 hours.

Sources with a public FHIR API. We authorize via OAuth, transfer resource by resource, validate, and you review. Fully automated end-to-end.

Elation Health

FHIR R4

24–48 hrs

TIER 2 — GUIDED MANUAL MIGRATION

Export-based, with a human team. 7–14 days.

Sources without a workable public FHIR API. You initiate an export from your current EMR; our migration team imports, cleans, validates, and walks you through a review.

Hint Health

Manual

7–10 days

Cerbo

Manual

7–10 days

Atlas MD

Manual

10–14 days

Osmind

Manual

10–14 days

SimplePractice

Manual

10–14 days

DrChrono

Manual

10–14 days

Athenahealth

Manual

10–14 days

Practice Better

Manual

10–14 days

Other / not listed

Assess

Talk to us

How it works

Two tracks. Same destination.

FHIR TRACK

Direct migration

24–48 hours · Elation today

Authorize. Sign in to your source EMR through OAuth, grant Switch read access to your data.

Migrate. Switch reads FHIR resources from the source and writes them into your Toro instance, preserving identifiers and references.

Review. We surface a migration report — counts, errors, mapping notes — and walk through it with you. Then you go live.

MANUAL TRACK

Guided migration

7–14 days · all other sources

Export. You initiate a data export from your current EMR (we send specific instructions for your source). Toro receives the export securely.

Toro imports. Our migration team maps source fields to FHIR resources, cleans inconsistencies, and validates against the FHIR spec.

You review. We provide a sample patient walkthrough, fidelity report, and any flagged ambiguities. You approve before go-live.

What gets migrated

The complete patient record, where the source EMR exposes it. Specifically:

Patient demographics — names, identifiers, contact info, insurance, emergency contacts. Full fidelity.
Encounters and visit notes — including SOAP notes, structured vitals, and free-text. Full fidelity for FHIR sources; preserved as DocumentReference for manual sources.
Problem lists and diagnoses — ICD-10 / SNOMED-coded where available. Full fidelity.
Medications — active prescriptions, RxNorm-coded. Full fidelity for FHIR; coded best-effort for manual.
Allergies and intolerances — RxNorm + SNOMED-coded. Full fidelity.
Immunizations — CVX-coded vaccine history. Full fidelity.
Documents — uploaded PDFs, signed forms, scanned records. Preserved as DocumentReference + Binary attachments.
Billing and memberships — recurring subscriptions, member status, payment history (excluding card numbers). Full fidelity for active members.
Appointments — past appointments preserved as Encounters; upcoming appointments rebooked in Toro's scheduler.

Lossy fields depend on source EMR export quality. We document any reductions in the migration report — never silently. If something matters and it didn't come through cleanly, we flag it.

Your data stays yours

Toro is built on a FHIR-native data layer, with a public FHIR API available to your practice from day one. That means: at any point, you can export your data through the same API anyone integrating with Toro uses. There's no proprietary database to escape from. No "data migration consultant" required to leave.

If you ever decide to leave Toro, our migration team helps you go — same process, same care, in reverse. Standards win because they make platform claims testable.

Move your practice without losing your data.

FHIR-to-FHIR. 24–48 hours.

Export-based, with a human team. 7–14 days.

Two tracks. Same destination.

What gets migrated

Your data stays yours

The platform Switch lands you on

Ready to make the move?