On this page

Migrate dental records in ten steps: inventory every data source, map fields, clean duplicates, decide what not to move, run a trial load, verify counts and spot-check plans, cut over on a weekend, train staff, keep a rollback plan and sign off in writing. The chart, the open treatment plan and the outstanding balance must arrive on the same patient.
Most dental software migrations lose the same thing: the thread between a patient's chart, their open treatment plan and their balance. A patient arrives for the fourth sitting of a root canal. The new system has the tooth chart and the phone number. The plan is empty and the balance reads zero.
That is not a data loss in the usual sense. Every record arrived. They just arrived in pieces, and the clinic now has to rebuild the story by hand while the patient waits.
What usually goes wrong?
Three failures cover most bad migrations.
The import moves the patient list and stops there. Names, phone numbers and addresses are easy to map. Charts, plans and balances need a person who understands the old system's data model.
The import moves everything and keeps the old mess. Duplicate patients, test entries, three spellings of the same name and a price list from 2019 all arrive in the new system, which is now as hard to search as the old one.
The clinic cuts over without a verification step. The import runs on Friday night and the clinic opens on Monday with no one having checked whether the balances survived.
Which data groups need a decision?
List every group before you talk to a vendor. The table is a starting point, and your clinic will have its own oddities.
Swipe the table to see every column| Data group | What it includes | Move it? | Check |
|---|---|---|---|
| Patients | Name, phone, address, age, referral | Yes | Duplicates and missing numbers |
| Appointments | Past and future bookings | Future yes, past 12 months usually | Double bookings and chair conflicts |
| Charts | Findings, tooth history, periodontal readings | Yes, at least the current state | Missing teeth, quadrant notes |
| Treatment plans | Open and completed courses, prices, stages | Open plans yes, with stages | Plan total equals the sum of items |
| Invoices | Numbers, dates, line items, tax | At least the retention period | Gaps in invoice numbers |
| Payments | Receipts, mode, UPI or card reference | Yes | Sum matches the invoice balance |
| Images | X-rays, photos, scans | Active and recent cases | Every file opens |
| Documents | Consent forms, referrals, letters | Active patients | Scans are readable |
| Lab orders | Open cases, shade, lab name | Open only | Case number and due date |
| Recalls and consent | Next recall date, consent version | Yes | Opt-outs are respected |
A clinic moving off paper has a different problem: there is nothing to import, and the work is data entry. Our guide to paper to digital records covers that route.
The ten steps
1. Inventory every source
Write down where patient data lives today. The main system, a spreadsheet the receptionist keeps, the accountant's billing file, WhatsApp messages with lab work, a folder of scans on the front desk computer. Each source needs an owner and a decision.
2. Map the fields
For each source, list the fields and where they will land in the new system. Phone numbers with and without country codes, dates in two formats, a single name field against separate first and last names, a "balance" field that includes an old discount. Mapping is boring and it prevents most surprises.
3. Clean duplicates before you load
Search for the same patient with two spellings, two phone numbers, a married name and a childhood name. Merge them in the old system, or flag them for the vendor to merge during import. Cleaning 200 duplicates before the load is a day of work. Cleaning them after go-live happens in front of patients.
4. Decide what not to move
Not everything deserves a place in the new system. Old appointment slots, closed complaints, obsolete price lists, internal notes about a staff member and test patients can stay in the archive. Move what a dentist needs to treat the patient and what the clinic needs to bill and defend the record.
5. Run a trial load
Load a copy of the data into a test environment, not the live system. Pick one branch or a few hundred patients. The trial shows what the mapping missed while there is still time to fix it.
6. Verify counts and spot-check
Count the patients, invoices and open plans in both systems. Then check 20 real patients with active plans by hand. Compare the plan total, the amount paid, the balance and the next stage. This sample is the best evidence you will get.
7. Plan the cutover weekend
Pick a weekend when the clinic is closed or quiet. Freeze the old system, run the final import, verify, and decide whether to go live or roll back. Do not run the final import on a Monday morning.
8. Train on the new screens, with real patients
Training on a demo account teaches buttons. Training on ten real patients teaches the workflow. Ask the front desk to book, bill and close a day in the new system before go-live, with the vendor watching.
9. Keep a rollback plan
The old system stays readable for at least 30 days. The old subscription is not cancelled until the new export is verified. If the import fails on Sunday, the clinic opens on Monday on the old system and nobody loses an appointment.
10. Sign off in writing
Both sides sign a short list: counts, sample checks, balances, tomorrow's schedule, images and receipts. The sign-off is the moment the vendor stops being responsible for the old data and the clinic accepts the new record.
Why must the chart, plan and balance travel together?
The chart says what is wrong with the tooth. The plan says what the clinic intends to do and what the patient has agreed to pay. The balance says what is still owed. Separately, each one is misleading.
A chart without the plan loses the clinical intent. A plan without the balance lets a patient pay twice or not at all. A balance without the plan is a number with no treatment behind it, which is hard to explain at the front desk and harder to defend in a dispute.
The practical test is the four-number check on 20 patients:
- The plan total in the old system.
- The amount paid against that plan.
- The outstanding balance.
- The next stage and its date.
If all four match for all 20, the migration kept the thread. If ten match and ten do not, the import needs another pass before go-live. Do not accept "we will fix it after" for balances. Balances are the part patients notice.
What does the cutover weekend look like?
Swipe the table to see every column| When | What happens | Who |
|---|---|---|
| Friday, 6 pm | Final backup, old system set to read-only | Vendor and clinic admin |
| Friday, 8 pm | Import patients, charts, plans and balances | Vendor |
| Saturday, 9 am | Four-number check on 20 patients, fix errors | Front desk lead and dentist |
| Saturday, 2 pm | Import images and documents, open each file type | Vendor and assistant |
| Saturday, 5 pm | Reconcile invoices and payments | Accountant or owner |
| Sunday, 10 am | Staff practise on real patients in the test day | Whole team |
| Sunday, 4 pm | Go or roll back, recorded in writing | Owner and vendor |
| Monday, 9 am | Go live, old system kept for reference | Whole team |
A clinic that cannot spare a weekend should migrate in a quiet week and accept a slower Monday. A clinic that cannot spare either should question whether the switch is worth it this quarter.
What belongs on the sign-off sheet?
- Patient count matches, within an agreed tolerance for duplicates.
- Twenty open plans match on total, paid, balance and next stage.
- Total outstanding matches the old system.
- Tomorrow's appointments appear on the right chairs.
- A sample of images opens on a clinic computer.
- Three receipts print with the correct exempt and taxable lines.
- Every staff member can log in with the right role.
- The support number answers.
- A fresh export is taken after go-live and stored by the clinic.
- The old system stays readable for the retention period.
On retention, the NMC Code of Medical Ethics Regulations, 2002 require indoor patient records for three years from the start of treatment and copies within 72 hours of a request. State rules and medico-legal practice often call for longer. Keep the old system and do not delete it. Put the retention period in a written policy reviewed by a lawyer. Our guide to patient records retention covers the detail. If the move also takes the clinic from a local server to a browser-based system, compare the trade-offs in cloud vs desktop dental software.
Where IvoryCRM fits
IvoryCRM scopes migration before rollout, including how the chart, the open plan and the balance travel together. The switching page describes the process, and the dental clinic software page explains what the record holds after the move.
Before you sign with any vendor, run the ten-point buying checklist. A product that cannot describe its migration in writing will not describe its failures either.
The migration is finished when the dentist can open a patient and see the same story the old system told. Until then, the clinic is running two records and trusting one.
Frequently asked questions
How long does dental software migration take?
A single-branch clinic with clean records can finish in two to four weeks, including a trial load and a weekend cutover. A multi-branch clinic with scanned files, open orthodontic cases and several years of invoices should plan six to ten weeks. The import itself is fast. Cleaning duplicates and checking balances takes the time.
What data should we not migrate?
Old appointment slots, closed complaints, duplicate patient entries, obsolete price lists and internal chat notes rarely earn their place. Move the clinical record, the open plan, the balance and the images that may be needed for care. Keep the old system readable for the retention period instead of importing everything.
How do we check that the migration worked?
Compare counts and then check a sample. Patient totals, invoice totals and outstanding balances should match within rounding. Then open 20 patients with active treatment plans in both systems and compare the plan total, amount paid, balance and next stage. If all 20 match, the import is probably sound.
Can we run the old and new systems at the same time?
Run them in parallel for two to four weeks, with the new system as the record of truth and the old one read-only. Entering every visit twice for a month creates errors and exhausts the front desk. Keep the old system available for reference, not for daily work.
What should the migration sign-off include?
Patient count, open plan count, outstanding balance total, tomorrow's appointments, a sample of images and three printed receipts with the right GST lines. Add the staff logins, the support number and a fresh export taken after go-live. Two people should sign: the clinic owner and the person who ran the import.
See it with your own clinic day.
Book a walkthrough and follow a patient from booking through charting, treatment and billing. No patient data is needed.