Migrate from Dr.DENTES to Salesforce Sales Cloud

Dr.DENTES contacts map directly to Salesforce Contacts. Salesforce requires an AccountId lookup for every contact — contacts without a primary company are attached to a default 'Unassigned Account' or flagged for manual assignment. Owner resolution happens by email match to Salesforce users before the migration commits.

Dr.DENTES companies map to Salesforce Accounts, preserving the original company name, domain, industry, and size. Parent-child hierarchies in Dr.DENTES translate to the Salesforce Parent Account lookup. When a Dr.DENTES contact belongs to multiple companies, the primary company becomes the AccountId on the Contact, and additional associations are stored as Account Contact Relation records.

Dr.DENTES deals map to Salesforce Opportunities, carrying the deal name, amount, close date, and owner. Each Dr.DENTES pipeline becomes a Salesforce Record Type linked to a Sales Process, ensuring stage pick-list values are isolated. Stage names are mapped value-by-value, probability and forecast category are reapplied from Salesforce conventions, and any Dr.DENTES-specific fields become custom Opportunity fields.

In Salesforce, each Dr.DENTES pipeline is represented by a Sales Process combined with a Record Type. The Record Type scopes the Opportunity StageName pick-list, isolates page layouts, and controls probability and forecast settings per deal type. We create the Record Types and associated Sales Processes before migration, and your admin assigns them to profiles.

Each Dr.DENTES pipeline stage is mapped to a Salesforce Opportunity StageName under the appropriate Record Type. Probability percentages and forecast categories are set according to Salesforce defaults and can be adjusted later. The original stage-entry timestamp from Dr.DENTES is stored in a custom datetime field (Stage_Entered_Date__c) to preserve historical timing.

Salesforce lacks a native lifecycle field, so Dr.DENTES lifecycle or status values are migrated as a custom pick-list (Lifecycle_Stage__c) on the Contact object. If your migration includes a Lead/Contact split, a matching custom field is added to Lead with identical pick-list values. Stage-transition timestamps are preserved in a separate custom datetime field (Lifecycle_Stage_Updated__c) for audit continuity.

Dr.DENTES calls and emails map to Salesforce Tasks with Type='Call' or Type='Email'. Meetings map to Salesforce Events with original start/end times preserved. Original timestamp, owner, and parent-record link are carried through via custom fields and the TaskWhoIds / EventWhoIds relationship.

Dr.DENTES notes are migrated to Salesforce Notes (the modern Note object). The original rich-text content, including basic formatting, is preserved. Any inline images embedded in Dr.DENTES notes are downloaded, uploaded to Salesforce Files (ContentDocument/ContentVersion), and then linked back to the parent Contact, Account, or Opportunity record to maintain context.

Dr.DENTES file attachments are re-uploaded to Salesforce Files. File size limits apply — Salesforce default is 25 MB per file. Files linked to records are attached via ContentDocumentLink so they appear in the Files tab and the record's Related List.

Dr.DENTES custom objects migrate one-to-one to Salesforce custom objects with the __c suffix. Relationships that are N:N in Dr.DENTES are modeled as Salesforce junction objects, which we define in the migration schema before data loads. All custom-object fields are created as matching Salesforce custom fields, preserving data types and pick-list values.

Dr.DENTES owner IDs are resolved by email match against Salesforce users. Unmatched owners are flagged before migration — your team either creates Salesforce users for them or assigns their records to a fallback owner. The original Dr.DENTES owner ID is preserved as Source_Owner_ID__c for audit purposes.