CRM migration
Field-level mapping, validation, and rollback between Dental-Exec and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Dental-Exec
Source
Freshsales
Destination
Compatibility
12 of 13
objects map 1:1 between Dental-Exec and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
Dental-Exec serves dental practices and DSO organizations with a practice-management-flavored CRM that stores patient records, referring dentist contacts, treatment-case deals, and dental-procedure custom fields. Freshsales organizes data around Lead, Contact, Account, Deal, and Sales Activity objects with a Kanban pipeline view and Freddy AI scoring available on Pro and Enterprise plans. We map Dental-Exec contacts to Freshsales Contacts (or Leads for unreached prospects), dental practice companies to Freshsales Accounts, treatment cases to Freshsales Deals, and dental-procedure custom fields to Freshsales custom fields. We preserve original create and modified timestamps as custom datetime fields since Freshsales overwrites CreatedDate at migration time. We surface dental-specific taxonomy—ADA codes, insurance carriers, treatment-stage pick-lists—as export-for-rebuild reference so your Freshsales admin can configure Freshsales pipelines and pick-list values that mirror your case workflow before go-live. The migration runs via scoped read access on Dental-Exec and bulk upsert into Freshsales, with a 24–48 hour delta-pickup window capturing in-flight changes during cutover.
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 Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Dental-Exec
Contact (Patient)
Freshsales
Contact
1:1Dental-Exec patient contacts migrate to Freshsales Contact. The patient's primary practice association maps to AccountId via the contact's linked dental practice. Phone, email, address, and job title fields migrate directly. Dental-Exec contact IDs preserved as Source_System_ID__c for delta-run de-duplication. This ID also enables audit trail across migrations.
Dental-Exec
Contact (Uncontacted Prospect)
Freshsales
Lead
1:manyDental-Exec contacts with no scheduled appointment and status 'Referral Only' or 'Cold Prospect' route to Freshsales Lead. This split happens during migration based on Dental-Exec contact status field value. The lead's source dentist or practice name maps to Lead Company field.
Dental-Exec
Contact (Referring Dentist)
Freshsales
Contact
1:1Dental-Exec referring-dentist contacts migrate to Freshsales Contact with a Referrer__c custom checkbox set to true. Their practice name becomes the Account lookup. Referring-dentist notes and specialty fields map to custom text fields on the Contact. We also capture the dentist’s NPI number in a separate custom field for compliance verification.
Dental-Exec
Company / Practice
Freshsales
Account
1:1Dental-Exec dental practice companies migrate to Freshsales Account. Practice name maps to Account Name. Website, address, phone, and industry ('Healthcare / Dental') migrate directly. Multi-location dental groups require Account hierarchies via ParentId when Dental-Exec stores parent-organization relationships. We also preserve the original practice identifier as Source_System_ID__c for future reference.
Dental-Exec
Deal / Treatment Case
Freshsales
Deal
1:1Dental-Exec treatment cases migrate to Freshsales Deals with the dental practice as AccountId and the patient as ContactId. Deal amount represents the case value. Deal stage maps to Freshsales pipeline stage values via value-by-value mapping per pipeline. We preserve original case-create date as Original_Create_Date__c since Freshsales Deal CreatedDate reflects migration time.
Dental-Exec
Treatment Case Pipeline
Freshsales
Deal Pipeline
1:1Dental-Exec case status workflows become Freshsales Deal Pipelines. Each Dental-Exec status type (Restorative, Ortho, Perio, Oral Surgery) can become its own Freshsales pipeline so stage pick-list values are scoped per treatment type. Pipeline configuration is delivered as a setup plan before data lands.
Dental-Exec
Task / Appointment
Freshsales
Sales Activity / Appointment
1:1Dental-Exec scheduled appointments map to Freshsales Appointments with original start/end times, owner, and linked ContactId preserved. Pre-appointment tasks (e.g., insurance verification) migrate as Freshsales Tasks with due date and status. Original Dental-Exec activity timestamps preserved for reporting continuity. All activity records retain their source IDs for traceability.
Dental-Exec
Note / Clinical Note
Freshsales
Note
1:1Dental-Exec clinical notes and general notes migrate to Freshsales Notes linked to the appropriate Contact or Deal. Rich-text formatting is preserved where the source exports allow. Notes created by specific users map to Freshsales owner by email match. Each note includes a link to its originating record for quick navigation.
Dental-Exec
Custom Field: ADA Procedure Codes
Freshsales
Custom Field (Deal)
1:1Dental-Exec custom fields storing ADA procedure codes (DXXXX format) migrate to Freshsales custom text fields on the Deal object. We cannot map procedure codes to Freshsales native pick-lists without Freshsales admin configuring the pick-list values. The mapping plan identifies every ADA code in use for admin configuration before migration.
Dental-Exec
Custom Field: Insurance Carrier
Freshsales
Custom Field (Contact/Deal)
1:1Dental-Exec insurance carrier custom fields map to Freshsales custom pick-list or text fields on Contact (primary insured) and Deal (case-level insurance). Carrier name value mapping is required when Dental-Exec uses free-text and Freshsales wants pick-list for reporting. We flag inconsistent carrier spellings for cleanup during migration.
Dental-Exec
Custom Field: Claim Status
Freshsales
Custom Field (Deal)
1:1Dental-Exec claim status flags (Submitted, Pending, Paid, Denied, Appeal) map to Freshsales custom pick-list values on the Deal. Each Dental-Exec status value gets a corresponding Freshsales pick-list entry. Claim status change dates migrate as additional custom datetime fields for audit trail.
Dental-Exec
User / Owner
Freshsales
User
1:1Dental-Exec user records resolve to Freshsales users by email match. Unmatched owners are flagged before migration — the team either invites them to Freshsales first or assigns their records to a fallback user. No record lands in Freshsales without a valid OwnerId.
Dental-Exec
Attachment / Document
Freshsales
File / Attachment
1:1Dental-Exec file attachments (treatment plan PDFs, insurance cards, consent forms) re-upload to Freshsales Files linked to the appropriate Contact or Deal record. We handle file download, re-upload, and re-link as part of the migration. Large files may be subject to Freshsales storage limits on the target plan.
| Dental-Exec | Freshsales | Compatibility | |
|---|---|---|---|
| Contact (Patient) | Contact1:1 | Fully supported | |
| Contact (Uncontacted Prospect) | Lead1:many | Fully supported | |
| Contact (Referring Dentist) | Contact1:1 | Fully supported | |
| Company / Practice | Account1:1 | Fully supported | |
| Deal / Treatment Case | Deal1:1 | Fully supported | |
| Treatment Case Pipeline | Deal Pipeline1:1 | Fully supported | |
| Task / Appointment | Sales Activity / Appointment1:1 | Fully supported | |
| Note / Clinical Note | Note1:1 | Fully supported | |
| Custom Field: ADA Procedure Codes | Custom Field (Deal)1:1 | Fully supported | |
| Custom Field: Insurance Carrier | Custom Field (Contact/Deal)1:1 | Fully supported | |
| Custom Field: Claim Status | Custom Field (Deal)1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Attachment / Document | File / Attachment1: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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Discovery and schema pre-mapping
We connect to Dental-Exec via scoped read access and export all object records: contacts, companies, deals, activities, and custom field definitions. We simultaneously export your Freshsales schema (standard fields, existing custom fields, pipeline configurations, pick-list values). We produce a pre-mapping document that shows every Dental-Exec field, its Freshsales destination, mapping type, and any value-mapping tables needed. Your team reviews and approves before we touch any destination data.
Freshsales account provisioning and user resolution
Your Freshsales tenant is provisioned at the agreed plan tier. We resolve Dental-Exec owner email addresses against Freshsales user list by email match. Unmatched owners are flagged — your team either creates Freshsales users for them or assigns a fallback owner. No record migrates without a valid Freshsales owner. We also create all required custom fields identified in the pre-mapping phase before the data import begins.
Account and hierarchy migration first
We sequence the migration to respect Freshsales foreign-key constraints. Accounts (dental practices) migrate first, establishing the Account records that contacts and deals will link to. For DSO setups with parent-organization relationships, we migrate parent accounts before child accounts to resolve Parent Account lookups. We run a sample of 50–100 accounts first and generate a field-level diff for your review before committing the full Account migration.
Contact and Lead split migration
Dental-Exec contacts split by lifecycle_role: patients and referring dentists become Freshsales Contacts linked to the appropriate Account. Cold prospects and unreached referrals become Freshsales Leads. The split logic is rule-based (determined from the lifecycle_role and status values in discovery) and documented in the pre-mapping. We migrate in batches of 1,000–5,000 records with error logging per batch. Each batch is validated against source counts, and any mismatches trigger a review before committing to Freshsales.
Deal and Sales Activity migration with delta window
Treatment cases migrate as Freshsales Deals linked to Account and primary Contact. Activities (appointments, tasks, notes) migrate as Freshsales Appointments and Notes with original timestamps and owner links. After the initial bulk migration, we open a 24–48 hour delta window. Any record modified or created in Dental-Exec during this window is upserted into Freshsales so the final state reflects your last Dental-Exec update. Audit log records every operation.
Validation, reconciliation report, and rollback window
We generate a reconciliation report comparing Dental-Exec record counts, field values, and date ranges against Freshsales. You verify deal amounts, contact email addresses, and pipeline stage assignments. One-click rollback is available for 48 hours after go-live if reconciliation identifies unexpected gaps. We also deliver the export-for-rebuild reference: Dental-Exec workflow definitions, ADA procedure code lists, and insurance carrier names in a structured format your Freshsales admin uses to configure pipelines, pick-lists, and automation rules.
Platform deep dives
Dental-Exec
Source
Strengths
Weaknesses
Freshsales
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 Freshsales.
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 Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Dental-Exec to Freshsales 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 Freshsales
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.