Dental Software Migration: Patient Records, Imports and Checks
Plan a dental software migration: field mapping, duplicate checks and financial reconciliation. See what Dentiva can import and what needs separate handling.

A dental software migration starts with agreeing which records can move, how they will be checked and how the clinic will access anything that cannot move. Exporting a spreadsheet is only the start. Patient details, clinical history, attachments and financial transactions need separate decisions.
This guide is published by Dentiva and was updated on 26 October 2026 against the current import fields and workflows. It describes a practical transition process, not a guarantee of lossless migration or a promise to import every vendor's database.
Define the migration scope before choosing a launch date
List the source system, record types, responsible staff and intended destination. Ask the current provider for a sample export and the conditions for obtaining it. Keep an authorised copy of the originals and document how the files will be protected during transfer.
| Record type | What to inspect in the source export | Destination question |
|---|---|---|
| Patient directory | Identifier, name, contact, dates and branch context | Which fields can be mapped and how are duplicates handled? |
| Clinical record | Notes, tooth/surface findings, treatment status and authorship | Will this be structured, an attachment or source-only history? |
| Images and documents | Original file, format, size and patient association | Can the destination accept and retrieve the original correctly? |
| Financial history | Invoices, receipts, credits, corrections and opening dues | Is there a supported financial import or a separately agreed process? |
| Upcoming work | Future visits, unfinished care and clinician-recommended recalls | Who will check or re-enter these before the clinic starts using the new system? |
Do not merge patients merely because their names or phone numbers match. Family members can share a number, and one patient can have more than one source identifier. Have clinic staff resolve uncertain matches while preserving the source history.
What Dentiva's current import supports
The enabled import types are patients, doctors, services and leads. The wizard accepts CSV and XLSX, provides column mapping and row validation, and checks duplicates before finalisation. A downloadable patient import template is available. Use its data sheet and field guidance rather than a guessed format.
Patient-directory fields include names, contact details, date of birth/age, gender, address, medical alerts, allergies, medications, conditions, communication preference and notes. These fields do not constitute a full historical dental EMR transfer.
The current import wizard does not import appointments, invoices or payments, structured odontograms, treatment-session history or image/document attachments. Those types must not be promised as an automatic CSV migration. Agree a separate supported handling process, or preserve access to the source records. Importing a notes cell does not recreate the original authorship, tooth structure or audit trail.
A small mapping example
| Source column | Dentiva destination | Validation question |
|---|---|---|
| Patient name | Full name | Is the name present and attached to the correct person? |
| Mobile | Mobile | Does the value normalise to a valid supported patient number? |
| DOB | Date of birth | Is day/month order correct and the date valid? |
| Drug allergy | Allergies | Does the original wording remain clinically understandable? |
| Previous notes | Notes, when appropriate | Is this suitable summary text rather than a substitute for structured history? |
| Balance due | No financial-import field | Who will preserve and reconcile the source invoice/receipt history? |
Check the live template for accepted columns. Avoid placing invoices, full clinical files or sensitive unrelated material into a catch-all notes column just to make the import pass.
Validate a sample with the people who know the records
Choose a sample that includes common and difficult cases: similar names, shared phone numbers, changed numbers, missing dates, allergies and patients with ongoing care. A random sample alone can miss these cases.
After staging, inspect the row report. Correct invalid values and resolve duplicate decisions before finalising. Record how many rows were accepted, skipped or rejected and why. A file having 1,000 rows does not establish that 1,000 distinct patients should be created.
Ask a clinician to check clinical summaries and reception to check identity/contact details. For historical documents kept outside the new system, test retrieval using the source identifier and check that access is limited to authorised staff.
Treat financial reconciliation as a separate workstream
For each patient with dues, retain the original invoice and received-payment evidence. Record the agreed opening balance, the date it was calculated and who checked it. A total receivables number can match while balances are assigned to the wrong patients.
For a fictional patient, an ₹18,000 invoice with ₹13,000 received leaves ₹5,000 due. Check those three amounts and the underlying documents together. Do not create a new ₹18,000 invoice solely to reproduce a ₹5,000 opening due; that could duplicate reported revenue. Agree the supported method with the provider and accountant.
See Dentiva's patient-billing scope and the daily reconciliation guide.
Rehearse a complete clinic day
Before switching, have staff find a patient, book a visit, inspect relevant history, record current care and verify a receipt. Check permissions using the actual receptionist and clinician roles. Confirm upcoming appointments and unfinished treatments individually where they were not imported.
Keep a cutover log: the last source-system entry, first destination entry, exceptions and the person responsible for each. Avoid uncontrolled dual entry, where the same payment or clinical note is entered twice without reconciliation.
Preserve access and agree a recovery plan
Agree the source access period, record-retention responsibilities, export format and cancellation timing before ending the old subscription. A generic 30-day overlap is not a legal retention rule and may be insufficient for your records.
Define when the team would pause the cutover, who can restore access and how new records made during the transition would be reconciled. A backup is useful only if the right staff can retrieve the correct information when needed.
Migration acceptance checklist
- Record the scope, exclusions, owner and planned switch date.
- Obtain and protect authorised source exports.
- Test the actual destination template with a representative sample.
- Resolve identity, date and duplicate exceptions.
- Check patient-level financial evidence separately.
- Confirm clinical history and attachment access.
- Rehearse a complete visit with the team.
- Record acceptance, unresolved items and the recovery process.
Can Dentiva import my entire Practo, BestoSys or other database?
Do not assume that. The enabled wizard imports the supported directory/catalogue types described above. Request a source sample and written scope before planning a complete database move.
Will imported notes recreate my tooth chart?
No. Free-text notes and structured odontogram findings are different records. Preserve the source chart and agree how staff will access clinically relevant history.
How long will migration take?
That depends on source access, data quality, supported scope and validation. Agree a schedule after testing a sample; an instant-migration promise is not a substitute for checked records.
Should we cancel the old system immediately?
Only after the clinic has accepted the agreed result and arranged ongoing access to retained records. Follow the applicable retention obligations and contract rather than a universal overlap period.
Review patient records, compare software and discuss a migration demo using an anonymised sample and your record-type checklist.
The Database Reactivation Playbook
Discover how to audit dormant patient records, segment your files, and execute recall campaigns that recover lost treatment cases.


