CRM migration
Field-level mapping, validation, and rollback between Henry Schein One and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Henry Schein One
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between Henry Schein One and Freshsales.
Complexity
BStandard
Timeline
5–10 business days
Overview
Henry Schein One organizes dental practices around patients, appointments, treatment plans, and clinical imaging — a vertical model built for chairside workflows. Freshsales is a horizontal CRM built for sales teams managing leads, accounts, and deals through pipeline stages. These are fundamentally different data architectures, which means the migration requires deliberate decisions about what patient data becomes contact data, what treatment history becomes notes, and what has no equivalent at all. FlitStack AI extracts patient demographics, contact information, insurance records, treatment history, and financial ledgers from Henry Schein One via its API Exchange (700 endpoints, SOC 2 Type II compliant). We map these to Freshsales standard objects — Contacts, Accounts, Leads, and Deals — plus custom fields for dental-specific data that has no native CRM equivalent. Clinical notes, perio charts, and imaging references migrate as formatted notes or attachment links. Insurance plan data becomes custom fields on accounts. What does not migrate: Henry Schein One workflows, automated appointment reminders, imaging files (X-rays, CBCT scans), and third-party integrations with imaging hardware or lab partners. These require rebuild or reconfiguration in Freshsales or complementary tools. Our export-for-rebuild package documents your existing automation logic so your team can reconstruct workflows in Freshsales' automation builder or a connected tool. The migration runs against Freshsales' REST API with rate-limit awareness (Freshworks enforces per-app and org-level constraints). A delta-pickup window captures any records modified during cutover, and a sample migration with field-level diff validates mapping before the full run commits.
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 Henry Schein One 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.
Henry Schein One
Patient / Patient Chart
Freshsales
Contact
1:1Patient demographics including name, date of birth, address, phone number, and email map directly to Freshsales Contact fields. The patient's primary dental provider is matched to the Contact's Owner field via email resolution. Each patient chart in Henry Schein One generates exactly one Contact record in Freshsales, preserving the complete demographic profile.
Henry Schein One
Patient Responsible Party
Freshsales
Account
1:1The financially-responsible party for each patient maps to a Freshsales Account record. When the responsible party is an individual person, the Account stores that individual as the account name with type set to 'Customer'. Insurance plan holders who are not the patient themselves become separate Account records for accurate coverage tracking.
Henry Schein One
Insurance Plan / Coverage
Freshsales
Account (custom fields)
1:1Insurance carrier name, plan type, group number, member ID, and coverage percentages migrate as custom fields on the Account record. Freshsales has no native insurance object, so all insurance data lives in custom fields or as linked custom object records. For dual-coverage patients, primary and secondary plans require careful field placement to avoid data overlap.
Henry Schein One
Treatment Plan
Freshsales
Deal (custom fields) + Note
1:1Proposed and completed dental procedures map to a Freshsales Deal with custom fields capturing procedure codes (CDT codes), treating provider, and treatment date. Long-form treatment notes and clinical observations attach as Freshsales Notes with the original timestamp and provider attribution fully preserved for audit continuity.
Henry Schein One
Appointment / Schedule
Freshsales
Event / Task
1:1Historical appointments map to Freshsales Events with start and end time, assigned provider as the event assignee, and patient contact link. Automated reminders attached to future appointments do not migrate since Freshsales Workflows must be rebuilt. Past appointments become read-only historical records in Freshsales for reference purposes.
Henry Schein One
Ledger Entry / Payment Record
Freshsales
Deal (custom fields) + Note
many:1Ledger entries including charges, payments, adjustments, and insurance write-offs are too granular for Freshsales native objects. We consolidate them into a Deal record with custom currency fields for total charges, total payments, balance due, and write-off amounts, then attach the complete ledger history as a structured PDF note.
Henry Schein One
Clinical Note / Progress Note
Freshsales
Note
1:1Clinical notes migrate as Freshsales Notes with the provider identified as the note author and the patient Contact set as the parent record. Rich text formatting is preserved as plain text with line breaks maintained. Original note timestamps are stored in a custom datetime field for chronological accuracy.
Henry Schein One
Perio Chart
Freshsales
Custom Object
1:1Perio measurements including pocket depths, recession, mobility, and BOP have no Freshsales native equivalent. We create a Perio_Chart__c custom object with numeric fields for each tooth surface and a lookup relationship to the Contact. Historical perio snapshots are stored as dated records within this custom object for longitudinal tracking.
Henry Schein One
Imaging Reference / X-Ray File Link
Freshsales
File / Note (link)
1:1Actual image files including X-rays, intraoral photos, and CBCT scans stored in Henry Schein One's proprietary format cannot be opened in Freshsales. We migrate the file name, original capture date, and a reference link as a Note attachment. The files themselves must be exported separately and rehosted in Freshsales Files or a connected imaging viewer application.
Henry Schein One
Recall / Maintenance Record
Freshsales
Task (recurring)
1:1Recall intervals such as six-month hygiene recalls or annual perio maintenance map to Freshsales Tasks with a due date calculated from the most recent recall date. Recurring task automation does not migrate automatically. Freshsales Workflows on Pro+ plans can recreate the automated recall reminder functionality based on the stored interval data.
Henry Schein One
Inventory / Supply Item
Freshsales
Product
1:1Henry Schein One supply catalog items including dental materials, equipment, and consumables map to Freshsales Products with the product name, SKU, unit price, and description. Products can be linked to Deals via the Deal Product junction object for treatment-based billing workflows and revenue attribution.
Henry Schein One
Provider / Staff User
Freshsales
User (Freshsales agent)
1:1Henry Schein One staff records resolve to Freshsales Users by matching email addresses. Unmatched providers are flagged in a pre-migration report for manual resolution. Provider specialties and license numbers migrate as custom fields on the User record for compliance tracking and reporting purposes.
| Henry Schein One | Freshsales | Compatibility | |
|---|---|---|---|
| Patient / Patient Chart | Contact1:1 | Fully supported | |
| Patient Responsible Party | Account1:1 | Fully supported | |
| Insurance Plan / Coverage | Account (custom fields)1:1 | Fully supported | |
| Treatment Plan | Deal (custom fields) + Note1:1 | Fully supported | |
| Appointment / Schedule | Event / Task1:1 | Fully supported | |
| Ledger Entry / Payment Record | Deal (custom fields) + Notemany:1 | Fully supported | |
| Clinical Note / Progress Note | Note1:1 | Fully supported | |
| Perio Chart | Custom Object1:1 | Fully supported | |
| Imaging Reference / X-Ray File Link | File / Note (link)1:1 | Fully supported | |
| Recall / Maintenance Record | Task (recurring)1:1 | Fully supported | |
| Inventory / Supply Item | Product1:1 | Fully supported | |
| Provider / Staff User | User (Freshsales agent)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.
Henry Schein One gotchas
Proprietary image encoding breaks image links post-migration
Insurance EDI re-enrollment required with every payer
API Exchange restrictions limit third-party data access
PCI compliance does not transfer between systems
Jarvis Analytics generates derived data that does not export
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 Henry Schein One data inventory and design Freshsales schema
We connect to your Henry Schein One API Exchange account and inventory all patient records, insurance plans, treatment histories, ledger entries, appointments, and staff accounts. Simultaneously, we audit your target Freshsales plan (Growth, Pro, or Enterprise) to identify which custom fields are available and which require custom object creation. We deliver a schema design document specifying every custom field, custom object, and record type your Freshsales instance needs before data lands.
Create Freshsales custom fields and objects
Your Freshsales admin creates the custom fields and custom objects specified in the schema design document — Insurance_Carrier__c, CDT_Code__c, Perio_Chart__c, Original_Created_Date__c, and all other dental-specific fields. If you use Freshsales Pro or Enterprise, we can create these programmatically via the REST API. Standard profile permissions must be updated to expose the new fields on the appropriate page layouts for Contacts, Accounts, and Deals before migration validation begins.
Resolve staff users and assign ownership
Henry Schein One staff records are matched to Freshsales Users by email address. We run an ownership resolution pass before any data is written — any provider without a corresponding Freshsales User is flagged in a pre-migration report. Your team creates the missing User accounts or confirms a fallback owner assignment. No Contact, Account, or Deal lands without a valid Freshsales owner.
Run sample migration with field-level diff
A representative slice — typically 200–500 patient records spanning different account types, insurance scenarios, and treatment volumes — migrates first. We generate a field-level diff comparing source values to destination field values for every mapped column. You review the diff to confirm insurance mapping, treatment history placement, and perio chart structure before the full run is authorized. Any mapping corrections are made before the production migration.
Execute full migration with delta-pickup cutover
The full record set migrates in sequenced batches: responsible parties (Accounts), patients (Contacts), insurance plans (custom fields), treatment records (Deals), appointments (Events), and ledger history (Deal custom fields + notes). During cutover, your team continues working in Henry Schein One. A delta-pickup window of 24–48 hours captures any records created or modified after the migration snapshot. An audit log records every insert and update operation. One-click rollback is available if reconciliation finds unexpected data quality issues.
Platform deep dives
Henry Schein One
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 Henry Schein One 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
Henry Schein One: Not publicly documented per-org limits; enterprise customers receive dedicated API capacity.
Data volume sensitivity
Henry Schein One exposes a bulk API — large-volume migrations stream efficiently.
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 Henry Schein One to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Henry Schein One 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 Henry Schein One
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.