Migrate from Dent-O-Soft to Salesforce Sales Cloud

Every Dent-O-Soft patient record becomes a Salesforce Contact. The Contact's AccountId links to the dental practice's Account. Primary dentist assignment resolves to Contact.OwnerId by email matching against Salesforce users. Patient status (active/inactive) migrates to a custom Contact.Active_Patient__c boolean field. Additional contact details such as phone, email, and address map to standard Contact fields, and the original patient identifier is preserved in a custom Source_Patient_ID__c field for future delta syncs.

Dent-O-Soft's practice location data maps to a Salesforce Account with type='Dental Practice'. Multi-location practices generate multiple Account records with hierarchical Parent Account linkage. Each Contact's AccountId points to its primary practice location. The practice's address, phone, and website migrate to standard Account fields (BillingAddress, Phone, Website), and the Tax ID is stored in a custom Tax_ID__c field.

Dent-O-Soft allows multiple providers per patient simultaneously. The primary provider maps to Contact.OwnerId. Secondary providers migrate as Account_Contact_Relation junction records with a custom Provider_Role__c pick-list field (Primary Dentist, Hygienist, Specialist). This preserves the full provider history without overwriting the OwnerId.

Dent-O-Soft appointment records map to Salesforce Events. Event.WhoId links to the patient Contact; Event.WhatId links to the Account. Original appointment datetime, duration, operatory number (stored in Description or a custom Operatory__c field), and provider assignment are preserved. Cancelled or no-show status maps to a custom Status__c field on Event.

Each Dent-O-Soft treatment plan becomes a Salesforce Opportunity keyed by a 'Dental Treatment' record type. Opportunity.Name is the treatment plan label. Opportunity.Amount is the estimated total. Procedure line items map to custom Opportunity_Line_Item__c records. Stage values (Proposed, Accepted, In Progress, Completed) map to Salesforce Opportunity Stage pick-list via value mapping.

Dent-O-Soft clinical notes (per-tooth conditions, periodontal readings, existing restorations) are too structured for a single text field. Tooth-chart data maps to a set of custom fields on Contact (Tooth_1_Condition__c through Tooth_32_Condition__c pick-list values: healthy, filling, crown, implant, missing, etc.). Long-form clinical notes attach as Salesforce Files on the Contact record with a custom Clinical_Note__c flag.

Periapical, panoramic, and CBCT image files from Dent-O-Soft re-upload to Salesforce Files and are linked to the patient Contact via ContentDocumentLink. A custom Image_Type__c pick-list on ContentVersion (X-Ray, Panoramic, CBCT, Clinical Photo) enables filtered reporting. Files exceeding Salesforce's 25MB per-file limit are split or compressed before upload.

Dent-O-Soft stores primary and secondary insurance carrier names, group numbers, subscriber IDs, and eligibility flags. A custom Insurance_Carrier__c object with fields Carrier_Name__c, Group_Number__c, Subscriber_ID__c, Eligibility_Status__c, and Is_Primary__c attaches to the Account. Salesforce has no native insurance data model, so this custom object must be created before migration.

Individual charge line items in Dent-O-Soft (prophylaxis, restoration, extraction) do not map to a single Opportunity.Amount. We split: the total encounter amount becomes Opportunity.Amount, and individual procedure codes with CDT codes, fees, and payment status migrate to a custom Invoice_Line_Item__c object linked to the Opportunity. This preserves billing audit trails that Salesforce's standard model cannot hold.

Dent-O-Soft referral-source records (referring dentist, advertising source, walk-in) map to Salesforce Leads. Lead.Source maps from Dent-O-Soft's referral_type field. The referring dentist's name and practice become Lead.Company. When a Lead converts to a Contact, the referring-dentist relationship is preserved as an Account Contact Relation on the converted Contact.

Dent-O-Soft recall records (hygiene re-care intervals, specialist follow-up) have no Salesforce equivalent. We map them as Salesforce Tasks with Task.ActivityDate set to the recall due date, Task.Subject describing the recall type, and a custom Recall_Type__c field. A completed recall creates a completed Task; missed recalls surface as open Tasks in the Salesforce task queue.