The decision that determines whether an EHR switch goes well is made before you sign with the new vendor: it is whether you can get your data out of the old one, in what format, at what cost, and on whose schedule. Everything else — training, templates, go-live — is work you control. Data extraction is work your outgoing vendor controls, and they have no commercial incentive to make it pleasant. Plan the exit first.
Start With the Contract, Not the Demo
Before you take a single sales call, pull your current agreement and find the answers to these questions. Write them down. They will shape your budget and your timeline more than any feature comparison.
- Termination and notice. How much notice must you give, and does the contract auto-renew if you miss a window? A missed notice date can cost you a full renewal term.
- Data extraction rights. Does the contract obligate the vendor to provide your data on exit? In what format? Structured, or a pile of PDFs?
- Extraction fees. Is there a charge, and is it capped? An uncapped extraction fee discovered late is enormous leverage for the vendor.
- Post-termination access. How long can you still read the system after you stop paying? This matters enormously if you plan to keep the legacy system as your archive.
- Hosting and custody. If the vendor hosts, where is the database and who can produce a copy of it?
If the answers are bad, you have not lost — you have found out early, and you can price the exit into your business case instead of being ambushed by it in month four.
What Data You Can Actually Take
Expect three tiers, and plan for each separately.
| Tier | What it is | How it usually moves |
|---|---|---|
| Structured, discrete data | Demographics, problems, medications, allergies, immunizations, results, vitals | Maps cleanly into the new EHR. This is the data worth paying to migrate. |
| Semi-structured | Encounter notes, orders, historical documents | Often lands as text or PDF documents attached to the chart — searchable at best, browsable at worst. |
| System-specific | Templates, order sets, macros, rules, letter templates, custom reports | Does not migrate. You are rebuilding it. Budget the staff time. |
The third row is where switching projects break their budgets. Practices assume their configuration comes with them, and it does not — every template and order set is written in the outgoing vendor's dialect. Treat the rebuild as a first-class workstream with named owners, and use it as an opportunity to retire the templates nobody actually uses.
Certified EHR technology is subject to ONC's certification criteria, which include capabilities intended to let a practice export electronic health information in a computable format. Ask your outgoing vendor, in writing, which certified export capability they will use, and get a sample export early — not on the week of the cutover — so you can see what you are actually receiving before your migration plan depends on it.
Where Information Blocking Fits
The 21st Century Cures Act's information blocking regulations prohibit practices that unreasonably interfere with the access, exchange, or use of electronic health information, and certified health IT developers are among the actors subject to them. That does not mean an outgoing vendor must migrate your data for free, and it does not make every fee or delay a violation — exceptions exist, including ones that permit recovering reasonable costs. But it does mean that a vendor stonewalling a legitimate request for a patient's electronic health information is operating in a regulated space, and it changes the tone of the conversation. Know the rules before you escalate, cite them accurately, and put your requests in writing.
Decide What Migrates and What Gets Archived
The instinct is to migrate everything. Resist it. Every additional data class multiplies mapping work, validation work, and the risk of a subtle error propagating into the live chart — and a chart full of badly-mapped historical junk is worse for clinicians than a clean chart with an archive link.
- Define the clinical minimum. What must be in the new chart for a provider to safely see a patient on day one? Typically: demographics, active problems, current medications, allergies, immunizations, recent results, and a defined lookback of notes.
- Set a lookback window for encounters and results, and get clinical leadership to sign it. Two years is common; the right answer depends on your specialty.
- Archive the rest, in a form you can search and produce on request. Everything you archive instead of migrate is time and money you get back.
- Validate against a real sample. Pick a set of complex patients and reconcile their charts field by field, old system to new. Do it twice: once on the test load, once after the production load.
- Freeze and cut. Define exactly when the old system becomes read-only, and what happens to anything documented during the gap.
A Realistic Sequence
- Contract review and exit analysis. Know your notice date and extraction terms first.
- Requirements and shortlist. Define what is actually broken about the current system, so you do not buy the same problem in a new skin.
- Sample extract from the outgoing vendor. Do this during selection, not after.
- Contract with the new vendor, with migration scope, validation criteria, and acceptance testing written into the agreement — not left to a project manager's goodwill.
- Build and rebuild. Configuration, templates, order sets, interfaces, and the billing connection.
- Test migration, validate, fix mappings, repeat. Plan for at least two full test loads. One is never enough.
- Train, then go live with a reduced schedule and extra support on the floor.
- Reconcile revenue cycle for the first several weeks. Claims are where a botched switch shows up in the bank account.
What to Do With the Old System
You cannot simply turn it off. HIPAA requires covered entities to retain required documentation for six years from creation or from the date it was last in effect, and state law — not HIPAA — generally governs how long you must keep the medical record itself, with longer periods common for minors. Decide deliberately between two options: keep the legacy system running in read-only mode (simple, but you keep paying, patching, and securing it), or export to a dedicated archive (cheaper to hold, but you must prove you can search it and produce records on request).
Whichever you choose, the legacy system remains in scope for your HIPAA risk analysis for as long as it holds ePHI. An unpatched, unmonitored server that everyone forgot about because "we moved to the new EHR" is a genuinely common breach story. Put its decommissioning date on a calendar, with a named owner and a documented media-sanitization step.
When Not to Switch
Switching is expensive, disruptive, and occasionally the wrong answer. Before you commit, be honest about whether the pain is the product or the implementation. Poorly built templates, bad training, an unconfigured inbox, and a broken billing interface all feel exactly like "our EHR is terrible" — and all of them will follow you to the next vendor if you have not diagnosed them. Optimizing what you have is dramatically cheaper than replacing it. Replace when the product genuinely cannot do what your practice needs, when the vendor's certification status or roadmap puts you at risk, or when the relationship has failed beyond repair. Those are good reasons. "Everyone hates it" is a symptom, not a diagnosis.
Common questions
Can my old EHR vendor refuse to give me my data?
Your contract governs what they owe you and at what cost, so read it before you give notice. Separately, certified health IT developers are subject to the information blocking regulations, which prohibit unreasonable interference with access, exchange, or use of electronic health information — though exceptions exist, including recovery of reasonable costs.
How much of the chart should we actually migrate?
Migrate the discrete clinical minimum — demographics, problems, medications, allergies, immunizations, recent results, and a defined lookback of notes — and archive the rest. Every extra data class adds mapping and validation risk for diminishing clinical value.
Do templates and order sets transfer to the new EHR?
No. Configuration is vendor-specific and you will rebuild it. Budget it as a real workstream with named owners, and use the rebuild to retire the templates nobody uses.
Can we shut down the old system after go-live?
Not immediately. HIPAA requires six-year retention of required documentation, and state law governs medical record retention itself. Either keep the legacy system read-only or move to a dedicated archive — and keep it in your risk analysis until it is properly decommissioned and sanitized.