CRM migration
Field-level mapping, validation, and rollback between DentAdmin and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.
DentAdmin
Source
Salesforce Sales Cloud
Destination
Compatibility
11 of 12
objects map 1:1 between DentAdmin and Salesforce Sales Cloud.
Complexity
BStandard
Timeline
72–96 hours
Overview
DentAdmin stores patient records, appointments, treatment plans, insurance data, and practice communications in a dental-vertical schema built around Belgian healthcare coding (RZIV codes). Salesforce Sales Cloud has no native dental object model — Contacts, Accounts, Opportunities, and Cases form the standard CRM structure, with custom objects and fields handling specialty data. The migration maps DentAdmin patients to Salesforce Contacts, DentAdmin providers to Salesforce Users with role-based assignments, and DentAdmin treatment plans to Salesforce Opportunities or a custom Dental_Treatment_Plan__c object depending on how the practice structures its sales process. Appointment history migrates as Salesforce Events with original start/end times preserved. Insurance information, RZIV codes, and multi-site assignments migrate as custom fields on Contact and Account. FlitStack AI sequences the migration so foreign-key dependencies resolve correctly: Accounts first, then Contacts with AccountId lookups, then Opportunities with Contact Roles. The delta-pickup window captures in-flight changes during cutover, and an audit log documents every operation. Workflows, SMS automations, and Outlook calendar sync rules do not migrate — those must be rebuilt in Salesforce Flow or documented for manual reconfiguration.
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 DentAdmin 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.
DentAdmin
Patient
Salesforce Sales Cloud
Contact
1:1DentAdmin Patient records map to Salesforce Contact. The patient's primary address, phone, email, and date of birth migrate as standard Contact fields. Multi-site assignments in DentAdmin migrate as a custom Multi_Site_Practice__c pick-list field on Contact. Unmatched patients with missing email receive a generated placeholder address and are flagged for manual review before go-live.
DentAdmin
Patient Insurance
Salesforce Sales Cloud
Account + Custom Field on Contact
many:1Insurance provider from DentAdmin maps to a Salesforce Account record (the insurer). The patient's insurance policy number, coverage tier, and RZIV entitlements migrate as custom fields on the Contact (Insurance_Policy_Number__c, RZIV_Coverage_Tier__c, RZIV_Entitlement__c). Insurer name links to Account via AccountId lookup. If the insurer is not already in Salesforce as an Account, a placeholder Account is created and flagged for the admin to populate.
DentAdmin
Treatment Plan
Salesforce Sales Cloud
Opportunity
1:1Treatment plans in DentAdmin contain procedure codes (RZIV), treatment descriptions, estimated costs, and status. These map to Salesforce Opportunity with Name derived from patient name + treatment type, Amount from total estimated cost, and Stage from DentAdmin status (Draft → 'Prospecting', Active → 'Value Proposal', Completed → 'Closed Won'). RZIV procedure codes migrate as custom Opportunity fields (RZIV_Procedure_Code__c, RZIV_Line_Item__c) since Salesforce Opportunity Products require a Price Book entry for each procedure code.
DentAdmin
Appointment
Salesforce Sales Cloud
Event
1:1DentAdmin appointments map to Salesforce Events with WhoId linked to the Contact record and original start/end times preserved. Appointment type (check-up, procedure, consultation) migrates as Event Type. Provider name maps to Event OwnerId resolved by email match to Salesforce Users. Multi-site location stored as custom Location__c field on Event. Outlook calendar sync behavior is not replicated — Salesforce Events do not push to Outlook automatically without third-party AppExchange apps.
DentAdmin
Provider / Dentist
Salesforce Sales Cloud
User
1:1DentAdmin provider records map to Salesforce Users by email match. Provider specialty (orthodontist, periodontist, general dentist) migrates as a custom Title or Department field. If a provider in DentAdmin does not have a corresponding Salesforce User license, their records are assigned to a fallback admin User and flagged in the migration report so the practice can provision the license before go-live.
DentAdmin
SMS / Communication Log
Salesforce Sales Cloud
Task
1:1DentAdmin SMS history and communication logs migrate as Salesforce Tasks with Type = 'SMS' or 'Email', Subject derived from the communication type, and the original body preserved in Description. Timestamps and sender/recipient information migrate as custom fields (SMS_Direction__c, SMS_Sent_Date__c). Salesforce does not send SMS natively — a third-party AppExchange app (such as Sarbacane or DialedIn) must be installed post-migration to enable outbound SMS.
DentAdmin
Invoice / Billing Record
Salesforce Sales Cloud
Custom Object: Dental_Invoice__c
1:1DentAdmin invoices contain line items, payment status, and insurance reimbursement data that have no standard Salesforce equivalent. FlitStack AI creates a custom Dental_Invoice__c object with fields for Invoice_Number__c, Invoice_Date__c, Amount__c, Payment_Status__c, Insurance_Reimbursement__c, and RZIV_Code__c. The invoice is linked to the Contact record via a lookup. Invoices that were fully reimbursed via RZIV are marked Paid in the custom object.
DentAdmin
Document / Attachment
Salesforce Sales Cloud
Salesforce Files
1:1DentAdmin file attachments (treatment consent forms, imaging files, referral letters) are downloaded and re-uploaded to Salesforce Files linked to the Contact record. File size limits of 25MB per Salesforce file apply; files exceeding this limit are split or linked via external URL in a custom External_Document_Link__c field. Inline images embedded in DentAdmin notes are extracted and saved as separate Salesforce Files.
DentAdmin
Custom Patient Field (RZIV-specific)
Salesforce Sales Cloud
Custom Field on Contact
1:1DentAdmin allows custom fields per patient for RZIV-specific tracking (such as Orthodontic_Waiting_Period__c or Implant_Coverage__c). Each custom field in DentAdmin is assessed by data type: pick-lists become Salesforce pick-list fields, text fields become text fields, date fields become date fields. All custom fields receive the __c suffix and are named with the original DentAdmin field label translated to Salesforce naming conventions (no spaces, underscores between words).
DentAdmin
Multi-Site Practice
Salesforce Sales Cloud
Territory + Account Hierarchy
1:1DentAdmin supports practices with 10+ sites under a single account. Each site in DentAdmin maps to a Salesforce Account record in a parent-child hierarchy under the master practice Account. Salesforce Territories are created per site to scope sharing rules, record access, and reporting. Users are assigned to Territories based on the site they manage in DentAdmin, so appointment data and patient records are visible only to the relevant site's team in Salesforce.
DentAdmin
Appointment Reminder Rules
Salesforce Sales Cloud
Flow (rebuild required)
1:1DentAdmin automated appointment reminder SMS and email sequences do not have a Salesforce equivalent. These are documented in the migration handoff package with DentAdmin rule logic (trigger timing, message templates, patient segments) so the Salesforce admin can rebuild them in Salesforce Flow or install an AppExchange reminder app. FlitStack does not migrate automation logic — only the configuration documentation is preserved.
DentAdmin
Outlook Calendar Sync (CLICKDOC)
Salesforce Sales Cloud
AppExchange calendar app (rebuild required)
1:1DentAdmin's CLICKDOC integration syncs the dental calendar bidirectionally with MS Outlook. Salesforce does not offer native Outlook calendar sync at the Event object level. A third-party AppExchange app (such as Outlook4Salesforce or RelateIQ Calendar Sync) must be installed post-migration to replicate this behavior. FlitStack provides a setup guide referencing compatible AppExchange products so the admin can configure the sync after data migration completes.
| DentAdmin | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| Patient | Contact1:1 | Fully supported | |
| Patient Insurance | Account + Custom Field on Contactmany:1 | Fully supported | |
| Treatment Plan | Opportunity1:1 | Fully supported | |
| Appointment | Event1:1 | Fully supported | |
| Provider / Dentist | User1:1 | Fully supported | |
| SMS / Communication Log | Task1:1 | Fully supported | |
| Invoice / Billing Record | Custom Object: Dental_Invoice__c1:1 | Fully supported | |
| Document / Attachment | Salesforce Files1:1 | Fully supported | |
| Custom Patient Field (RZIV-specific) | Custom Field on Contact1:1 | Fully supported | |
| Multi-Site Practice | Territory + Account Hierarchy1:1 | Fully supported | |
| Appointment Reminder Rules | Flow (rebuild required)1:1 | Fully supported | |
| Outlook Calendar Sync (CLICKDOC) | AppExchange calendar app (rebuild required)1: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.
DentAdmin gotchas
No publicly documented REST API for DentAdmin
Pricing is opaque and requires direct contact
RIZIV code version drift between systems
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
Pre-migration schema design for Salesforce Territories and custom objects
Before extracting any DentAdmin data, FlitStack works with the practice admin to map the multi-site structure to Salesforce Territories, define the custom Dental_Invoice__c object schema, and confirm RZIV code value-mapping lists. We deliver a Salesforce setup checklist covering Territory creation, sharing rule configuration, the Dental_Invoice__c custom object fields, and RZIV pick-list values so the Salesforce org is ready before data lands. This step typically takes 3–5 business days and requires a Salesforce admin with Modify All Data permissions.
Extract DentAdmin patient records, appointments, treatment plans, and insurance data
FlitStack connects to the DentAdmin API using scoped read access (read-only credentials scoped to the migration project). We extract all Patient records with custom fields, Appointment history with provider assignments, Treatment Plans with RZIV codes, Provider records, Invoice data, and file attachments. Multi-site exports are pulled per site to preserve the practice_site field value. The API extraction respects DentAdmin's rate limit of 3,600 calls per hour — for practices with large patient volumes, extraction runs in off-peak hours to avoid hitting the quota during business operations.
Resolve provider-to-user mapping and insurance provider-to-account mapping
DentAdmin provider records are matched to Salesforce Users by email. If a provider in DentAdmin does not have a corresponding Salesforce User, FlitStack flags the record and assigns it to a designated fallback admin User. Insurance providers from DentAdmin are matched to existing Salesforce Accounts; if no match exists, a placeholder Account is created and flagged for the admin to populate with correct billing address and contact details. This step prevents orphan records and ensures Contact.AccountId lookups resolve correctly before Opportunity creation.
Run sample migration with field-level diff across all object types
A representative slice of 100–500 records — spanning patients across multiple sites, appointments of each type, treatment plans at various stages, and a sample of invoices — migrates first into a Salesforce sandbox. FlitStack generates a field-level diff report comparing DentAdmin source values against Salesforce destination values for every mapped field. The practice admin reviews the diff to verify RZIV code mapping, appointment owner assignment, multi-site visibility, and invoice payment status. Any mapping errors are corrected before the full run commits.
Execute full migration with delta-pickup window and audit log
The full DentAdmin dataset migrates into Salesforce using Bulk API for high-volume objects (Events, Tasks) and REST API for smaller objects (Contacts, Opportunities, custom objects). A delta-pickup window of 24–48 hours runs concurrently, capturing any DentAdmin records modified or created during the migration window. FlitStack generates an audit log listing every record created, every field populated, every RZIV code mapped, and every file re-uploaded to Salesforce Files. If reconciliation reveals missing records, the delta-pickup resolves them automatically before go-live.
Post-migration handoff: workflow documentation and AppExchange setup guide
FlitStack delivers a migration handoff package containing: (1) complete field-mapping CSV with transformation notes, (2) DentAdmin automation documentation for rebuilding appointment reminders and SMS sequences in Salesforce Flow, (3) AppExchange compatibility guide for Outlook calendar sync (CLICKDOC replacement) and SMS sending, (4) RZIV code value-mapping reference sheet, and (5) a rollback procedure with snapshot-based restore instructions. The package is handed off to the Salesforce admin for final configuration and user acceptance testing before the practice goes live on Salesforce.
Platform deep dives
DentAdmin
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 DentAdmin 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
DentAdmin: Not publicly documented.
Data volume sensitivity
DentAdmin 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 DentAdmin to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
Walk through your DentAdmin 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 DentAdmin
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.