Copergrine
Get Started

EMR Switching Guide

EMR migration checklist

Switching EMRs is mostly a data and billing-continuity problem, not a software problem. This vendor-neutral checklist walks the five phases — and flags the steps where practices most often lose data or open a revenue gap.

1. Plan (4–8 weeks out)

  • Name an internal owner and a clinical champion; align on a realistic go-live date (avoid month-end and your busiest season).
  • Sign the BAA and confirm the new vendor's data-migration scope in writing — what they migrate vs. what you export yourself.
  • Inventory your current data: patients, active problems/medications/allergies, documents, schedules, open orders, and accounts receivable.
  • Pull a clean export from the legacy system (or confirm API/database access) and document field mappings to the new schema.
  • Decide your historical-data strategy: full chart migration vs. migrate active patients + read-only archive of the rest.

2. Migrate data

  • Migrate structured data first: demographics, insurance/payers, problem list, medications, allergies, immunizations.
  • Migrate scheduling so day-one appointments exist; migrate open/active orders and care plans (485s for home health).
  • Bring over AR and open claims so billing continuity is preserved — a revenue gap at go-live is the most expensive mistake.
  • Attach documents/PDFs to the correct charts; confirm encoding and that nothing is truncated.
  • Run the migration into a staging/sandbox tenant first, never straight into production.

3. Validate (before go-live)

  • Reconcile record counts: patients in = patients out; medications, allergies, and documents tie to source totals.
  • Spot-check 20–30 charts across visit types for fidelity — active meds, allergies, and recent notes especially.
  • Verify e-prescribing, eligibility checks, and the clearinghouse connection in the sandbox with test transactions.
  • Confirm payer enrollments and EDI (837/835) are active for the new system — these often have lead times.
  • For home health: validate OASIS export to iQIES and PDGM grouping on sample episodes.

4. Train & prepare go-live

  • Role-based training (providers, nursing, front desk, billing) on real workflows, not a generic demo.
  • Write a one-page day-one quick-reference for each role; identify super-users for floor support.
  • Plan a parallel period or a clean cutover date; keep the legacy system read-only for a defined window.
  • Document a rollback plan and the exact conditions that would trigger it.

5. Go-live & the first billing cycle

  • Lighten the schedule for the first 2–3 days; staff extra support hours.
  • Submit a small first claim batch and watch acceptance/277CA before scaling up.
  • Monitor the first full billing cycle daily: rejections, denials, days-in-AR, and any payer enrollment gaps.
  • Hold a 2-week retro; clean up data issues surfaced in real use before closing out the legacy system.

Copergrine handles the migration scope with you — structured data, schedules, documents, and AR — into a sandbox first, with reconciliation before go-live. See the Copergrine EMR or, for agencies, the Home Health & Therapy EMR.

Book a migration walkthrough →Estimate your savings →

Frequently asked questions

How long does an EMR migration take?

For a small-to-midsize practice, plan on roughly 4 to 8 weeks from kickoff to go-live: a couple of weeks of planning and data mapping, one to two weeks of migration into a sandbox plus validation, and a training-and-cutover window. Home-health agencies and multi-location groups usually need longer because of payer enrollments, OASIS/PDGM validation, and larger historical data sets.

What data should I migrate to a new EMR?

At minimum: patient demographics and insurance, the active problem list, current medications, allergies, immunizations, upcoming schedules, open orders and care plans, and your accounts receivable / open claims. Documents and historical notes can either be fully migrated or kept in a read-only archive of the legacy system, depending on cost and how often older records are needed.

How do I avoid a revenue gap when switching EMRs?

Migrate accounts receivable and open claims, confirm payer EDI enrollments (837/835) are active in the new system before go-live, submit a small first claim batch and verify acceptance before scaling, and monitor the first full billing cycle daily. A revenue gap almost always traces to claims continuity or payer enrollment being treated as an afterthought.

Should I run the old and new EMR in parallel?

Keep the legacy system available read-only for a defined window (commonly 30–90 days) so staff can reference historical records, and consider a short parallel period for billing continuity. A true full parallel run — double-charting in both systems — is rarely worth the staff burden; a clean cutover with a read-only archive is usually the better tradeoff.