Migrate from Denticon to Salesforce Sales Cloud

Denticon's clinical and RCM data has no native Salesforce equivalent — extensive custom objects required

Denticon stores tooth charts, perio measurements, ADA procedure codes, insurance claim histories, and adjustment codes that Salesforce Sales Cloud does not model natively. A single patient record in Denticon with primary/secondary insurance, employer group, guarantor, referral source, and multiple treatment plans may require Contact fields plus three custom objects (Treatment_Plan__c, Claims__c, Referral__c) plus custom fields for billing breakdowns. Before migration begins, we deliver a schema plan specifying every custom object, custom field, and pick-list value that must exist in Salesforce — your admin creates these in a sandbox first so data validates on insertion. This upfront schema design is the longest planning step for a Denticon migration and directly affects timeline.

Provider-to-User email resolution must complete before appointments and treatment plans load

Denticon providers own appointments and treatment plans. Salesforce Events and custom object records require an OwnerId — a Salesforce User ID. We match Denticon provider email addresses to Salesforce User emails. Unmatched providers are flagged before migration: your team either invites them as Salesforce Users first or we assign their records to a fallback owner. This resolution gate must clear before Event records (appointments) and custom object records (treatment plans, referrals) can load, because Salesforce rejects records with invalid OwnerId values at insert time. The consequence of skipping this step is orphaned records with no owner in Salesforce.

Multi-location DSO Account hierarchy must be sequenced — parent Accounts load before child Contacts

Salesforce requires Accounts to exist before Contacts can reference them via AccountId. In a multi-location DSO migration with 45 offices (as in the Affinity Dental case study), we must load the Account hierarchy first — parent PGID-level account, then child office accounts — before any patient Contacts can insert. This creates a dependency chain: if the Account load fails or partially rolls back, every downstream Contact insert fails. We handle this sequencing in our migration runner, but your team must confirm the desired Account hierarchy structure (which Denticon office maps to which Salesforce Account, and which is the parent) before the first load begins.

Dental imaging files (X-rays, scans) require separate storage strategy beyond Salesforce Files

Denticon integrates with XVWeb for dental imaging, and patients may have radiographs, intraoral photos, and CBCT scans attached to their records. Salesforce Files support documents up to 25MB per file. Dental imaging files routinely exceed this — CBCT scans can be 500MB+. We re-upload standard attachments (PDFs, consent forms, treatment plan documents) to Salesforce Files linked to the Contact. Imaging files are flagged in the migration manifest and excluded from the Salesforce load; your team needs a separate imaging storage strategy (XVWeb continues standalone, or you migrate to Salesforce's Health Cloud imaging add-on for larger files). We document every excluded file with its Denticon record reference so nothing is lost silently.

Denticon recall and appointment-confirmation workflows must be rebuilt in Salesforce Flow

Denticon's automated recall reminders (based on last-appointment date and recall-type interval) and appointment-confirmation messages (via the Patient Communication Automated Campaigns module) are platform-native automation. These do not export as portable logic — there is no Denticon workflow-export format compatible with Salesforce. We can export your recall-interval settings and campaign-configuration screenshot as a reference document for your Salesforce admin, but the rebuild must happen in Salesforce Flow or a third-party tool like Brainshark or Marketing Cloud. This is a significant operational decision your team should plan for before migration day; automated patient communication gaps post-cutover affect patient retention.