Dentee migration
See what can migrate before you commit to the switch.
Plan an assisted switch from Dentee: review the export, prepare the data, resolve import issues and check the resulting records before your clinic changes systems.
SOURCE WORKBOOKOne workbook through five checksFive checks before cutover
01Workbook requirements checked
02Issue preview
03Controlled import
04Post-import reconciliation
1. Assess
Start with a representative Dentee export
Preserve an untouched source workbook and identify the clinics and date range it covers. A sample should include duplicate names, partial payments, cancelled appointments, tooth-linked treatments and longer clinical histories.
The assessment separates supported fields, cleanup decisions and records that need manual treatment before a timeline is proposed.
The first three checks before any import
The first three checks before any import
- 01Assess
Representative export, clinics, history and scope agreed.
- 02Prepare
Preserved original export and agreed workbook requirements.
- 03Preview
Blocking relationships resolved by documented evidence.
2. Prepare
Confirm the workbook requirements before preparing data
The assessment confirms the required patient, treatment, bill, payment, appointment, prescription, medicine, clinical-note and doctor data against your actual export. It also records the upload limit and fields the current importer can accept.
Do not rename, omit or repurpose workbook tabs without an agreed mapping. Preserve unsupported source material in the agreed archive.
Current source-to-patient data map
Current source-to-patient data map
| Checkpoint | Primary link | Preview question | Reconciliation evidence |
|---|---|---|---|
| Patient | Clinic identity and contact | Duplicate or insufficient match? | Identity and local context sample |
| Treatment / TreatmentType | Patient, procedure and status | Missing patient or unsupported value? | History and total sample |
| Bill / Payments | Patient, invoice and amount | Ambiguous relationship or invalid money? | Invoice, payment and balance totals |
| Appointments | Patient, doctor, time and status | Missing reference or invalid date? | Upcoming schedule sample |
| Prescription / Medicine | Patient and authored record | Missing patient or medicine mapping? | Complex history sample |
| Clinical Notes / Doctors | Patient, clinician and note | Missing clinician or unsupported structure? | Authorship and patient-history sample |
Patient
Primary linkClinic identity and contact
Preview questionDuplicate or insufficient match?
Reconciliation evidenceIdentity and local context sample
Treatment / TreatmentType
Primary linkPatient, procedure and status
Preview questionMissing patient or unsupported value?
Reconciliation evidenceHistory and total sample
Bill / Payments
Primary linkPatient, invoice and amount
Preview questionAmbiguous relationship or invalid money?
Reconciliation evidenceInvoice, payment and balance totals
Appointments
Primary linkPatient, doctor, time and status
Preview questionMissing reference or invalid date?
Reconciliation evidenceUpcoming schedule sample
Prescription / Medicine
Primary linkPatient and authored record
Preview questionMissing patient or medicine mapping?
Reconciliation evidenceComplex history sample
Clinical Notes / Doctors
Primary linkPatient, clinician and note
Preview questionMissing clinician or unsupported structure?
Reconciliation evidenceAuthorship and patient-history sample
3. Preview
Resolve matching and data issues before importing
Thirty2OS prepares import counts and classifies issues before the controlled import runs. Fatal issues block execution where the workbook structure or relationships cannot be handled safely.
Duplicate patient, invalid amount, missing reference and ambiguous relationship issues should be resolved by evidence—not by choosing the match that produces the largest imported count.
Preview issue cards
Preview issue cards
- Duplicate identity: do not guess the patient match
- Missing reference: map or exclude with an owner
- Invalid amount: resolve source and approved financial value
- Ambiguous financial link: block until invoice and patient are evidenced
- Unsupported structure: retain in archive or scope separate treatment
4. Import
Execute against the agreed clinic and preserve import context
The import creates supported patients, treatments, invoices, payments, appointments, prescriptions and clinical notes with organisation and clinic context. Existing matches and approved reference-list mappings are used where the preview supports them.
The exact result depends on the workbook and approved decisions made during preview.
5. Reconcile
Verify money, identity and relationships before cutover
Compare counts, sample patient histories, upcoming appointments, treatment totals, invoices and payment sums. Confirm that each imported payment belongs to the intended invoice and that clinic and doctor relationships are correct.
Supported audited repair workflows exist for specific post-import identity split and financial-link issues, but they require preview and explicit review.
Cutover acceptance criteria
Cutover acceptance criteria
- Patient identities sampled across duplicate-name cases
- Upcoming appointments match agreed scope
- Treatment and clinical histories sampled
- Invoice totals, payment sums and balances reconcile
- Excluded or archived records are documented
- The clinic signs off the record-of-truth cutover
NEXT STEP
Request a Dentee workbook assessment
Share scope and record counts first. A migration plan should be based on a representative export and written decisions—not a generic promise.