Case study · August 20, 2026 · 3 min read

Migrating a Legacy EMR to Epic With Zero Data Loss

How a Toronto specialty hospital moved a decade of clinical history to Epic without losing a single record

The client was a specialty hospital in Toronto, managing a dozen inpatient beds and a busy outpatient practice for about 3,000 patients.

The challenge

The hospital was running on Bcare, an aging EMR that was reaching the end of the line. It was time to move to Epic. The stakes were high: over a decade of clinical history, including encounters, orders, lab results, scanned documents, and messy free-text notes, had to be migrated.

In healthcare data, there is zero tolerance for lost or misattributed patient records. If a note gets attached to the wrong patient, it’s a massive clinical risk.

The problem? Bcare exported data in a bizarre, proprietary format. Epic, on the other end, expects incoming data to perfectly match its own strict ingestion structure. Usually, a migration of this size and complexity requires a project manager and three or four data engineers.

The approach

We ran the entire migration end-to-end with a single engineer.

The outcome

We successfully carried over every patient record, document, and clinical note, keeping the links to the correct patient and encounter entirely intact. Not a single material data element was lost.

No patient data ever left the hospital’s controlled environment. By engineering a smarter pipeline, the hospital avoided the massive overhead of a multi-engineer team while ensuring absolute continuity of care.

Read the underlying methodology in What Actually Breaks in an EMR Migration.