CRM migration
Field-level mapping, validation, and rollback between Denticon and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Denticon
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between Denticon and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
Denticon stores dental practice data across patients, providers, appointments, clinical records, billing, insurance claims, and referrals — organized around the treatment workflow rather than the sales pipeline. Freshsales uses the standard CRM object model: leads, contacts, accounts, deals, tasks, events, and custom fields. FlitStack AI maps Denticon patient records to Freshsales contacts, referring practices to accounts, completed appointments to sales activities, and treatment plans to deal records with custom fields capturing clinical detail. The migration extracts data via Denticon's REST APIs (Patients, Appointments, Clinical, RCM) and loads into Freshsales via its CRM API with bulk operations for large record sets. We preserve original create and update timestamps, provider owner assignments, and insurance carrier data as custom fields since Freshsales has no native insurance or clinical-procedure object. Workflows, appointment reminder sequences, and billing automations built in Denticon do not migrate — they require Freshsales workflow and sequence rebuilds. A 24-48 hour delta pickup window captures any appointments or record updates made during the cutover window so Freshsales reflects Denticon's 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 Denticon 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.
Denticon
Patient
Freshsales
Contact
1:1Denticon patient records map directly to Freshsales contacts. The patient demographics (name, date of birth, address, phone, email) translate to Freshsales contact standard fields. Primary dental provider assigned in Denticon resolves to Freshsales contact owner by email match. Original patient create date preserved as custom datetime field since Freshsales CreatedDate reflects migration timestamp.
Denticon
Patient Insurance Record
Freshsales
Custom Fields on Contact
1:1Denticon stores primary and secondary insurance carrier, group number, subscriber ID, and effective dates per patient. Freshsales has no native insurance object. We create custom fields (Insurance_Carrier__c, Group_Number__c, Subscriber_ID__c, Insurance_Effective_Date__c) on the Contact record to preserve this data. Insurance claim history from RCM module migrates as deal custom fields or activity notes.
Denticon
Provider
Freshsales
Freshsales User
1:1Denticon providers (dentists, hygienists, assistants) map to Freshsales users who become record owners. Each provider's email address in Denticon is matched against Freshsales user accounts. Providers without Freshsales access are flagged for admin to create accounts before migration. Provider specialty (GP vs specialist) stored as a custom pick-list field on the user record.
Denticon
Appointment
Freshsales
Sales Activity (Event)
1:1Denticon scheduled appointments map to Freshsales events with the original appointment date, time, duration, provider, and procedure type preserved. Appointment status (completed, no-show, cancelled) maps to Freshsales event status. Future appointments migrate as open events; past appointments as completed events with original timestamps.
Denticon
Treatment Plan
Freshsales
Deal
1:1Denticon treatment plans (proposed procedures with CDT codes, fee estimates, insurance estimates) map to Freshsales deals. The treatment plan total becomes the deal amount. Plan status (proposed, accepted, in-progress, completed) maps to deal stage via value mapping. Individual procedure line items from the plan become deal product records in Freshsales.
Denticon
Clinical Note / Procedure Record
Freshsales
Custom Fields on Deal + Activity Note
1:1Completed clinical procedures (fillings, extractions, root canals) with CDT codes, surfaces, and materials documented in Denticon's clinical module translate to custom fields on the related Freshsales deal and as activity notes. We capture procedure code, tooth number(s), date performed, and provider. This preserves the clinical context that sales reps need when following up on treatment plan deals.
Denticon
Account (Referring Practice)
Freshsales
Account
1:1External referring practices tracked in Denticon's referral module map to Freshsales accounts. Practice name, address, phone, and referring dentist name translate to Freshsales account standard fields. Referral-specific data (referral cost, referral source category) stored as custom fields on the account record.
Denticon
Incoming Referral Record
Freshsales
Task on Account
1:1Individual patient referrals received from external providers tracked in Denticon become tasks on the referring practice's Freshsales account. The task records the referred patient name, referral date, referring provider, and referred procedure type. This gives the account executive visibility into referral volume per practice.
Denticon
RCM Billing Record
Freshsales
Custom Fields on Deal + Activity Note
1:1Insurance claims, payments received, adjustments, and explanation of benefits from Denticon's RCM module link to the corresponding treatment plan deal. We create custom fields for claim status, amount billed, amount paid, adjustment reason, and balance. Payment transactions migrate as activity notes on the deal so the billing history is visible to Freshsales users.
Denticon
Practice Location (OID)
Freshsales
Freshsales Territory + Custom Field on Account
1:manyMulti-location dental organizations running separate office IDs (OIDs) under one Denticon PGID require split mapping. Each OID's patients, providers, and appointments map to Freshsales accounts with a Practice_Location__c custom field. If the organization wants separate Freshsales accounts per location, we create parent-child account hierarchy matching the OID structure.
Denticon
Patient Custom Fields (User-Defined)
Freshsales
Custom Fields on Contact
1:1Denticon supports two user-defined custom fields per patient record (up to 25 alphanumeric characters each) configured in setup screens. These map to Freshsales contact custom fields. The field labels and data types are preserved. Long-text clinical notes that exceed 25 characters migrate as multi-line text custom fields or as activity notes attached to the contact.
Denticon
Appointment Reminder Sequences
Freshsales
No Equivalent
1:1Automated patient communication sequences (appointment reminders via text/email, recall reminders, pre-treatment instructions) built in Denticon do not have a native equivalent in Freshsales CRM. Freshsales has sales sequences for outbound rep communication, not patient appointment reminders. We document the sequence logic for rebuild in Freshsales Chat or a third-party patient communication tool.
| Denticon | Freshsales | Compatibility | |
|---|---|---|---|
| Patient | Contact1:1 | Fully supported | |
| Patient Insurance Record | Custom Fields on Contact1:1 | Fully supported | |
| Provider | Freshsales User1:1 | Fully supported | |
| Appointment | Sales Activity (Event)1:1 | Fully supported | |
| Treatment Plan | Deal1:1 | Fully supported | |
| Clinical Note / Procedure Record | Custom Fields on Deal + Activity Note1:1 | Fully supported | |
| Account (Referring Practice) | Account1:1 | Fully supported | |
| Incoming Referral Record | Task on Account1:1 | Fully supported | |
| RCM Billing Record | Custom Fields on Deal + Activity Note1:1 | Fully supported | |
| Practice Location (OID) | Freshsales Territory + Custom Field on Account1:many | Fully supported | |
| Patient Custom Fields (User-Defined) | Custom Fields on Contact1:1 | Fully supported | |
| Appointment Reminder Sequences | No Equivalent1: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.
Denticon gotchas
PGID Split requires signed agreements and coordination between buyer and seller
Chrome cache and bad shortcuts corrupt patient context between sessions
Custom fields are severely limited to two fields of 25 characters
API writeback scope is limited to specific endpoints
Automated campaign quiet hours restrict message delivery timing
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
Audit Denticon data volume and schema
Before mapping begins, FlitStack AI inventories your Denticon account: total patient count, provider count, appointment volume, treatment plan records, RCM transactions, and active custom fields. We connect to Denticon's REST APIs (Patients, Appointments, Clinical, RCM) using your API credentials to assess record counts and identify data quality issues such as missing email addresses on patient records, duplicate providers, and inactive locations. This audit produces a migration scope document with record counts per object and a list of fields requiring custom field creation in Freshsales.
Provision Freshsales users for all Denticon providers
FlitStack AI generates a provider-to-user mapping report from your Denticon provider list. Each provider's email address is checked against existing Freshsales users. Providers without Freshsales accounts are flagged — your admin must create those user accounts and assign appropriate roles and territories before the migration run. We cannot assign Denticon record ownership to Freshsales users that do not exist. This step prevents owner-resolution failures during the data load and ensures appointment and treatment plan records land with the correct rep in Freshsales.
Create custom fields in Freshsales for dental-specific data
Based on the schema audit, FlitStack AI delivers a custom field creation plan for your Freshsales admin. Required custom fields include Date_of_Birth__c on Contact, Insurance_Carrier__c, Group_Number__c, and Subscriber_ID__c for insurance data, Procedure_Code__c and Tooth_Number__c on Deal and Activity objects, Claim_Status__c and Claim_Amount__c on Deal for RCM data, and Referral_Category__c on Account for referral source classification. We recommend creating these fields before the sample migration runs so field-level validation can execute properly during testing.
Run sample migration with field-level diff
A representative slice of records migrates first — typically 100–500 records spanning patients across multiple providers, appointments in various statuses, treatment plans at different stages, and a sample of RCM transactions. We generate a field-level diff report comparing source Denticon values against the mapped Freshsales values so you can verify owner resolution, insurance field population, procedure code mapping, and pipeline stage assignments before the full run commits. Any field mapping errors are corrected before the production migration begins.
Execute full migration with delta-pickup window
The full record set loads into Freshsales via the CRM API using bulk operations for large record volumes. During cutover, your team continues working in Denticon — we use scoped read access only. A delta-pickup window of 24–48 hours after the initial load captures any appointments scheduled, treatment plans created, or patient records updated during the cutover period. These delta records are merged into Freshsales and deduplicated against the initial load using the Source_System_ID__c field. Audit log captures every operation; one-click rollback reverts to pre-migration state if reconciliation fails.
Platform deep dives
Denticon
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 Denticon 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
Denticon: Not publicly documented in either the legacy reference (api.denticon.com) or the new developer portal pages indexable without authentication. Confirm at partner onboarding..
Data volume sensitivity
Denticon 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 Denticon to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Denticon 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 Denticon
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.