Migrate from Dr.DENTES to Microsoft Dynamics 365 Sales

Dr.DENTES patient records map 1:1 to Dynamics 365 Contact. The patient's name, date of birth, address, phone, email, and insurance fields migrate as Contact columns or custom fields prefixed new_. The original Dr.DENTES patient ID is stored as new_SourcePatientID__c on the Contact for traceability and delta-run de-duplication.

Each Dr.DENTES practice or clinic location migrates as a Dynamics 365 Account. Address, phone, and practice name map directly to the corresponding Account fields. For multi-location groups, parent-child practice hierarchies in Dr.DENTES map to Account.ParentAccountId relationships in Dynamics 365, preserving the organizational structure. Where Dr.DENTES stores a primary provider or practice manager on the location record, that assignment migrates as the Account's owner lookup in Dynamics 365.

Dr.DENTES treatment plans contain procedure codes (CDT), proposed dates, accepted status, and provider notes. There is no native treatment plan entity in Dynamics 365 Sales, so FlitStack creates a new_TreatmentPlan custom table in Dataverse with columns for plan date, provider lookup, status, and linked Contact. CDT codes migrate as text values or pick-list values depending on whether a value-mapping table exists.

Individual procedure items within a Dr.DENTES treatment plan (tooth number, surface, CDT code, fee, insurance estimate) map to a new_ProcedureLine custom table with a lookup to new_TreatmentPlan. This preserves the one-to-many relationship between plan and procedures. The procedure status (proposed, completed, rejected) maps to a pick-list on the custom table.

Dr.DENTES appointments carry provider ID, operatory, date range, procedure code, appointment type, and status. They migrate as Dynamics 365 Appointment activities linked to the Contact. Provider assignment resolves to the Dynamics 365 systemuser by email match. Operatory and appointment type store as custom columns (new_Operatory, new_AppointmentType) on the activity record.

Dr.DENTES insurance fields (payer name, group number, policy number, subscriber relationship, effective dates) have no native Dynamics 365 equivalent. FlitStack creates a new_InsurancePolicy custom table with lookups to Contact and, optionally, to an Account representing the insurance company. Fields like new_PayerName (text), new_GroupNumber (text), and new_SubscriberRelationship (pick-list) preserve the full insurance profile.

Dr.DENTES clinical notes attached to patient records migrate as Dynamics 365 Annotation entities linked to the Contact. Original note timestamps, provider author, and note type ( SOAP format, narrative, etc.) are preserved as annotation properties. Rich-text formatting is retained as HTML in the notetext column.

Dr.DENTES billing records (procedure charges, insurance payments, patient payments, adjustments, write-offs) have no native Dynamics 365 equivalent. A new_BillingLine custom table stores the charge amount, payment amount, adjustment, balance, and payment date, linked to the Contact and the associated new_ProcedureLine. This gives finance teams a complete ledger per patient without requiring Dynamics 365 Finance.

Dr.DENTES document attachments — consent forms, insurance cards, clinical images, X-rays — migrate as Dynamics 365 Annotation records of type 'Document'. Files are downloaded from Dr.DENTES and re-uploaded to the Dynamics 365 SharePoint-integrated document storage or Dataverse file attachments. Original filenames and MIME types are preserved in the annotation properties.

Dr.DENTES provider and staff records map to Dynamics 365 systemuser accounts by email address match. Active providers are matched first; inactive or departed staff are flagged and assigned to a fallback owner (typically the practice administrator). The Dr.DENTES user ID is stored as new_SourceUserID__c on the systemuser record for audit traceability.

Dr.DENTES recall records (6-month cleaning, annual exam, perio maintenance due dates) have no native Dynamics 365 equivalent. FlitStack creates a new_PatientRecall custom table with next recall date, recall type, and last appointment date, linked to Contact. This enables Dynamics 365 users to run recall reports without rebuilding the logic from scratch.

Any Dr.DENTES custom field that does not map to a native Dynamics 365 Sales column is created as a custom column on the appropriate table using the new_ prefix (e.g., new_TreatmentPhase on Contact, new_RxAntibiotic on new_ProcedureLine). Field data type is preserved — text fields stay text, pick-lists become option sets, date fields become datetime columns. Value-mapping is applied for pick-list fields with discrete value lists.