Migrate your Open Dental data

The core patient record (PatNum) is the primary key across the entire system. All clinical, financial, and communication data links back to Patients. We migrate patient demographics, contact info, billing guarantors, and super-family groupings. Family tab structure is preserved by mapping guarantor relationships.

Custom patient fields support Text, PickList, Date, Checkbox, and Currency types. Field definitions (PatFieldDefs) must be exported separately from values. We map both definitions and values, and resolve picklist items by name against the destination system's equivalent lists.

Appointment records include provider, operatory, start/end times, recall linking, confirmation status, and appt field values. We preserve appointment history including completed, cancelled, and no-show records and reconstruct the recall chain linking.

Clinical procedure records include tooth numbers, surfaces, ADA codes, provider, date performed, fee, and status. We map procedure codes to destination equivalents and preserve treatment plan stages, attachments, and benefit insurance estimates.

Claims link patients, providers, procedures, and insurance plans. We migrate claim status history, supplemental claim records, tracking entries, and associated ClaimProcs. The ClaimPayments table is also migrated to preserve the insurance payment ledger.

PayPlans (dynamic) support structured payment schedules with PayPlanLinks to individual procedures or charges. We preserve the plan terms, linked items, and completed pay splits. Some legacy PayPlan formats may require mapping review for date-range and adjustment logic.

Documents are stored as files (images, PDFs) with database entries referencing patient folders. We export document metadata, category assignments, and file references. Actual binary files must be exported from the A-to-Z folder on the server separately from the database export. Radiographs require a separate x-ray bridge and are not included in standard migrations.

Insurance plan definitions, fee schedules, coverage categories (CovCats), and coverage spans migrate as structured data. PatPlans linking patients to insurance carriers are preserved. We map carrier names and plan numbers but verify benefit percentages against destination plan structures.

Provider records include name, credentials, NPI, fee schedules, and scheduling rules. We map provider assignments across procedures, appointments, claims, and pay splits. Provider specialties are preserved as provider properties.

The Clinics feature is only active when enabled. Multi-location practices may have Clinics disabled. We detect the Clinics setting during pre-migration scoping and map clinic assignments only where the feature is in use. Practices running separate databases per location do not use this object.

User accounts and security permissions are separate from provider clinical records. We map user logins, role assignments, and preference overrides. Password hashes do not transfer; staff will need to reset credentials on the destination system.

Custom sheets use a proprietary XML format that only imports into another Open Dental database. We export sheet definitions and data, but the XML structure requires conversion for any non-Open Dental destination. Sheet data attached to patient records is migrated as structured fields.