CRM migration
Field-level mapping, validation, and rollback between Dental-Exec and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.
Dental-Exec
Source
Salesforce Sales Cloud
Destination
Compatibility
13 of 14
objects map 1:1 between Dental-Exec and Salesforce Sales Cloud.
Complexity
BStandard
Timeline
48–72 hours
Overview
Dental-Exec stores patient records, provider data, treatment histories, and appointment logs in a dental-practice-specific schema. Salesforce Sales Cloud has no native concept of dental specialty, production-tracking metrics, or treatment-plan phases — these require custom fields and custom objects on the Account and custom objects we create during schema setup. We extract Dental-Exec data via its export interface, transform each record into the Salesforce data model, and load via the Salesforce Bulk API. Provider-to-patient relationships that Dental-Exec stores as a native many-to-many association need a custom junction object in Salesforce. Treatment-plan records, insurance carrier data, and clinical notes migrate as custom objects with custom fields. Automations, recall sequences, and appointment reminders are not migratable — we deliver a workflow audit export so your Salesforce admin can rebuild those in Flow or Process Builder post-migration. A delta-pickup window captures any records created or modified in Dental-Exec during the cutover so Salesforce reflects your final state at go-live.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Dental-Exec object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Dental-Exec
Patient
Salesforce Sales Cloud
Account
1:1Dental-Exec Patient records map directly to Salesforce Account. Patient-facing fields (name, date of birth, address, contact information) land on the Account object. Clinical data and treatment history require custom fields or a linked Treatment_History__c custom object we create during schema setup.
Dental-Exec
Provider
Salesforce Sales Cloud
Contact
1:1Dental-Exec Provider records (dentists, hygienists, specialists) map to Salesforce Contact. Provider type (dentist, hygienist, office manager) migrates as a Role__c custom pick-list field on Contact. We also create a Dental_Specialty__c pick-list for specialty categorization. Each provider Contact is associated to patient Accounts via a Provider_Patient_Junction__c custom junction object we provision during schema setup.
Dental-Exec
Appointment
Salesforce Sales Cloud
Task / Event
1:1Dental-Exec appointment records map to Salesforce Event for scheduled appointments (with StartDateTime, EndDateTime, WhatId pointing to the Account) and Task for completed visits. Appointment type (hygiene, restorative, consultation) maps to a custom Appointment_Type__c pick-list on the Event or Task. Status (scheduled, completed, cancelled) maps via value mapping to Salesforce activity status pick-list values.
Dental-Exec
Treatment Plan
Salesforce Sales Cloud
Custom Object (Treatment_Plan__c)
1:1Dental-Exec treatment plan records have no Salesforce standard equivalent. We create a Treatment_Plan__c custom object with fields for plan status, procedure code, provider assigned, and estimated completion date. The custom object links to the Account (patient) and Contact (provider) via lookup fields.
Dental-Exec
Treatment History
Salesforce Sales Cloud
Custom Object (Treatment_History__c)
1:1Dental-Exec treatment history records contain procedure codes, tooth numbers, surfaces treated, materials used, and completion dates. We create a Treatment_History__c custom object with a lookup to Account and to the performing provider Contact, preserving the original treatment date as a custom field.
Dental-Exec
Insurance Carrier
Salesforce Sales Cloud
Account
many:1Dental-Exec stores insurance carrier name, group number, and subscriber ID per patient. We merge carrier name into a Salesforce Account record representing the insurance company and store group number and subscriber ID as custom fields on the patient Account linked via Insurance_Carrier__c lookup.
Dental-Exec
Provider-Patient Association
Salesforce Sales Cloud
Provider_Patient_Junction__c
1:1Dental-Exec supports many-to-many relationships between providers and patients, where a patient may see multiple providers and a provider may treat multiple patients. We create a Provider_Patient_Junction__c custom junction object with lookups to both the patient Account and provider Contact, plus a Relationship_Type__c pick-list to capture the nature of each provider-patient relationship.
Dental-Exec
Production Metrics
Salesforce Sales Cloud
Custom fields on Account / Custom Object
1:1Dental-Exec tracks daily production goals, units completed, and collection rate as built-in practice metrics. These have no Salesforce equivalent and migrate as custom number fields (Daily_Production_Goal__c, Units_Completed__c, Collection_Rate__c) on the Account or a custom Production_Metrics__c object — your team configures how these populate post-migration.
Dental-Exec
Recall Record
Salesforce Sales Cloud
Task
1:1Dental-Exec recall records trigger when patients are due for hygiene or checkup appointments. These map to Salesforce Task records with Subject='Recall Due', ActivityDate set to the recall date, and WhatId pointing to the patient Account. Completed recalls mark the Task as Completed.
Dental-Exec
Clinical Note
Salesforce Sales Cloud
Custom Object (Clinical_Note__c)
1:1Dental-Exec clinical notes and progress notes contain rich text observations per visit. We create a Clinical_Note__c custom object with Body__c (long text area), Note_Date__c, and lookups to the patient Account and provider Contact. Notes are linked to the corresponding Event or Task for the visit.
Dental-Exec
Patient Document / Attachment
Salesforce Sales Cloud
Salesforce Files
1:1Dental-Exec file attachments (X-rays, consent forms, insurance cards) re-upload to Salesforce Files attached to the patient Account. File size limits per Salesforce (25MB default per file) apply; inline images in notes are downloaded, rehosted, and linked to the parent Account.
Dental-Exec
Billing Record
Salesforce Sales Cloud
Custom Object (Billing_Record__c)
1:1Dental-Exec billing records (charges, payments, adjustments, outstanding balance) have no Salesforce standard equivalent. We create a Billing_Record__c custom object with Amount__c, Type__c pick-list (charge, payment, adjustment), Date__c, and a lookup to the patient Account. Outstanding balance migrates as a custom currency field.
Dental-Exec
Lead / Prospective Patient
Salesforce Sales Cloud
Lead
1:1Dental-Exec prospects (patients who inquired but did not schedule) map to Salesforce Lead. Name, phone, email, referral source, and interest level map to standard Lead fields. Lead status from Dental-Exec maps via value mapping to Salesforce Lead Status pick-list values.
Dental-Exec
User / Staff Account
Salesforce Sales Cloud
User
1:1Dental-Exec staff user accounts (office managers, billing staff, administrative personnel) map to Salesforce User records. Owner resolution uses email matching — we cross-reference each Dental-Exec staff email against existing Salesforce Users to preserve ownership continuity. Any Dental-Exec staff email with no matching Salesforce User is flagged before migration so your admin can provision the corresponding User record first.
| Dental-Exec | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| Patient | Account1:1 | Fully supported | |
| Provider | Contact1:1 | Fully supported | |
| Appointment | Task / Event1:1 | Fully supported | |
| Treatment Plan | Custom Object (Treatment_Plan__c)1:1 | Fully supported | |
| Treatment History | Custom Object (Treatment_History__c)1:1 | Fully supported | |
| Insurance Carrier | Accountmany:1 | Fully supported | |
| Provider-Patient Association | Provider_Patient_Junction__c1:1 | Fully supported | |
| Production Metrics | Custom fields on Account / Custom Object1:1 | Fully supported | |
| Recall Record | Task1:1 | Fully supported | |
| Clinical Note | Custom Object (Clinical_Note__c)1:1 | Fully supported | |
| Patient Document / Attachment | Salesforce Files1:1 | Fully supported | |
| Billing Record | Custom Object (Billing_Record__c)1:1 | Fully supported | |
| Lead / Prospective Patient | Lead1:1 | Fully supported | |
| User / Staff Account | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Dental-Exec gotchas
No public API for automated exports
Recall and hygiene data embedded in task records
Drug interaction flags are binary, not structured
Thin vendor footprint raises continuity risk
Salesforce Sales Cloud gotchas
Workflow Rules and Process Builder are retired
Bulk API batch quota exhaustion during large imports
Storage overage billing is non-obvious
Account-Contact many-to-many relationship mapping
Territory and team member import ordering dependencies
Pair-specific challenges
Migration approach
Audit Dental-Exec data model and export files
Before any mapping work begins, FlitStack AI audits your Dental-Exec export files to understand the structure of patient records, provider data, treatment histories, appointment logs, and insurance data. We identify missing fields, inconsistent date formats, and duplicate records during this phase. The audit produces a data quality report and flags any fields that cannot be extracted from the standard export — those require a supplemental export request to Dental-Exec support. This step typically takes 2–4 business days depending on data volume.
Design Salesforce schema with custom fields and custom objects
FlitStack AI designs the Salesforce schema based on the audit findings. We create the Dental_Specialty__c pick-list on Contact, the Provider_Patient_Junction__c junction object, and custom objects for Treatment_Plan__c, Treatment_History__c, Clinical_Note__c, and Billing_Record__c. Each custom field receives the correct data type (text, pick-list, currency, date, lookup) before data loads begin. We deliver a schema setup plan so your Salesforce admin can review and approve field definitions before we proceed.
Transform data and resolve owner/provider lookups
We transform Dental-Exec records into Salesforce format: patient records become Accounts, providers become Contacts, appointments become Events or Tasks, and treatment data lands in custom objects. Primary providers are resolved via lookup to the corresponding Contact record. Insurance carriers are linked to patient Accounts via the Insurance_Carrier__c custom lookup. Any records without a matching Salesforce user (by email) are flagged before migration so your admin can provision access or assign a fallback owner.
Run sample migration with field-level diff
A representative slice of records — typically 50–200 spanning patients, providers, appointments, and a few treatment histories — migrates into a Salesforce sandbox first. We generate a field-level diff comparing each source field to its destination counterpart so you can verify specialty mapping, provider relationship resolution, treatment date preservation, and insurance data linkage before the full run. You review and approve the diff; we adjust mapping logic if any discrepancies are found.
Execute full migration with delta-pickup window
The full migration runs against your Salesforce production org using the Salesforce Bulk API for high-volume ingestion. Your team continues working in Dental-Exec during this time — FlitStack AI uses read-only access only. A delta-pickup window (typically 24–48 hours after the full load) captures any records created or modified during the cutover so Salesforce reflects your final state at go-live. Audit logs document every record created, updated, or skipped; one-click rollback is available if reconciliation finds discrepancies.
Platform deep dives
Dental-Exec
Source
Strengths
Weaknesses
Salesforce Sales Cloud
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Dental-Exec and Salesforce Sales Cloud.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Dental-Exec: Not publicly documented.
Data volume sensitivity
Dental-Exec doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Dental-Exec to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
Walk through your Dental-Exec to Salesforce Sales Cloud migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Dental-Exec
Other ways to arrive at Salesforce Sales Cloud
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.