Migrate your Denticon data

Patient is the central object in Denticon. We migrate patient demographics, contact information, insurance details, referral sources, and custom_field_1/2 properties. Patient portals and online registration data are preserved at the patient level.

Appointments are scheduled against providers and offices, color-coded by production type. We map appointment records including date, time, provider, office, production type, and status across the scheduling schema.

Providers represent clinical staff assigned to offices. We migrate provider profiles, credentials, and office assignments. Multiple providers can be associated with a single office, and vice versa.

Offices (OIDs) are the location-level entities in Denticon's multi-location model. Each office has its own assigned providers, production types, referral codes, and explosion codes. We preserve office-level granularity during migration.

Referrals exist as incoming (external providers sending patients) and outgoing (referring patients to external providers). Custom external referral forms with data tags require field-level mapping. Referral cost fields must be preserved separately from clinical data.

Treatment plans are linked to patients and providers and include procedure codes, tooth surfaces, and clinical notes. We migrate treatment plan history including completed and pending procedures.

Clinical charting includes tooth conditions, restorations, periodontal data, and pre-existing conditions. AI Assist opportunities require Pearl + XVWeb integration and are metadata at migration time. Historical charting records are migrated as-is.

RCM (Revenue Cycle Management) encompasses insurance claims, payments, adjustments, and accounts receivable. Claims history and AR data are migrated with provider and office context. RCM API handles writeback for claims reconciliation.

Automated campaign records and 2-way texting history are migrated. Quiet-hours settings (9 PM–7 AM send restriction) are preserved as configuration metadata. Note: message delivery timestamps may shift during migration due to timezone handling.

Denticon restricts custom fields to two alphanumeric fields of up to 25 characters each on patient, office, provider, referral, and account objects. We map these fields to destination custom fields but flag truncation risk if destination fields have shorter limits.

User accounts with role-based access are migrated with office assignments. Production types and schedule watermarks tied to users are preserved. User login behavior warnings (Chrome shortcut caching) are documented for post-migration training.

Production types categorize appointments by color on the schedule. We migrate all production type definitions and their office assignments. They must be recreated in the destination if the target lacks a comparable color-coding schema.