Migrate your Henry Schein One data

Patient demographics, contact information, medical history flags, and insurance relationships map cleanly via the API Exchange. We extract the full patient record and recreate it in the destination system, preserving treatment history and appointment associations.

Future scheduled appointments and appointment history transfer reliably. However, appointment-specific custom flags, provider color-coding, and template associations may not map identically across platforms — we flag these during the scoping call.

Treatment plan records, procedure codes, and associated fees export from Dentrix/Dentrix Ascend. The level of clinical detail (tooth numbers, surface designations, diagnosis codes) that survives depends heavily on the destination system's schema for clinical documentation.

Insurance carrier, plan details, subscriber information, and eligibility history export cleanly. However, EDI enrollment is tied to the PMS's payer IDs, not the data itself — when switching systems, the practice must re-enroll with each payer separately, which we flag as a separate workflow step.

Account balances, ledger entries, payment history, and adjustment records map 1:1 via the API. We verify AR totals match between source and destination before declaring the ledger migration complete.

Free-text clinical notes and perio chart data export, but note formatting and structured clinical data (perio measurements, tooth charts) vary significantly across platforms. We scope which clinical data types are supported by the destination before migrating.

Dentrix encodes image file names using a proprietary scheme, and broken image links are the most reported post-migration issue in dental PMS migrations. We perform a dedicated imaging migration pass, remapping file references to the destination system's naming convention, and validate every image category independently before go-live.

Lab case records, Rx prescriptions, and prosthesis orders export from Dentrix. Links to external lab systems (through LinkIt or direct integrations) may not carry over — we document which lab connections need to be re-established in the new system.

Provider records, staff profiles, role assignments, and schedule templates export cleanly. We map provider IDs to the destination system's user accounts and verify schedule permissions post-migration.

Office-specific custom fields, recall systems, and tagging schemes require field-level mapping. We document all custom fields during discovery and map each one explicitly to the destination field or flag it as a manual re-entry item.

Jarvis Analytics generates reporting and benchmarking data derived from the live PMS database. This derived data is not independently exported — it must be regenerated in the destination system's analytics module after the core data migration is complete.

Payment history, card-on-file tokens, and billing configuration export but PCI compliance status does not transfer — the new system will require its own PCI self-assessment. We flag this to avoid $75/month non-compliance fees from the payment processor.