Migrate from Core Practice to Microsoft Dynamics 365 Sales

Core Practice has no standard CRM object model — every export requires custom table creation in Dynamics 365 Sales

Core Practice is a practice-management system, not a CRM. Its primary objects (Patient, Treatment, Appointment, Billing) have no native equivalents in Dynamics 365 Sales. Before migration data can land, your Dynamics admin must create custom tables in Dataverse for TreatmentHistory, Appointment, TreatmentPlan, and Billing. Dynamics 365 Sales Professional enforces a 15-table limit — practices needing more than 15 custom entities must upgrade to Enterprise ($105/user/mo) before migration proceeds. We provide the exact table schemas and field definitions as part of the migration plan so your admin can pre-create the structure.

Appointment scheduling does not migrate to Dynamics 365 Sales — scheduling must be rebuilt in Bookings or a third-party app

Core Practice stores appointment records with date, time, provider, and status. Dynamics 365 Sales has no native scheduling engine — appointment records migrate as historical data but the appointment-scheduling workflow requires a separate rebuild. Microsoft Bookings is the native path for Dynamics 365 environments, but it is a separate product requiring additional licensing and setup. We preserve all appointment history as data but do not migrate active scheduling logic, recurring appointment rules, or calendar-sync configurations. This must be addressed in the post-migration Power Apps or Bookings setup phase.

Insurance and payer data requires custom fields on Contact with no native Dynamics 365 equivalent

Dental and specialist practices using Core Practice store insurance carrier, policy number, group number, subscriber ID, and coverage percentages per patient. Dynamics 365 Sales has no standard insurance or payer fields on Contact. We create custom text fields (Insurance_Carrier__c, Policy_Number__c, Group_Number__c) and optionally a related Insurance custom table for multi-payer scenarios. However, these custom fields do not integrate with Dynamics 365's native billing or finance modules — they are reference fields only. Practices needing insurance-claims integration must evaluate Dynamics 365 Fraud Protection or a third-party dental billing connector.

Owner resolution by email fails for staff without Dynamics 365 user licenses

Core Practice providers and administrative staff are assigned as record owners in the source system. Dynamics 365 Sales requires a licensed User record to own a Contact, Account, or Opportunity. We resolve Core Practice staff to Dynamics 365 users by email match. Staff members without a matching Dynamics 365 user are flagged before migration — their patient and treatment records land as Contacts owned by a designated fallback user. This means provider attribution in migrated treatment history may require a post-migration data patch once licensing is settled.

Treatment-plan and clinical-note attachments face file-size and format constraints in Dynamics 365

Core Practice attachments — X-rays, intraoral images, consent forms, PDF treatment plans — migrate to Dynamics 365 file storage linked to Contact records. Dynamics 365's default file size limit is 25MB per file; dental imaging files commonly exceed this. We chunk large files and upload to the associated SharePoint document library connected to the Contact rather than inline attachments. Intraoral image formats (JPEG, PNG, DICOM) are preserved as-is. Practices using DICOM imaging may need a dedicated medical imaging storage integration post-migration.