1. Your records may already be free to export
Before you accept a quote to extract your own data: check whether your current system is a certified EHR.
Under the 21st Century Cures Act, certified electronic health record technology must provide a way to export electronic health information — for a single patient and for the whole patient population — without special effort, and information blocking rules restrict a vendor from making that unreasonably difficult or expensive. If your vendor is certified and is quoting five figures to hand back records you already own, that is worth challenging in writing before you pay it.
Not every clinic system is certified. Plenty of practice-management products used in cash-pay medicine never sought certification, and some withdrew from the programme. Those vendors are not bound by the same requirement — but they usually still have a documented export path, and their own help articles are the fastest place to find it.
Either way, ask two questions in writing: what does a full export contain, and what does it cost. Getting that in email before you sign anywhere else changes the negotiation entirely.
2. What actually moves, and what quietly does not
Moves cleanly in most migrations: patient demographics, contact details, allergies, problem lists, medication lists with current doses, appointment history, and documents or lab PDFs as files.
Moves badly, or not at all: anything the old system stored as free text rather than structured data. A dose written into a paragraph cannot be trended after the move because it was never data to begin with. Chart notes usually arrive as documents rather than as fields — readable, not searchable.
The one people forget: membership and subscription state. Who is on which programme, what they pay, when they renew, which card is on file, and how many included visits they have left. This is not clinical data, so it is routinely left out of a migration plan — and it is the thing that causes chaos in week one when renewals do not fire and nobody can tell who is active.
Payment tokens are a separate problem again. Cards stored with your old processor generally cannot be handed to a new one directly; processors migrate tokens between themselves, on request, and it takes lead time. Ask about it early or you will be re-collecting card details from every member.
3. The sequence that keeps a clinic running
A migration is not a weekend. The clinics that do this without pain follow roughly the same order.
Request the export from your current vendor first, before you commit to a new one — the answer tells you what is possible and how long it takes. Then have the new vendor map a sample: a few hundred patients, so field mismatches surface while they are cheap to fix. Run both systems in parallel for a short overlap, with the old one read-only, so nothing is being written to a system you are about to leave. Cut over new bookings before you cut over charting. Keep read access to the old system for as long as the contract allows.
Ask what happens to historical charts specifically: do they arrive as structured records you can search and trend, or as a folder of PDFs? That single answer decides whether your history stays useful or becomes an archive you never open.
4. What you are still required to keep
Leaving a vendor does not end your record-keeping obligations. Medical record retention is set by state law and varies widely; prescription records carry their own federal requirements. Your new system holding a copy is what satisfies this — not your old vendor still having one.
That is why the export matters more than the relationship. Verify the records arrived and are readable before the old contract terminates, because a vendor is entitled to stop providing access once the term ends. Confirm receipt in writing, keep the export file itself, and do not rely on being able to log back in.
5. How this works with Aminova
Migration is a supported part of onboarding rather than a service you buy separately. We take an export in whatever format your current vendor produces, map it against a sample first so mismatches surface early, and import demographics, medications with current doses, documents, lab results and membership state — including who renews when, which is the field most migrations drop.
Data portability runs the other direction too. Your data exports in usable formats whenever you ask, for as long as you are a client. A platform should keep clinics by being good, not by making leaving expensive — see how we handle data and security.
6. Frequently asked questions
How long does an EMR migration take?
For a single-location clinic, plan on two to six weeks from requesting the export to running day-to-day on the new system — most of which is waiting on the old vendor and validating the mapping, not the import itself. Multi-location groups take longer, mostly because their membership and billing state is more tangled.
Will I lose my chart notes?
Usually not, but the format changes. Notes typically arrive as documents attached to the right patient rather than as structured fields, so they remain readable and legally sufficient without being searchable or trendable. Structured data — doses, vitals, lab values — is what survives as data, and only if the old system stored it that way.
Can I be charged to get my own patient data out?
If your current vendor is a certified EHR, the Cures Act requires an export capability and information blocking rules restrict making it unreasonably burdensome or costly. If they are not certified, they are not bound by that — but ask for the documented export path anyway, in writing, before you assume the quote is the only option.
What happens to stored payment cards?
They generally do not transfer with the chart data. Card tokens live with your payment processor, and processors migrate them between each other on request rather than handing them to a software vendor. Start that conversation early, or plan to re-collect card details from every active member.