United States
Planning a Dental EHR Migration
Migrating a clinical record is not the same project as migrating a schedule and a ledger, even when they travel together. The clinical chart is a legal record with retention obligations, a safety instrument whose gaps can affect care, and the hardest data in dentistry to move with fidelity. The framework here — scope, validation, clinical sign-off, governance — exists because "the vendor handles the conversion" is a sentence that has preceded a great many quiet disasters.
Why clinical data raises the stakes
Three properties make the clinical record different from every other dataset in the practice. It is a legal record: notes, consents, and prescriptions carry authorship and timestamps that must survive the move, because a note whose signature or date was mangled in conversion is a weakened document exactly when it matters. It is a safety instrument: allergies, alerts, and medical histories that fail to surface in the new system are not missing rows — they are missing warnings. And it is structurally fragile: the odontogram and perio charting are stored in vendor-specific representations, so the fidelity of any migration depends on the specific source-target pair, not on either product's general quality. Ledger history that arrives summarized is an inconvenience; charting that arrives as flattened images is a permanent loss of clinical usability.
Ask the receiving vendor, in writing: "For a migration from [our exact system and version], which objects arrive as structured data, which as documents, and which not at all?" The answer varies by system pair and sets every downstream decision. A vendor who answers generically has not done this pair before — which is itself information.
The fidelity decision, object by object
For each clinical data object there are three legitimate destinies: structured migration (the data lives natively in the new system), document migration (content survives as retrievable files or text attached to the right patient), and read-only archive (the data stays in the legacy system or an export, consulted when needed). Cost and risk rise steeply with structure, so the mature question is not "can it migrate?" but "what fidelity does this object need to serve care, defensibility, and retention?"
| Clinical object | Typical reality | Minimum fidelity worth insisting on | Verify in sandbox |
|---|---|---|---|
| Medical history, allergies, alerts | Migrates, but alert flags map imperfectly | Structured — these must fire at point of care | Alerts actually trigger in new-system workflows |
| Clinical notes | Content survives; structure and formatting often flatten | Retrievable per patient with author and date intact | Sample notes against legacy: content, authorship, timestamps |
| Odontogram / restorative charting | Highly pair-dependent: structured, image, or absent | Honest answer up front; document-level at minimum | Charted teeth match legacy for sampled patients |
| Perio charting | Frequently the first casualty — history arrives flat or not at all | Recent exams structured if the pair supports it; else archived and retrievable | Depth values by site and date for sampled patients |
| Treatment plans (open) | Migrates with procedure-mapping errors | Structured — open plans drive scheduling and finance | Plan contents, phasing, and fees against legacy |
| Consents & signed documents | Transfers as documents; linkage is the risk | Exact copies attached to the correct patient | Sampled documents open and match the right chart |
| Prescription history | Varies; e-prescribing systems may hold it separately | Retrievable history per patient | Sampled patients' med lists match |
| Imaging | Often stays in the imaging system; linkage re-pointed | Standard formats, dates, and patient linkage preserved | Images open from the new chart for sampled patients |
Validation is clinician work, with a signature at the end
Administrative staff can reconcile counts and balances; only a clinician can look at a migrated chart and judge whether it still tells the truth. Clinical validation therefore has two layers — statistical reconciliation across the whole dataset, and chart-level review of a deliberate sample by people qualified to notice what is subtly wrong. It ends with a named clinical owner signing that the migrated record is fit to treat from. That signature is not ceremony; it is the moment the practice, rather than the vendor, accepts the record.
- Reconcile the population firstPatient counts, note counts per year, document counts, and alert counts, sandbox versus legacy. Population-level gaps — a missing year of notes, a class of documents that didn't transfer — surface here in minutes, before anyone burns hours reading individual charts.
- Build a deliberate chart sampleNot random alone: include complex medical histories, heavy perio patients, long multi-phase treatment plans, pediatric and family-linked records, hyphenated and changed names, and a few charts the clinicians know intimately. Edge cases are where conversions fail; sample where failure is likely and where it would matter most.
- Review each sampled chart against legacy, side by sideFor each: allergies and alerts present and firing, notes complete with author and date, charting accurate tooth by tooth, open plans intact, documents attached to the right person. Log every discrepancy with a screenshot — the reconversion argument goes better with evidence.
- Fix, reconvert, and re-sampleDiscrepancies go back to the vendor as a batch; the corrected conversion gets a fresh sample, not a re-check of the same charts. Two or three loops are normal. This loop is the schedule's honest critical path — compress it and the errors ship to production.
- Close with a written clinical sign-offA named dentist attests the record is fit to treat from, listing known limitations ("perio history pre-2022 is archive-only") so they are documented decisions rather than future surprises. Cutover waits for this signature.
Governance: the legacy record's long tail
Go-live ends the project but not the obligations. Records-retention requirements for dental charts vary by state and by patient circumstance — minors' records commonly carry longer clocks — so the fate of the legacy system is a compliance decision, not a licensing afterthought: verify your retention obligations with qualified counsel and let the archive plan follow. Practically, that plan usually takes one of three shapes: the legacy system kept alive in read-only mode (complete, but a perpetual license and an aging server); a full export to a documented archive format (cheaper, but verify completeness before the legacy license lapses — after is too late); or a hosted archive service holding the legacy database. Whichever you choose, the archive inherits security obligations too: it holds the same patient data the live system did, and an unpatched forgotten server with fifteen years of charts is a breach waiting for a scan.
The governance close-out list
- Retention periods confirmed with qualified counsel for your state, including minors and any special categories
- Archive mechanism chosen and, if export-based, verified complete while the legacy system still runs
- Read-only access documented: who can retrieve a legacy record, how, and how quickly — records requests will not wait
- Archive security handled: access controls, patching or isolation, backup, and inclusion in your risk analysis
- Migration limitations from the clinical sign-off filed where future clinicians and auditors will find them
- A calendar entry, years out, to revisit the archive before its platform or media quietly rots
Frequently asked questions
Do clinical notes migrate between dental EHR systems?
Content usually survives; structure often does not. Notes commonly arrive as text or documents with formatting flattened — acceptable if authorship, dates, and completeness are verified, which is exactly what chart-level sampling is for. The subtler risk is metadata: a note whose author or timestamp was mangled in conversion is a weakened legal document, so those two fields belong in every validation check.
Will our perio charting history transfer to a new EHR?
This is the migration's most frequent casualty, because perio data is stored in vendor-specific structures that rarely map cleanly. Outcomes range from full structured transfer to flattened printouts to nothing, depending on the specific system pair. Get the pair-specific answer in writing, verify it in the sandbox with real patients' depth values, and if structured history cannot move, ensure it is retrievable from the archive — trending across the migration boundary is often what you are really deciding about.
Who should sign off that a clinical data migration is acceptable?
A named dentist — not the office manager, not the vendor's project manager. Administrative staff validate counts, balances, and schedules; judging whether a migrated chart still tells the clinical truth requires clinical eyes. The sign-off should be written, should list known limitations of the conversion, and should be a genuine gate: cutover waits for it, and the vendor knows it.
How long do we have to keep records from our old EHR?
There is no single national answer: retention periods for dental records are set primarily by state rules and vary meaningfully, with longer clocks common for minors and other special situations, and other obligations sometimes extending them further. Establish your specific periods with qualified counsel, then design the archive to outlast the longest of them — and verify the archive's completeness while the legacy system still runs, because afterward there is no way to check.
Can we just keep the old system running instead of migrating clinical data?
Partially, and sometimes wisely — a common pattern migrates operational data (demographics, balances, future appointments) while clinical history stays in a read-only legacy archive consulted as needed. It reduces conversion risk and cost at a real price: clinicians work across two systems, cross-migration trending is manual, and the legacy platform must stay secure and readable for your entire retention period. It is a legitimate scope decision when made deliberately — and a trap when it is simply what happened.
Related on Dental EHR
How we handle this information
We keep material limitations visible, separate advertising from editorial judgment, and avoid inventing live scores or recommendations when the underlying evidence is not available.
Related in this network
Related properties may share common ownership. A cross-property link is not an endorsement — see our ownership disclosures.