Guide
Switching chiropractic EHRs: the checklist from a practice that did it
By Dr. Daniel Turner, DC · Reviewed September 2, 2026
Cervica's founding practice moved three offices off its previous EHR while treating full schedules the whole time. This guide is that experience turned into a checklist: what to demand before you sign anything, how to move the data, and the parallel running strategy that means no revenue gap and no lost history.
Before you sign anything: the exit interview
The switch is won or lost before it starts, in what you get in writing from both vendors. From your current vendor:
- ✓What exports do I get: patient demographics, insurance, balances, appointment history, clinical notes, documents? In what formats, CSV, PDF, or database?
- ✓What does the export cost and how long does it take to deliver?
- ✓How long after cancellation can I still access my data, and is read only access available cheaply?
- ✓What is my contract end date, and what does leaving early cost, exactly?
And from the new vendor, the mirror image: exactly which of those files they import, shown against a sample of your real export, with the result previewed before anything commits. A migration promise without your sample file behind it is a sales line. Any serious vendor will process a sample before you sign. If you are weighing specific vendors, the Cervica vs ChiroTouch and Cervica vs Jane pages cover the switching questions per vendor.
What actually migrates, honestly
| Data | Reality |
|---|---|
| Demographics, phones, emails | Migrates cleanly almost everywhere; the quality issue is duplicates, which a good importer flags rather than doubles |
| Insurance and member IDs | Migrates, but payer matching matters: rows that arrive unlinked to your payer list quietly break claims until someone notices |
| Open balances | Migrates as starting balances; reconcile totals against your old AR reports before trusting them |
| Appointment history | Usually migrates as visit counts and dates |
| Clinical notes | The honest answer: usually arrives as PDF chart exports attached to the patient, not as editable structured notes. Workable, normal, and better than retyping history |
| Claims in flight | Do not migrate these; wind them down in the old system (see parallel running below) |
The parallel running strategy
The single best decision our practice made: do not cut over blind. Pick a cutover date for new dates of service. Everything on or after it lives in the new system; claims for services before it finish their lives in the old system, worked by the same biller in a shrinking queue. For about 60 to 90 days you run two systems on purpose: one growing, one draining. Then reconcile the two against each other, collections, AR, and patient balances, before the old system drops to read only. There is never a day when revenue has no home and never a claim stranded between systems.
The week by week checklist
Weeks 1 and 2: foundations
- ✓Export from the old system; import and preview in the new one
- ✓Build locations, providers, appointment types, fee schedules, and payer list
- ✓Verify payer linkage on migrated insurance, since this is where future claims break
- ✓Start clearinghouse enrollment and ERA redirection now; payer paperwork is the long pole
Weeks 3 and 4: rehearsal
- ✓Train by role with real scenarios: front desk checks in a real patient, biller works a real claim, doctor documents a real visit type
- ✓Schedule two weeks of future appointments in the new system
- ✓Test reminders, intake forms, and the kiosk with staff phones before patients ever see them
- ✓Set the cutover date; tell the whole team the claims rule: date of service decides the system
Cutover week and after
- ✓Go live on a lighter day, not your busiest Monday
- ✓Daily reconciliation for the first week: visits, charges, and payments in both systems sum to the whole practice
- ✓Watch the first ERAs arrive, then review and post them to verify the clearinghouse and ledger workflow
- ✓At 60 to 90 days: old system AR near zero, final reconciliation, drop to read only access
Timing it around your contract
Count backward from your renewal date: most contracts demand notice 30 to 90 days before auto renewal, and the export plus migration takes 30 to 60 days. That means the decision window opens roughly four to five months before renewal. Stuck mid contract? Price the early exit against what the switch earns you monthly; sometimes paying out three months beats a year of the wrong system, and any vendor worth joining will help you plan the timing rather than pressure it.
How Cervica runs migrations
Guided imports with a preview and mapping step before anything commits, a ChiroFusion importer proven on our own three office migration, payer linking during import so migrated insurance can actually bill, and the parallel running playbook above walked with you, because it is the one we used. The setup fee covers humans doing this with you, and we will look at your sample export before you sign anything.
General guidance, not legal advice on any specific vendor contract. Your agreement's terms control; read them before relying on any timeline here.