Migrate from DentAdmin to Microsoft Dynamics 365 Sales

DentAdmin patient records map directly to Dynamics 365 Contacts. Most fields (name, birthdate, address, phone, email) carry over as-is. Insurer affiliation, RIZIV number, and payment status require custom fields on the Contact record since Dynamics 365 has no native dental-insurer entity.

DentAdmin insurer names and codes have no direct Dynamics 365 equivalent. FlitStack creates an Account record per insurer using the insurer's legal name, then links every affected Contact via a custom InsurerId__c lookup field. The DentAdmin insurer code maps to a custom InsurerCode__c text field on the Account.

DentAdmin provider records (tandarts, specialist, hygienist) resolve to Dynamics 365 SystemUser entities by matching email addresses between the two systems. Each provider's specialty and INAMI/RIZIV registration number are preserved as custom fields (Specialty__c, RIZIVRegistration__c) on the SystemUser record so appointments can correctly reference the practitioner responsible for each visit.

Dynamics 365 Sales has no native scheduling entity — appointments map to a custom Dataverse table (Appointment__c) with fields for PatientId (Contact lookup), ProviderId (SystemUser lookup), StartTime, EndTime, TreatmentCodeId (custom lookup), Status, and LocationId. Practices using Dynamics 365 Field Service can extend this to resource-scheduling entities.

DentAdmin treatment codes ( Flemish RIZIV nomenclature or Dutch UV-begrippen ) have no Dynamics 365 standard equivalent. FlitStack creates a TreatmentCode__c custom table with Code__c, Description__c, Category__c, and DefaultFee__c fields, then links each appointment record via TreatmentCodeId. Value mapping for inactive or deprecated codes requires admin review before migration.

Each completed treatment in DentAdmin is modelled as a custom TreatmentRecord__c table entry linked to the appointment, plus a Dynamics 365 Task activity to surface the clinical note in the patient's timeline. Tooth numbers and surface annotations stored as free text in DentAdmin are preserved in a custom TreatmentNotes__c field.

DentAdmin invoices with line items, insurer refunds, and patient co-pays do not map to any standard Dynamics 365 Sales entity. FlitStack creates an Invoice__c custom table linked to Contact and Opportunity, capturing InvoiceNumber__c, InvoiceDate__c, TotalAmount__c, InsurerAmount__c, PatientAmount__c, and Status__c. Dynamics 365 Business Central integration is required for full accounting workflows.

DentAdmin PDF documents (treatment plans, consent forms, clinical notes) attached to patient records are downloaded and re-uploaded to a SharePoint document library created under the Dynamics 365 environment. Each file is linked to the corresponding Contact record via a Notes record pointing to the SharePoint URL, preserving the original filename and create date.

DentAdmin's DentaSync Outlook calendar synchronisation has no direct Dynamics 365 equivalent in Sales Professional. We export the calendar rule definitions so your admin can configure Dynamics 365 server-side sync to Outlook — the mechanism differs but the outcome (dual-calendar visibility) can be replicated using Power Automate flows for appointment push-back.

DentAdmin SMS logs and email history attached to patient records are imported as Communication__c custom table entries linked to Contact. The message body, direction (sent/received), timestamp, and channel (SMS/email) are preserved. Email templates and automated reminders must be rebuilt in Dynamics 365's Email Template system or Power Automate.

Any DentAdmin custom fields on patient records (allergy flags, medical history fields, referral source) are read from the DentAdmin export schema and created as custom fields on Contact in Dynamics 365. Field type is matched (text, picklist, date, checkbox) using the DentAdmin field metadata. Enterprise licensing is required if the total custom-field count exceeds the 15-table Professional ceiling.

Multi-site DentAdmin setups store location addresses and site-specific providers. FlitStack creates an Account record per site using the site name and address, then flags practitioners who belong to each location via a custom SiteId__c lookup on SystemUser. Contact records retain a primary site via the AccountId lookup. This approach supports Dynamics 365 territory management for multi-location reporting.