Migrate from Henry Schein One to Microsoft Dynamics 365 Sales

Henry Schein One API Exchange does not expose all data elements needed for a complete migration

The Henry Schein One API Exchange, while robust with 700 endpoints and 6 billion annual requests, explicitly excludes required data elements for dental workflows — specifically, the claims submission data and workflow state that practices depend on for billing reconciliation. When migrating to Dynamics 365, practices expecting complete claim history to land in the native case management model will find gaps. We address this by supplementing API pulls with file-based ledger exports from Dentrix and reconstructing a custom Claim__c table in Dynamics 365 that surfaces the billing history without relying on the missing API endpoints. Practices should audit their reporting needs before migration to confirm all required data elements are accessible via export.

Dental imaging files use proprietary encoding that breaks standard file-link migration

Dentrix stores X-rays, intraoral photos, and CBCT scans using a proprietary filename encoding scheme embedded in the patient record. The image file references in Dentrix are not standard file paths — they contain internal identifiers that break when migrated to a flat file system. Microsoft Dynamics 365 has no native dental imaging viewer; files must be exported to SharePoint or an external imaging repository and linked via URL custom fields on the patient Contact record. We run a separate imaging export workflow that decodes Dentrix image filenames, maps them to patient records by ID, uploads to SharePoint, and creates File_Link__c records with the original image path preserved as a reference. Practices with large imaging volumes (CBCT datasets in particular) should budget additional time for this step.

Dynamics 365 Sales Professional caps custom tables at 15 — dental data models typically need more

A complete dental data model in Dynamics 365 requires custom tables beyond the standard Contact-Account-Opportunity model: Treatment_Plan__c, Treatment_Procedure__c (child of Treatment_Plan__c), Insurance_Carrier__c, Insurance_Coverage__c, Claim__c, Claim_Line_Item__c, Clinical_Note__c, Appointment__c, Provider__c, and File_Link__c are all standard requirements. That count — 10 tables — plus any practice-specific extensions pushes against the 15-table limit on Dynamics 365 Sales Professional. Practices on the Professional tier must either upgrade to Sales Enterprise (unlimited custom tables) or carefully prioritize which custom tables to create first and which data elements to consolidate. We identify the required custom table count during scoping and advise on the appropriate Dynamics 365 license tier before migration begins.

Dentrix per-practice licensing does not map to Dynamics 365 per-user licensing — DSO cost structures shift

Dentrix pricing is per practice (or per DSO agreement), covering all users within a practice under one subscription regardless of headcount. Dynamics 365 Sales uses per-user licensing (Sales Professional at $65/user/month, Sales Enterprise at $105/user/month). For a DSO moving 50 users across 10 practices from Dentrix to Dynamics 365, the cost model flips: Dentrix's single practice fee becomes 50 individual Dynamics 365 seat licenses. Some DSOs find Dynamics 365 more cost-effective at scale (especially where fewer than half of practice staff need CRM access), while others see a cost increase. We provide a licensing cost analysis as part of the migration scoping, comparing the current Dentrix spend against projected Dynamics 365 seat costs based on actual user counts.

Appointment and clinical note migration requires custom table creation before data can land

Dynamics 365 Sales has no native appointment entity with operatory, procedure-code, or provider-linkage fields, and no native clinical note structure. Unlike standard CRM migration where objects have a direct equivalent in the destination, dental data cannot be migrated until the custom tables (Appointment__c, Treatment_Plan__c, Clinical_Note__c) are designed, reviewed, and created in the Dynamics 365 environment. If the practice needs Dynamics 365 configured for dental use before data moves, the timeline extends by the custom table design and approval phase. We deliver a custom schema plan upfront showing all required tables, fields, and relationships, so the Dynamics 365 environment is schema-ready before the first record is loaded.