CRM migration
Field-level mapping, validation, and rollback between Henry Schein One and HighLevel. We move data and schema; workflows are rebuilt natively in HighLevel.
Henry Schein One
Source
HighLevel
Destination
Compatibility
10 of 10
objects map 1:1 between Henry Schein One and HighLevel.
Complexity
BStandard
Timeline
24–72 hours
Overview
Henry Schein One (operating Dentrix, Dentrix Ascend, and Jarvis Analytics) stores patient demographics, treatment plans, clinical notes, insurance ledgers, and provider records in a dental-specific schema. HighLevel is a general-purpose all-in-one CRM that organizes data around Contacts, Companies, and Opportunities with a workflow builder for automations. The two platforms share almost no native object equivalency — Dentrix has no standard CRM Opportunity, and HighLevel has no native insurance or treatment-plan object. We extract patient records, provider data, appointments, and treatment plans from the Dentrix database, map them into HighLevel Contacts and custom objects, and configure custom fields for the dental data that has no CRM-native equivalent. Workflows, appointment reminders, and recall sequences must be rebuilt in HighLevel's workflow builder — they do not migrate. Our migration uses scoped read-only access to the Dentrix database; Dentrix itself stays fully operational throughout the cutover window. The migration also preserves provider credentials and appointment resources to ensure continuity of care after go-live.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Henry Schein One object lands in HighLevel, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Henry Schein One
Patient
HighLevel
Contact
1:1Henry Schein One patient records map to HighLevel Contacts with direct field transfers for name, date of birth, gender, contact information, and address. We create custom fields for dental-specific properties that have no native HighLevel equivalent — including insurance carrier, group number, and employer.
Henry Schein One
Insurance Carrier / Plan
HighLevel
Custom Fields on Contact
1:1Insurance carrier name, group number, subscriber ID, and effective dates store as custom fields on the Contact record in HighLevel. Multi-plan patients receive multiple custom field sets or a custom Insurance Plans object linked by contact ID. This approach ensures that eligibility checks can be automated using the HighLevel workflow builder with the carrier and group data.
Henry Schein One
Treatment Plan
HighLevel
Custom Object (Treatment Plans)
1:1Treatment plan codes, tooth numbers, surfaces, procedure descriptions, fees, and acceptance status migrate to a HighLevel custom object linked to the Contact record. Custom object relationships are created in HighLevel before migration so foreign keys resolve correctly. Each treatment plan line is assigned a unique identifier that mirrors the Dentrix plan ID, allowing downstream references in reporting.
Henry Schein One
Appointment
HighLevel
Calendar Event / Task
1:1Scheduled appointments map to HighLevel Calendar events with start time, duration, provider name, and procedure type. Cancelled or no-show appointments migrate as completed tasks with status tags for reporting continuity. We also retain the original appointment status code as a custom field to support historical analytics after migration.
Henry Schein One
Provider / Doctor
HighLevel
Contact (staff type)
1:1Dentrix provider records migrate as HighLevel Contacts with a Staff tag, specialty field, and license number stored in custom fields. Provider-to-appointment links are preserved via the calendar event owner field. The Staff role enables filtering providers in HighLevel reports and ensures they appear correctly in the scheduling calendar.
Henry Schein One
Ledger / AR Entry
HighLevel
Note attached to Contact
1:1Dentrix ledger history — charges, payments, adjustments, and insurance write-offs — stores as Notes attached to the Contact record in HighLevel. HighLevel has no native accounts-receivable object; the full ledger history is preserved as reference text for billing staff. This preservation allows the billing team to reference historical charges without requiring a separate accounting system.
Henry Schein One
Clinical Note
HighLevel
Note / Custom Field on Contact
1:1Clinical notes, perio chart data, and medical history entries from Dentrix are extracted as plain text and attached as Notes to the Contact record. Practices choose whether to keep clinical notes as a single long note or split by visit date.
Henry Schein One
Referral Source
HighLevel
Custom Field on Contact
1:1Referring doctor name and practice stored as a custom text field on the Contact record. Referral source attribution migrates as-is and can be used to tag contacts for HighLevel workflow segmentation. Tagging enables targeted outreach campaigns and helps track referral performance over time.
Henry Schein One
Document / Attachment
HighLevel
Files attached to Contact
1:1Patient documents and uploaded files from Dentrix attach to the corresponding Contact record in HighLevel as Files. Each file is linked to the contact by ID. Note: Dentrix uses proprietary image filename encoding; we extract the binary file and re-upload with a descriptive name.
Henry Schein One
Insurance Claim
HighLevel
Custom Field + Note on Contact
1:1Claim status, submission date, and payer reference store as custom fields on the Contact. Full claim history is preserved as a Note. Practices using HighLevel's billing features map claim data to invoice records manually post-migration. The custom fields enable automated claim tracking workflows in HighLevel once the practice configures the appropriate triggers.
| Henry Schein One | HighLevel | Compatibility | |
|---|---|---|---|
| Patient | Contact1:1 | Fully supported | |
| Insurance Carrier / Plan | Custom Fields on Contact1:1 | Fully supported | |
| Treatment Plan | Custom Object (Treatment Plans)1:1 | Fully supported | |
| Appointment | Calendar Event / Task1:1 | Fully supported | |
| Provider / Doctor | Contact (staff type)1:1 | Fully supported | |
| Ledger / AR Entry | Note attached to Contact1:1 | Fully supported | |
| Clinical Note | Note / Custom Field on Contact1:1 | Fully supported | |
| Referral Source | Custom Field on Contact1:1 | Fully supported | |
| Document / Attachment | Files attached to Contact1:1 | Fully supported | |
| Insurance Claim | Custom Field + Note on Contact1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Henry Schein One gotchas
Proprietary image encoding breaks image links post-migration
Insurance EDI re-enrollment required with every payer
API Exchange restrictions limit third-party data access
PCI compliance does not transfer between systems
Jarvis Analytics generates derived data that does not export
HighLevel gotchas
Sub-account architecture creates isolated data silos per client
Usage-based telecom and AI costs are not in the subscription price
Workflows have no native equivalent in most destination CRMs
API rate limits cap bulk migration throughput at 100 requests per 10 seconds per sub-account
White-label configuration and branding assets do not export via API
Pair-specific challenges
Migration approach
Extract Dentrix data and audit custom field requirements
FlitStack connects to the Dentrix database (on-premise SQL Server) or works with an API Exchange partner to extract patient records, providers, appointments, treatment plans, ledger entries, clinical notes, and attachments. We audit the extracted schema and produce a custom field design document for HighLevel, listing every dental field, its HighLevel target (custom field or custom object), the data type, and any value-mapping required. The custom field design is reviewed and approved before any HighLevel configuration begins.
Configure HighLevel custom fields and custom objects
We create the custom fields on the Contact object (insurance carriers, recall dates, employer, responsible party) and deploy the Treatment_Plan__c custom object with its related fields (procedure code, tooth number, surface, fee, status). Field-level security and visibility settings are configured to match the practice's staff roles. This step completes before any test migration runs so field IDs are stable for mapping.
Run test migration and verify field-level accuracy
A representative slice of 100–500 patient records migrates first, including records with treatment plans, multiple insurance carriers, and clinical notes. We generate a field-level diff comparing source values against the HighLevel destination values. The practice reviews the diff to confirm insurance mappings, recall dates, and treatment plan display meet expectations. Any field mapping adjustments are made before the full migration commits.
Execute full migration with delta-pickup window
The full record set migrates to HighLevel with all custom objects and attachments. A delta-pickup window of 24–48 hours opens simultaneously, capturing any records created or updated in Dentrix during the cutover period. FlitStack AI applies the delta changes to HighLevel so the destination reflects Dentrix's final state at go-live. The practice retains full read and write access to Dentrix throughout.
Reconcile record counts and deliver audit log with rollback option
We run a final reconciliation comparing total contact count, appointment count, and treatment plan count between Dentrix and HighLevel. An audit log listing every record migrated, its source ID, and destination ID is delivered to the practice. If reconciliation identifies discrepancies, FlitStack provides a one-click rollback to the pre-migration state. Post-migration, we deliver a HighLevel workflow rebuild specification documenting the existing recall intervals and appointment reminder logic for the practice's admin to implement in the workflow builder.
Platform deep dives
Henry Schein One
Source
Strengths
Weaknesses
HighLevel
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Henry Schein One and HighLevel.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Henry Schein One: Not publicly documented per-org limits; enterprise customers receive dedicated API capacity.
Data volume sensitivity
Henry Schein One exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Henry Schein One to HighLevel migration scoping. Not seeing yours? Book a call.
Walk through your Henry Schein One to HighLevel migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Henry Schein One
Other ways to arrive at HighLevel
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.