Dentrix to HubSpot migration
Moving from Dentrix to HubSpot CRM means translating a dental practice management system into a business CRM. We map every Dentrix patient, insurance record, appointment, and treatment history into HubSpot Contacts with custom properties, preserving original create dates and provider associations. HubSpot's free CRM core handles the contact-company model; dental clinical data becomes custom fields since no native dental object exists in HubSpot.
FlitStack AI migrates contacts, companies, custom properties on contacts, tasks and hubspot files — reference onlies from Dentrix to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

What moves from Dentrix to HubSpot?
Dentrix is a dental practice management system built around clinical operations — patient records, treatment plans, appointments, insurance claims, and imaging — organized by practice and provider with no native API for bulk export.
Read the full summary
HubSpot is a cloud CRM built around the contact-company-deal model with full REST API access and a free starter tier. The migration carries Dentrix patient records (as HubSpot Contacts), insurance and treatment data (as HubSpot custom properties), appointments (as HubSpot Tasks), and documents (as HubSpot Files linked to contacts). We preserve original timestamps, provider ownership, and household groupings throughout. What does not migrate: Dentrix workflows, automations, and clinical imaging objects — those are dental-practice-specific constructs with no HubSpot equivalent. We surface each of these gaps in the migration plan before data moves so your team can rebuild the operational logic on the HubSpot side using HubSpot's automation tools. The migration plan includes a delta‑pickup window to capture any records created or updated in Dentrix during the cutover period, ensuring a near‑zero‑downtime transition. After migration, you can create HubSpot dashboards that visualize insurance carrier breakdowns, treatment frequency, and recall intervals using the custom properties populated during the transfer, giving your practice immediate analytical insight.
Patient → Contact
Dentrix patient maps 1:1 to HubSpot Contact.
How it maps
Standard name, email, phone, and address fields move to HubSpot built-in contact properties. Dental-specific fields (patient ID, birth date, medical alerts) migrate to HubSpot custom properties created before migration. We also preserve the original patient create date as a custom datetime property, and we map the provider who originally created the record to a custom owner field for audit traceability.
Family / Household → Contact (grouped)
Dentrix family members and responsible-party relationships have no native HubSpot equivalent.
How it maps
We create separate HubSpot Contacts for each family member and link them using a custom Household_ID__c property. The primary guarantor becomes the primary contact; others inherit the group link.
Practice / Office → Company
Dentrix practice or office entity maps to HubSpot Company.
How it maps
Practice name, address, phone, and website move to standard Company fields. Multi-location practices create one Company per location in HubSpot. Each Company record also stores the practice's time zone and a custom property for the location ID, enabling filtered views by office. This supports multi-location reporting without additional custom filters.
Insurance → Custom properties on Contact
HubSpot has no native insurance object.
How it maps
We migrate carrier name, plan name, group number, subscriber ID, subscriber relationship, and coverage percentage as custom contact properties. Each property is created in HubSpot before the migration mapping is finalized. We also add a custom pick‑list for subscriber relationship (Self, Spouse, Child, Other) and a number field for coverage percentage, with validation rules to match Dentrix values.
Appointment → Task (or custom datetime properties)
Dentrix appointment records include date, time, provider, procedure, type, status, and notes.
How it maps
We map appointment date and provider to HubSpot Task (TaskWhoId links to contact, TaskWhatId links to deal or company). Procedure codes and appointment types migrate as HubSpot custom properties on the task.
Treatment / Procedure History → Custom properties on Contact
Treatment history — CDT codes, tooth numbers, description, date, provider, fee, and status — maps to HubSpot custom properties on the Contact.
How it maps
For practices with extensive treatment history, we create a custom Treatment_History__c text block or link related custom objects.
- PatientContact1:1
- FamilyContacttransformed
- PracticeCompany1:1
- InsuranceCustom properties on Contacttransformed
- AppointmentTasktransformed
- TreatmentCustom properties on Contacttransformed
+ 6 more in the mapping below
How Dentrix and HubSpot differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Dentrix | HubSpot |
|---|---|---|
| Deployment model | On-premise server with .dat file database; requires local hardware, backups, and Windows server licensing | Cloud-native SaaS; access via browser and mobile app with no server infrastructure required |
| Primary data focus | Clinical dental operations: tooth charts, CDT codes, treatment plans, insurance claims, imaging metadata | Business relationship management: contacts, companies, deals, lifecycle stage, marketing contacts |
| API access | Henry Schein API Exchange with partner-vendor restrictions; bulk export requires SQL server access or third-party tool | Full REST API and Bulk API; unlimited contacts on free tier, commercial API access at Starter and above |
| Patient grouping model | Patient-household with guarantor and responsible-party relationships across family members | Flat contact list; family/household grouping requires custom properties or association labels |
| Insurance object | Native insurance carrier, plan, group number, subscriber ID, and coverage percentage fields per patient | No native insurance object; carrier name, plan, group number, and coverage require custom contact properties |
| Appointment object | Dedicated appointment table with date, time, provider, procedure code, status, and treatment type | No native appointment object; appointment data migrates as Tasks or custom datetime properties on the contact |
| Imaging / X-ray storage | Integrated Dexis imaging with caries detection and CBCT metadata stored inside the Dentrix image path | No native imaging object; X-rays and photos re-uploaded to HubSpot Files and linked by URL property |
Dentrix to HubSpot field mapping
The 30 most-used fields of 44 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
first_namePatientfirstnameContact -
last_namePatientlastnameContact -
emailPatientemailContact -
phonePatientphoneContact -
mobile_phonePatientmobilephoneContact
| Dentrix field | HubSpot field | Mapping | Note |
|---|---|---|---|
Patient.first_name | Contact.firstname | direct | |
Patient.last_name | Contact.lastname | direct | |
Patient.email | Contact.email | direct | |
Patient.phone | Contact.phone | direct | |
Patient.mobile_phone | Contact.mobilephone | direct | |
Patient.address_line_1 | Contact.address | direct | |
Patient.city | Contact.city | direct | |
Patient.state | Contact.state | direct | |
Patient.zip_code | Contact.zip | direct | |
Patient.dentrix_patient_id | Contact.Dentrix_Patient_ID__c | custom_field_required | HubSpot has no native patient ID field. Custom text property created before migration. |
Patient.date_of_birth | Contact.date_of_birth | custom_field_required | HubSpot has no native DOB field. Custom date property created on Contact. |
Patient.medical_alerts | Contact.medical_alerts__c | custom_field_required | Custom text or multi-line text property on Contact captures allergies and medical alerts. |
Patient.treatment_notes | Contact.treatment_notes__c | custom_field_required | Custom multi-line text property stores clinical notes and medical history summary. |
Patient.responsible_party_name | Contact.responsible_party__c | custom_field_required | Custom text property stores responsible party name for billing purposes. |
Patient.family_relationship | Contact.family_relationship__c | custom_field_required | Custom pick-list (Spouse, Child, Parent, Other) links family members within a household. |
Patient.insurance_carrier_name | Contact.insurance_carrier__c | custom_field_required | HubSpot has no native insurance object. Custom text property created on Contact. |
Patient.insurance_plan_name | Contact.insurance_plan__c | custom_field_required | Custom text property captures insurance plan name from Dentrix insurance record. |
Patient.insurance_group_number | Contact.insurance_group_number__c | custom_field_required | Custom text property for group number; requires exact value mapping from source. |
Patient.insurance_subscriber_id | Contact.insurance_subscriber_id__c | custom_field_required | Custom text property stores subscriber/member ID from insurance record. |
Patient.insurance_subscriber_relationship | Contact.insurance_subscriber_relationship__c | custom_field_required | Custom pick-list (Self, Spouse, Child, Other) for subscriber relationship. |
Patient.insurance_coverage_percentage | Contact.insurance_coverage_pct__c | custom_field_required | Custom number property for coverage percentage; validated against Dentrix value. |
Appointment.appointment_date | Task.activity_date | direct | |
Appointment.appointment_time | Task.hs_all_team_emails | transformed | Time appended to Task datetime field or stored as appointment_time__c custom property. |
Appointment.status | Task.hs_task_status | value_mapping | Dentrix status (Scheduled, Confirmed, Complete, No-Show, Cancelled) maps to HubSpot Task status values; custom pick-list created if needed. |
Appointment.appointment_type | Task.appointment_type__c | custom_field_required | Custom pick-list property for appointment type (Hygiene, Perio, Restorative, Consult, Emergency, Recall). |
Appointment.procedure_code | Task.procedure_code__c | custom_field_required | CDT code from Dentrix stored as custom text on the task for treatment tracking. |
Appointment.procedure_description | Task.hs_task_subject | transformed | Procedure description becomes Task subject; original code stored in procedure_code__c. |
Appointment.provider_name | Task.hs_all_task_assignees | custom_field_required | Internal providers mapped to HubSpot User by email match; external providers become a custom provider_name__c text field on the task. |
Treatment.treatment_date | Contact.last_treatment_date__c | custom_field_required | Most recent treatment date stored as custom date field on Contact. |
Treatment.cdt_code | Contact.last_cdt_code__c | custom_field_required | Most recent CDT procedure code stored as custom text; full history as custom text block. |
What to watch for in a Dentrix to HubSpot migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Imaging files and clinical metadata have no HubSpot equivalent
Dentrix Dexis integration stores X-rays, photos, and CBCT scans with clinical metadata (caries detection results, bone loss measurements, tooth charting) inside the Dentrix image path.
How we handle it
HubSpot has no native imaging object — clinical metadata and AI analysis results cannot migrate at all. We export image files, upload them to HubSpot Files, and link them by URL property on the contact. Imaging metadata (AI detection flags, per-tooth annotations) requires manual re-entry or a separate dental imaging tool post-migration.
Insurance data requires 6–10 HubSpot custom properties per patient
HubSpot has no native insurance object, yet Dentrix stores carrier name, plan name, group number, subscriber ID, subscriber relationship, and coverage percentage per patient.
How we handle it
We create custom contact properties for each insurance field before migration. Practices with dual insurance (primary and secondary) need 12 custom properties. This is manual schema setup — we deliver the property list and configuration plan as part of the migration scoping. The property list includes field labels, data types, and pick‑list options for subscriber relationship, and we validate each field populates correctly on the HubSpot Contact record during the sample migration phase.
HubSpot file size and rate limits affect large document sets
Dentrix document stores can contain thousands of files per practice — EOBs, treatment forms, lab prescriptions, referral letters.
How we handle it
HubSpot's API enforces file size limits per upload and rate limits on the Bulk API. Large document archives require chunked upload scheduling. We test file upload throughput against your document volume during the sample migration phase and adjust the upload strategy accordingly. If any file exceeds HubSpot's size cap, we split it or store a link to the original location. We also monitor rate‑limit headers and back‑off automatically to avoid throttling. This ensures all documents are transferred without manual intervention.
Family/household grouping needs explicit household linking strategy
Dentrix links family members through guarantor and responsible-party relationships that define household billing and insurance.
How we handle it
HubSpot has no native household model. We create separate HubSpot Contacts for each family member and link them using a custom Household_ID__c property pointing to the primary contact's HubSpot ID. Practices using Dentrix's family ledger feature need an additional custom property to track guarantor financial responsibility. We also set a custom property to indicate the guarantor's billing role, and we map any outstanding family balances to a custom currency field on the primary contact. After migration, you can filter contacts by Household_ID__c to view the full family record in HubSpot.
Provider-to-HubSpot-User mapping requires login-capable accounts
Internal Dentrix providers (hygienists, associate dentists) who need HubSpot task assignment map to HubSpot Users by email match.
How we handle it
External referring doctors should not receive HubSpot user accounts — they map to Contacts with a custom Provider_Type__c = 'Referral' property. Mixing these two is a common error during self-service migrations. We validate the provider-contact split during the sample migration before the full run commits. During validation we verify that each provider's email resolves to an active HubSpot User and that no external referral contacts receive login credentials. We also generate a reconciliation list showing each provider's mapping status.
How the migration runs
Extract Dentrix data from server database and audit for quality
We access your Dentrix SQL database (or .dat export via third-party extraction tool if no direct SQL access) and pull all patient, appointment, treatment, insurance, document, and provider records.
What this step covers
We audit for duplicates, incomplete fields, orphaned family records, and missing provider assignments. We document the Dentrix schema version, any custom fields configured in your Dentrix setup, and the file storage location for documents and imaging. This step produces a data quality report and confirms which Dentrix objects have data before mapping begins.
Create HubSpot custom properties for all dental clinical fields
HubSpot has no native fields for patient ID, date of birth, CDT codes, tooth numbers, insurance plan details, appointment types, or treatment status.
What this step covers
We create all required custom properties on the Contact and Task objects before migration: custom text fields for IDs and codes, custom date fields for DOB and treatment dates, custom pick-lists for appointment type, treatment status, and insurance subscriber relationship, and custom number/currency fields for coverage percentage and fees. We deliver a HubSpot property setup checklist that your admin can apply or we apply on your behalf.
Match Dentrix providers to HubSpot Users and validate the provider-contact split
Internal Dentrix providers are matched to HubSpot Users by email address.
What this step covers
If a provider does not yet have a HubSpot user account, we flag it for account creation before migration. External referring doctors are identified and routed to become HubSpot Contacts with Provider_Type__c = 'Referral' rather than HubSpot Users. We validate this split against the provider list during the sample migration phase to prevent login-capable accounts being created for referring doctors who should not have CRM access.
Run sample migration with 50–100 records and verify field-level mapping
A representative slice of patient records — spanning different family sizes, insurance types, appointment histories, and document volumes — migrates first.
What this step covers
We verify that all custom properties populate correctly, that household linking produces the expected family grouping in HubSpot, that appointments appear as Tasks linked to the correct Contact, that insurance fields map to the right custom properties, and that document files attach to contacts. A field-level diff report is generated so you can confirm the mapping before the full migration runs.
Execute full migration with delta-pickup window for in-flight records
The full dataset migrates: patients as Contacts with dental custom properties, families linked by Household_ID__c, practices as Companies, appointments as Tasks, treatment history as custom Contact properties, and documents as HubSpot Files.
What this step covers
A delta-pickup window captures records modified in Dentrix during the cutover window. All timestamps, provider ownership, and create dates are preserved as custom datetime properties where HubSpot overwrites CreatedDate. An audit log records every operation, and one-click rollback is available if reconciliation reveals mapping errors.
Verify record counts, spot-check custom properties, and deliver migration report
Post-migration verification includes: record count comparison between Dentrix source and HubSpot destination (Contacts, Companies, Tasks), spot-checks of dental custom properties (CDT codes, insurance fields, appointment types), confirmation that all document files attached correctly, and a sample end-to-end walkthrough of a family group to verify household linking.
What this step covers
We deliver a migration report listing all migrated records, any records skipped due to data quality, and the delta-pickup log. Imaging files are listed separately with file URLs for verification.
Dentrix - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Dentrix migrations scale with record count, the number of custom properties required, and data-model divergence. All dental clinical fields (CDT codes, tooth numbers, insurance plans, appointment types, treatment status) need HubSpot custom properties — a single patient record can require 30–40 custom fields. Record volume drives base cost; custom property count and multi-location setups push toward the upper price tier. Multi-location group practices or practices with heavy treatment history and imaging file sets fall in the upper range. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Dentrix to HubSpot →Why teams move from Dentrix to HubSpot
- Dentrix's Windows-native interface and server-based architecture feel dated and slow down on aging hardware — a consistent complaint across DentalTown and Reddit r/Dentists threads. Cloud-accessible CRM reduces dependency on office server performance and enables remote access without VPN. Upgrading or replacing older servers also incurs capital expense that can be avoided by moving to a SaaS platform. With a cloud CRM, your team can log in from any browser, reducing the need for on‑premises maintenance.
- Server maintenance, backups, Windows licensing, and Henry Schein support contracts add significant overhead that cloud-native CRM pricing eliminates. Practices report frustration with recurring server costs not reflected in original software quotes. These ongoing expenses often surpass the initial license cost, and IT staff time spent on patch management and backup verification adds hidden labor overhead. Moving to a subscription-based CRM bundles support and updates into a predictable annual fee, simplifying budgeting for the practice.
- Dentrix lacks native mobile access and modern API integrations — practices running Zoom, Calendly, or modern marketing stacks cannot connect Dentrix without middleware. HubSpot's integration marketplace offers direct connections to the tools dental practices already use. With direct integrations, your team can sync calendar events, automate lead capture, and trigger follow-up tasks without custom development. This reduces reliance on IT for routine connectivity and speeds up daily workflow.
- Data portability concerns cited as the top barrier to switching — practices fear they cannot extract their data cleanly from Dentrix's .dat file format and SQL schema. A structured migration with a partner reduces the perceived risk of being locked in again.
- HubSpot's free CRM tier with unlimited contacts provides better value for small practices than Dentrix's per-seat or per-location pricing model, particularly for practices not using Dentrix's clinical imaging or e-prescribing modules. Even practices that require additional storage or advanced automation can upgrade to a paid tier at a fraction of the cost of maintaining a local server and support contract. This cost predictability helps small teams budget for growth without unexpected capital outlays.
Questions, answered
Dentrix to HubSpot migration questions
How long does a Dentrix to HubSpot migration take?
The clock time for data migration runs 48–72 hours for under 50,000 patient records. Setup (custom property creation, provider matching, document extraction) adds 3–7 days before the migration runs. Full project timelines including sample migration, validation, and delta pickup typically run 2–4 weeks for a single-location practice. Practices with over 100,000 records or multi-location setups extend to 5–7 days of processing time and 3–5 weeks total. The longest step is typically waiting for your team to validate the sample migration field mapping.
Will my Dentrix workflows and automations migrate to HubSpot?
No. Dentrix workflows — appointment reminders, recall sequences, insurance follow-up tasks, and treatment plan automations — do not migrate. They operate on dental-specific objects (CDT codes, tooth charts, insurance claims, recall intervals) that have no native equivalent in HubSpot. Rebuilding these in HubSpot requires mapping each Dentrix workflow trigger and action to HubSpot's automation model (workflows, sequences, or HubSpot CRM Playbooks). We can export your Dentrix workflow definitions as a reference document for your team or implementation partner.
What happens to my Dentrix patient data in HubSpot?
Every Dentrix patient becomes a HubSpot Contact with standard name, email, phone, and address fields, plus custom properties for dental fields HubSpot doesn't have natively: Dentrix_Patient_ID__c, date_of_birth, medical_alerts__c, insurance_carrier__c, insurance_plan__c, insurance_group_number__c, last_cdt_code__c, last_tooth_treated__c, and treatment_status__c. Insurance coverage percentages and subscriber relationships also migrate as custom fields. Original create dates and provider ownership are preserved as custom datetime and user-linked properties.
Can I migrate Dentrix custom objects and custom fields to HubSpot?
Yes. Any custom fields configured in your Dentrix database — custom procedure codes, insurance plan variants, referral source tracking, recall intervals — map to HubSpot custom properties on the Contact or Task. We audit your full Dentrix schema (standard + custom fields) during the pre-migration audit and create matching HubSpot properties before the migration runs. The key limitation is clinical Dentrix objects like tooth charts and treatment plans: their data migrates as text properties but loses the interactive structure.
What happens to Dentrix X-rays and imaging files in HubSpot?
Clinical imaging — X-rays, photos, and CBCT scans stored in the Dentrix image path — cannot migrate fully. HubSpot has no native imaging object and no equivalent for Dexis-specific metadata like caries detection results or CBCT measurement annotations. We export image files, upload them to HubSpot Files, and link them to the patient Contact via a custom imaging_files__c URL property. Clinical metadata (AI analysis results, per-tooth charting) requires manual re-entry or a dedicated dental imaging tool post-migration.
Does the migration affect my Dentrix account during cutover?
No. We use read-only access to your Dentrix database during the migration. Your team continues working in Dentrix normally throughout setup, sample migration, and the full migration run. A delta-pickup window (typically 24–48 hours after the main migration completes) captures any new patients, appointments, or insurance changes recorded in Dentrix during the cutover period. Once the delta is confirmed in HubSpot, your team transitions to HubSpot and we provide a final reconciliation report.
How does Dentrix family and household grouping work in HubSpot?
Dentrix links family members through guarantor and responsible-party relationships that define billing and insurance responsibility. HubSpot has no native household object, so we create separate HubSpot Contacts for each family member and link them using a custom Household_ID__c property pointing to the primary contact's HubSpot ID. Subscriber relationship (Self, Spouse, Child) and responsible party name migrate as custom properties on each contact. You can then use HubSpot lists filtered by Household_ID__c to view family groups.
Can I migrate Dentrix appointments and treatment history to HubSpot?
Yes. Dentrix appointments (date, time, provider, procedure, type, status, notes) migrate as HubSpot Tasks linked to the patient Contact. CDT procedure codes and appointment types become custom properties on the task. Treatment history — procedure code, tooth number, date, provider, fee, and status — migrates as custom properties on the patient Contact, with the most recent treatment date stored as last_treatment_date__c. Practices with extensive multi-year treatment plans may use a custom text block or linked custom object for full history.
Related migrations
HubSpot implementation
Set up HubSpot and migrate into it as one engagement.
See the service → Twenty CRM to HubSpotMapping · history · rollbackJobber to HubSpotMapping · history · rollbackStreak to HubSpotMapping · history · rollbackAttio to HubSpotMapping · history · rollbackFreshsales to HubSpotMapping · history · rollbackInsightly CRM to HubSpotMapping · history · rollbackSources: official documentation
- Format import files — HubSpot Knowledge Base
- Create and edit custom objects — HubSpot Knowledge Base
- Import objects programmatically — HubSpot Knowledge Base
- Understand property field types in HubSpot
- Associate records on CRM objects — HubSpot Knowledge Base
- Integration throughput and limits — HubSpot Knowledge Base
- HubSpot Cloud Infrastructure and Data Hosting FAQ
Get a quote
Moving from Dentrix to HubSpot?
Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.
Get a quote