Migrate from axiUm Dental to Microsoft Dynamics 365 Sales

axiUm patient records with an organizational entity (e.g., a hospital clinic, DSO location, or insurance-linked family account) map to Dynamics 365 Sales Account. The patient name, date of birth, and address fields convert directly. Individual patients without an organizational affiliation map to Contact records instead.

Individual axiUm patients who are natural persons — not organizational entities — map to Dynamics 365 Sales Contact. We preserve the patient ID as Source_System_ID__c for traceability. For patients who appear as both individual consumers and linked to a family or corporate insurance plan, we create a Contact record and link it to the parent Account.

axiUm providers who are active staff members in the target Dynamics 365 Sales organization map to Dynamics User records by email match. Providers who are external referrers or specialists with no Dynamics license map to Contact records with a Provider_Role__c custom field indicating their axiUm provider type (Dentist, Hygienist, Specialist).

axiUm appointments map to Dynamics 365 Sales Activity records (Task or Appointment entity). The appointment date, time, status, provider owner, and appointment type transfer directly. Operatory and chair assignments, which have no Dynamics equivalent, migrate as custom text fields on the Activity record for reference.

axiUm treatment plans with a financial value (procedure code + fee) map to Dynamics 365 Sales Opportunity records using the estimated treatment amount as the Opportunity Amount field. Individual line items (ADA CDT codes) and tooth-specific details are stored in a custom Dental_Treatment_Plan__c table with a lookup to the Opportunity. Treatment plan status (proposed, accepted, in progress, completed) maps to Opportunity Stage values.

axiUm financial transactions — charges, payments, and adjustments — map to Dynamics 365 Sales Invoice records where the invoice represents a billing event. ADA procedure codes, which Dynamics does not natively store, are preserved as a custom field (CDT_Code__c) on the Invoice line. Insurance payments and write-offs are noted in a custom Insurance_Payment__c field since Dynamics lacks a native dental insurance adjudication model.

axiUm clinical notes (progress notes, medical history flags, clinical alerts) have no native Dynamics 365 Sales equivalent. We create a Dental_Clinical_Note__c custom field on the Contact record and migrate note text as long-text values with the original note date and provider owner. Clinical alerts that triggered pop-up warnings in axiUm map to a custom Alert__c field on Contact.

axiUm odontogram charting (tooth-surface conditions) and perio chart (periodontal measurements) are entirely dental-specific with no Dynamics 365 Sales equivalent. We create a custom Dental_Chart__c table in Dataverse with a lookup to the Contact record. Tooth-number and surface fields are stored as custom fields (Tooth_Number__c, Surface__c, Condition__c) and perio measurements as a custom Perio_Record__c table. The graphic chart itself cannot be migrated as visual data — the underlying measurement data transfers numerically.

axiUm insurance records (carrier name, subscriber ID, group number, subscriber relationship, eligibility dates) are preserved as custom fields on the Contact or Account record. Insurance carrier names that appear repeatedly are optionally mapped to a separate Insurance_Carrier__c custom entity to enable reporting on claims volume per carrier.

axiUm provider availability windows and operatory scheduling have no direct Dynamics 365 Sales equivalent. If the destination includes Dynamics 365 Field Service, providers can be set up as Bookable Resources with schedule entities — but this requires Field Service licensing and is not part of the base CRM migration. We flag this as a gap and document the rebuild path.

axiUm customizable clinical forms and CODA-accreditation evaluation forms are academic-specific artifacts. The form field labels and response data migrate as custom fields on the Contact record if they relate to patient data, or as notes attached to the Account record if they relate to institutional tracking. The form structure itself (layout, conditional logic) does not transfer.

axiUm scanned consent forms and attachments stored on patient records are exported and re-uploaded to the Dynamics 365 Sales record's SharePoint document location (if SharePoint integration is enabled) or as Notes/Annotations with the original file attached. We preserve the original upload date and provider who uploaded the document.