Migrate from Dentrix to Salesforce Sales Cloud

Dentrix patient records map directly to Salesforce Contact. The patient's primary family Account is created or matched first, then Contact is linked via AccountId. All contact fields (name, phone, email, address) map 1:1. Dentrix patient create date is preserved in Original_Patient_Create_Date__c custom datetime.

Patient mailing address fields (street, city, state, zip, country) in Dentrix map to Contact.MailingStreet, MailingCity, MailingState, MailingPostalCode, MailingCountry. If Dentrix stores a separate billing address, it maps to Contact.OtherAddress fields in Salesforce.

Dentrix insurance carrier name becomes a Salesforce Account (Insurance_Carrier__c type). The subscriber ID, group number, and eligibility dates migrate to a custom Insurance_Detail__c junction object linking the patient Contact to the carrier Account. If the insurance carrier Account already exists, FlitStack matches by name before creating a duplicate.

Dentrix appointments map to Salesforce Events with Subject = patient name + procedure type, StartDateTime and EndDateTime from Dentrix slot start/end, and WhoId = Contact. Custom fields Operatory__c, Provider__c (lookup to User), and Appointment_Type__c capture Dentrix-specific appointment attributes. Practices preferring a dedicated appointment object use a custom Appointment__c custom object instead.

Dentrix treatment plans have no Salesforce standard equivalent. FlitStack creates a Treatment_Plan__c custom object with fields for plan date, provider, status (proposed/accepted/completed), total fee, and CDT_Code__c pick-list. Each Treatment_Plan__c links to the patient Contact via Contact__c lookup. Original treatment plan create date stored in Original_Create_Date__c.

Individual CDT-coded procedures performed on a patient create Procedure__c records linked to the Treatment_Plan__c and Contact. CDT_Code__c stores the ADA procedure code as a custom pick-list. Surface__c (tooth surface), Quad__c (quadrant), and Fee__c fields capture procedure specifics. Completed procedures have Status__c = 'Completed' with Completion_Date__c.

Dentrix clinical note text migrates to a Clinical_Note__c custom object with a Long Text Area field (32K character limit) preserving full note content. Notes are linked to Contact via Contact__c lookup and to Treatment_Plan__c when associated. Provider attribution preserved via Provider__c lookup to User. Original note timestamp stored in Original_Note_Date__c.

Dentrix providers who need Salesforce login (associate dentists, office managers) become Salesforce Users, matched by email address. Providers who do not need CRM access (referring dentists, retired associates) become Contacts with the custom flag Is_Provider__c = true and Specialty__c pick-list (General Dentist, Hygienist, Oral Surgeon, etc.).

Dentrix billing ledger entries map to a custom Billing_Ledger__c object linked to Contact. Fields include Transaction_Type__c (charge/payment/adjustment), Amount__c, Procedure_Link__c (lookup to Procedure__c), Insurance_Payment__c, Patient_Payment__c, and Ledger_Date__c. Historical ledger data is preserved for auditing even though Salesforce is not a dental billing system.

Dentrix stores X-ray and imaging file paths pointing to a local or network server share. Because Salesforce Files has a 25MB per-file limit and re-uploading clinical images creates HIPAA storage compliance complexity, FlitStack preserves the original file path as a custom URL field Source_Imaging_URL__c on the Contact. Your team configures the destination storage and updates URLs post-migration.

Dentrix recall rules (6-month cleaning reminders, per-procedure follow-up intervals) are workflow logic with no Salesforce native equivalent. FlitStack exports the recall configuration as a structured reference document your Salesforce admin uses to build Salesforce Flow reminder rules post-migration. The original recall interval data is preserved in a custom Recall_Rule__c field on Contact for reference.

Patient allergies, medical conditions, and clinical alerts stored in Dentrix map to a custom pick-list and text field on Contact. Multiple alerts per patient require either a multi-select pick-list or a custom Clinical_Alert__c junction object depending on the number of alert types. HIPAA-flagged conditions stored per your compliance requirements.