Migrate your Dentally data

Patients is the core record object in Dentally, holding contact details, medical history, clinical notes, and insurance information. Standard fields migrate cleanly between systems. We handle patient-level custom fields by mapping them to equivalent destination properties or custom field schemas.

Treatment items define the clinical procedures offered by the practice, including codes, pricing, and clinical notes. They support custom fields added via Settings > Treatments & Plans. We preserve treatment item hierarchies and link them to associated patients and appointments.

Dentally supports custom fields on patient records, accessible via Settings > Practice Settings > Custom Fields. These can be text, tick boxes, or preset dropdown options. We map these to destination custom fields and flag any dropdown options that require re-creation in the target system.

Custom fields on individual treatment items are created in the Fields tab of each treatment. They are distinct from patient-level custom fields. We export these as structured key-value pairs and re-apply them during import, noting which treatment items carry custom field data.

Appointments link patients to practitioners and treatment items with scheduling status, duration, and notes. We preserve appointment history including past visits. Practitioner re-assignment during migration is handled via a name-matching process to avoid orphaned records.

Practitioners are the clinical and administrative staff with calendar visibility and appointment assignments. We map practitioner records by name and email, preserving role permissions where the destination supports role-level access control.

Treatment plans group related treatment items for a patient and track proposed, accepted, and completed states. We preserve the full plan structure including item order, pricing, and status flags at time of migration.

Tasks are practice-level work items created in Dentally's task list. They support due dates, assignees, and completion status. We export open and completed tasks within a configurable lookback window agreed upon during scoping.

NHS e-referral submissions are integrated into Dentally's workflow for UK practices. They represent structured referral records tied to specific patients. We flag these for explicit review because destination platforms may not have an equivalent NHS referral object and data may need to be stored as clinical notes or attachments.

Payment records linked to treatment items and patients are migrated as part of the patient record. We note that Xero integrations handle accounting downstream and must be reconfigured separately after migration to restore automated payment reconciliation.

Dentally Vision is a separate integrated imaging product requiring its own setup and licensing. We export imaging metadata and links where accessible, but image files themselves require separate handling and the destination must have compatible imaging software configured before clinical use.

Dentally Portal is the patient-facing module for online bookings, form completion, and payment. Portal accounts are tied to patient email addresses. We export portal configuration settings and patient portal status, but the destination platform must support equivalent patient portal functionality.

Practices running multiple sites in a single Dentally account have location-specific data that must be disaggregated during migration. We separate site-level appointment, patient, and practitioner records and map them to the appropriate destination locations, which may require additional scoping time.

The Other section in Practice Settings holds security, IP restrictions, custom email domains, currency, timezone, and custom field configurations that apply across the practice. We extract these settings and note any region-specific parameters that cannot be transferred to a non-Dentally destination.