CRM migration

Migrate from DentAdmin to Salesforce Sales Cloud

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 logo

DentAdmin

Source

Salesforce Sales Cloud

Destination

Salesforce Sales Cloud logo

Compatibility

92%

11 of 12

objects map 1:1 between DentAdmin and Salesforce Sales Cloud.

Complexity

BStandard

Timeline

72–96 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

DentAdmin logo

DentAdmin

What's pushing teams away

  • Limited transparency around subscription pricing makes it difficult for practices to compare cost against alternatives before committing to a contract term.
  • The product appears to have a small market footprint outside Belgium, which limits access to peer reviews, third-party integrations, and specialist support talent.
  • Practices report that the software lacks a well-documented public API, making it difficult to connect with modern third-party tools or automate data workflows.

Choosing

Salesforce Sales Cloud logo

Salesforce Sales Cloud

What's pulling them in

  • The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
  • Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
  • Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
  • Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
  • Organizations with a large, established Salesforce implementation choose it because switching costs — integrations, custom code, trained admins — are prohibitive.

Object mapping

How DentAdmin objects map to Salesforce Sales Cloud

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

maps to

Salesforce Sales Cloud

Contact

1:1
Fully supported

DentAdmin 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

maps to

Salesforce Sales Cloud

Account + Custom Field on Contact

many:1
Fully supported

Insurance 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

maps to

Salesforce Sales Cloud

Opportunity

1:1
Fully supported

Treatment 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

maps to

Salesforce Sales Cloud

Event

1:1
Fully supported

DentAdmin 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

maps to

Salesforce Sales Cloud

User

1:1
Fully supported

DentAdmin 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

maps to

Salesforce Sales Cloud

Task

1:1
Fully supported

DentAdmin 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

maps to

Salesforce Sales Cloud

Custom Object: Dental_Invoice__c

1:1
Fully supported

DentAdmin 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

maps to

Salesforce Sales Cloud

Salesforce Files

1:1
Fully supported

DentAdmin 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)

maps to

Salesforce Sales Cloud

Custom Field on Contact

1:1
Fully supported

DentAdmin 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

maps to

Salesforce Sales Cloud

Territory + Account Hierarchy

1:1
Fully supported

DentAdmin 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

maps to

Salesforce Sales Cloud

Flow (rebuild required)

1:1
Fully supported

DentAdmin 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)

maps to

Salesforce Sales Cloud

AppExchange calendar app (rebuild required)

1:1
Fully supported

DentAdmin'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.

Gotchas + challenges

What specifically takes care here

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 logo

DentAdmin gotchas

High

No publicly documented REST API for DentAdmin

Medium

Pricing is opaque and requires direct contact

Medium

RIZIV code version drift between systems

Salesforce Sales Cloud logo

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

Pair-specific challenges

  • RZIV procedure codes require custom field mapping and cannot use Salesforce standard product catalog

    DentAdmin RZIV codes are Belgian dental insurance procedure identifiers (e.g., 301011, 306071) that map to specific reimbursement amounts. Salesforce has no native RZIV code field. FlitStack migrates these as custom text and pick-list fields on Opportunity (RZIV_Procedure_Code__c, RZIV_Line_Item__c) and Contact (RZIV_Entitlement__c). However, Salesforce Opportunity Products require a Price Book entry for each product — if the practice wants to link RZIV codes to Salesforce Products for revenue reporting, a custom Price Book with dental procedure codes must be built first. This adds a schema setup step before data migration lands.

  • Multi-site DentAdmin practices create data-model fragmentation in Salesforce Territories

    DentAdmin supports practices with 10+ sites on a single account, each with its own providers, schedules, and patient pools. Salesforce Territories manage multi-division access but require explicit configuration: each site must become a Territory, each provider a User assigned to that Territory, and sharing rules scoped to Territory membership. If sharing rules are not configured before migration, patient records and appointments from Site A may be visible to users at Site B by default, violating patient privacy expectations. FlitStack delivers a Territory and sharing-rule setup plan as part of the pre-migration schema design phase.

  • Appointment history volume can trigger Salesforce API rate limits during migration

    A dental practice with 5 years of appointment history may have 50,000–200,000 Event records to migrate. Salesforce Bulk API limits are 15,000 batches per day with 10,000 records per batch. FlitStack uses Bulk API for high-volume Event migration, but practices with appointment histories exceeding 100,000 Events may experience migration duration extending into a second day. We pre-calculate the expected Event volume from DentAdmin export metadata and advise on scheduling the migration window to avoid conflicts with business-hours API usage.

  • DentAdmin SMS logs do not replicate as sendable Salesforce records

    DentAdmin stores SMS communication history linked to patient records. Migrating these as Salesforce Tasks preserves the message content and timestamps for historical reference, but Salesforce Tasks with Type = 'SMS' are not sendable — they are log entries only. If the practice wants to send SMS from Salesforce post-migration, an AppExchange SMS app (e.g., SMS Magic, DialedIn) must be installed and configured separately. FlitStack documents the SMS app options and installation steps in the post-migration handoff guide.

  • DentAdmin Outlook calendar sync (CLICKDOC) has no Salesforce native equivalent

    DentAdmin's CLICKDOC integration bidirectionally syncs the dental practice calendar with MS Outlook so providers see appointments in their personal calendar. Salesforce Events do not push to Outlook without a third-party integration. The migration does not preserve calendar sync behavior — patients, providers, and administrators will need to install an AppExchange calendar sync app (such as Outlook4Salesforce or RelateIQ Calendar Sync) post-migration. FlitStack provides a compatibility guide for AppExchange calendar apps tested with Salesforce Sales Cloud Events.

Migration approach

Six steps for a successful DentAdmin to Salesforce Sales Cloud data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

DentAdmin logo

DentAdmin

Source

Strengths

  • Native Belgian RIZIV-code and health-insurance billing automation reduces administrative overhead for domestic practices.
  • Managed migration service from CGM Belgium handles database import from any prior dental system at onboarding.
  • Explicit GDPR-conformity statement addresses data-privacy compliance requirements for European dental practices.
  • Multi-provider support within a single database accommodates group practices and multi-dentist clinics.

Weaknesses

  • No publicly documented REST API, limiting automated integrations and making programmatic migration more complex.
  • Subscription pricing is not published publicly, requiring direct contact to obtain a quote.
  • Small international footprint outside Belgium reduces availability of peer reviews, community support, and third-party integration plugins.
Salesforce Sales Cloud logo

Salesforce Sales Cloud

Destination

Strengths

  • Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
  • Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
  • Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
  • Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
  • Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

  • Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
  • Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
  • Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
  • API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
  • Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across DentAdmin and Salesforce Sales Cloud.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    DentAdmin: Not publicly documented.

  • Data volume sensitivity

    B

    DentAdmin doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your DentAdmin to Salesforce Sales Cloud migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about DentAdmin to Salesforce Sales Cloud data migrations

Answers to the questions buyers ask most during DentAdmin to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most DentAdmin-to-Salesforce migrations complete in 72–96 hours of clock time for practices with under 25,000 patient records. Multi-site practices with 100,000+ appointment records or complex RZIV-code value mapping extend to 10–14 days. The longest phase is pre-migration schema design (3–5 days) where Salesforce Territories, the Dental_Invoice__c custom object, and RZIV pick-list fields are configured before data extraction begins. The delta-pickup window runs 24–48 hours after the full migration commits to capture any final changes made in DentAdmin during cutover.

Adjacent paths

Related migrations to explore

Ready when you are

Move from DentAdmin.
Land in Salesforce Sales Cloud, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day