CRM migration
Field-level mapping, validation, and rollback between Henry Schein One and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Henry Schein One
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Henry Schein One and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Henry Schein One is a dental-practice-management platform centered on patient records, clinical workflows, treatment plans, insurance ledgers, and imaging — built for front-office and clinical teams inside a dental practice. Nutshell is a sales CRM built around People, Accounts, Leads, Deals, and Activity tracking for small-to-mid-market sales teams. The two systems share almost no object vocabulary, which makes this one of the more structurally divergent migrations in our catalog. We extract patient demographics, insurance carrier and plan data, appointment timestamps, treatment-plan summaries, and ledger balances from Henry Schein One via its API Exchange (700+ endpoints, 6 billion annual requests). For each patient, we create a corresponding Nutshell Person record. Dental-specific properties — insurance group numbers, treatment plan status, outstanding balance, last-visit date — migrate as Nutshell custom fields on the Person object. Appointment history converts to Nutshell Activity records with original timestamps and assigned owner. Clinical notes, perio chart summaries, and treatment summaries migrate as Nutshell Notes attached to the Person. Dental imaging (x-rays, intraoral photos, CBCT scans) and proprietary image references require a separate migration path: we extract file references and re-upload images to Nutshell's file storage with person-level associations. Clinical note templates, treatment-planning workflows, insurance verification rules, and appointment reminder sequences do not migrate — those are platform-specific logic that must be rebuilt manually in Nutshell's workflow tools. We export Henry Schein One workflow definitions as a rebuild reference for your team.
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 Nutshell, 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
Nutshell
Person
1:1Each Henry Schein One patient chart maps to one Nutshell Person record. We pull first name, last name, date of birth, phone, email, address, and guarantor information. The patient's source system ID is stored in a custom field on the Nutshell Person for delta-run deduplication.
Henry Schein One
Insurance Plan / Insurance Ledger
Nutshell
Custom Fields on Person
1:1Henry Schein One insurance records (carrier name, group number, subscriber ID, employer, effective dates, coverage percentages) have no direct Nutshell equivalent. We create custom fields on the Person record — Insurance_Carrier__c, Insurance_Group__c, Insurance_Subscriber_ID__c, Insurance_Effective_Date__c, and Coverage_Percentage__c — to preserve this data.
Henry Schein One
Appointment / Visit Record
Nutshell
Activity
1:1Appointment records (date, time, provider name, procedure codes, operatory, visit type) convert to Nutshell Activity records of type 'Meeting' with the original start/end timestamps and the assigned provider as the Nutshell activity owner. Clinical notes attached to the visit become Notes linked to the same Person.
Henry Schein One
Treatment Plan
Nutshell
Custom Fields + Note on Person
1:1Treatment plan status (proposed, accepted, in-progress, completed), recommended procedures, estimated costs, and provider clinical notes from Henry Schein One migrate as a structured set of custom fields on the Person — specifically Treatment_Plan_Status__c, Last_Treatment_Date__c, and Estimated_Cost__c — with a linked Note containing the complete treatment plan narrative for clinical reference.
Henry Schein One
Ledger / Financial Ledger
Nutshell
Custom Fields on Person
1:1Outstanding balance, last payment date, total production, and total adjustment from the Henry Schein One ledger migrate as numeric custom fields on the Nutshell Person. Current ledger totals serve as a snapshot — Nutshell's accounting module is not a full dental ledger replacement.
Henry Schein One
Referral Source
Nutshell
Custom Field on Person
1:1Referral source (referring doctor name, referral type, referral date) migrates as a custom text field on the Person. This preserves referral tracking history from Henry Schein One, which is important for dental practices that track referring-provider relationships for DSO contract management.
Henry Schein One
Dental Imaging (X-rays, Photos)
Nutshell
File Attachment on Person
1:1We extract image files referenced in the patient chart and re-upload them to Nutshell's file storage, associating each file with the corresponding Person record. Note that Henry Schein One uses proprietary file-naming encoding — we decode file references during extraction. CBCT volumetric files may exceed Nutshell's file size limits and require a separate file-hosting plan.
Henry Schein One
Perio Chart Summary
Nutshell
Note on Person
1:1Periodontal chart summary data (most recent probing depths, bleeding points, recession values) migrates as a structured Note attached to the Person. Full perio chart history is preserved in the note body text — Nutshell does not support chart-specific data types.
Henry Schein One
Clinical Note Templates
Nutshell
Not Migrated
1:1Clinical note templates and clinical-decision support rules are Henry Schein One–specific logic. We export the template field names and structure as a JSON reference document that your team can use to configure equivalent templates in Nutshell's custom note formats or a connected documentation tool.
Henry Schein One
User / Provider / Owner
Nutshell
Person (Team Member)
1:1Henry Schein One provider and staff user records are matched to Nutshell users by email address. Unmatched providers are flagged before migration — your team either creates their Nutshell account first or assigns records to a fallback owner. Provider specialties and license numbers migrate as custom fields on the Person.
Henry Schein One
Marketing / Recall List
Nutshell
Custom Field on Person
1:1Recall status (due, scheduled, lapsed) and next-recall-date from Henry Schein One's hygiene-recall system migrate as custom fields on the Nutshell Person record — Recall_Status__c and Next_Recall_Date__c. After migration, Nutshell's task automation and email sequence tools can be configured to generate automated follow-up reminders and patient outreach based on these recall dates.
Henry Schein One
Integrated Third-Party Tools
Nutshell
Not Migrated
1:1Henry Schein One's imaging integrations with Dexis, Schick, and Carestream imaging systems, lab case management integrations via LinkIt, and payment processing connections are platform-specific links that do not have direct equivalents in Nutshell. These integrations must be re-established separately after migration — either through Nutshell's native integration ecosystem, third-party middleware tools, or as standalone connections to your preferred imaging PACS, lab case, and payment processing platforms.
| Henry Schein One | Nutshell | Compatibility | |
|---|---|---|---|
| Patient / Patient Chart | Person1:1 | Fully supported | |
| Insurance Plan / Insurance Ledger | Custom Fields on Person1:1 | Fully supported | |
| Appointment / Visit Record | Activity1:1 | Fully supported | |
| Treatment Plan | Custom Fields + Note on Person1:1 | Fully supported | |
| Ledger / Financial Ledger | Custom Fields on Person1:1 | Fully supported | |
| Referral Source | Custom Field on Person1:1 | Fully supported | |
| Dental Imaging (X-rays, Photos) | File Attachment on Person1:1 | Fully supported | |
| Perio Chart Summary | Note on Person1:1 | Fully supported | |
| Clinical Note Templates | Not Migrated1:1 | Fully supported | |
| User / Provider / Owner | Person (Team Member)1:1 | Fully supported | |
| Marketing / Recall List | Custom Field on Person1:1 | Fully supported | |
| Integrated Third-Party Tools | Not Migrated1: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
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Audit Henry Schein One data volume and API access scope
Before extraction begins, we connect to the Henry Schein One API Exchange or establish a server-side export connection (for on-premise Dentrix) and audit your patient record count, appointment history depth, insurance record count, and attachment volume. We identify which API credentials are available, whether impersonation mode is enabled, and whether bulk export is supported under your current vendor agreement. This audit produces the record counts and file volumes that determine final pricing and timeline.
Define Nutshell custom field schema for dental data
We create all required custom fields in Nutshell — Insurance_Carrier__c, Insurance_Group_Number__c, Treatment_Plan_Status__c, Outstanding_Balance__c, Recall_Status__c, and others identified in the object mapping — before any data is written. Each custom field gets the correct data type (text, date, number, pick-list) and an optional description so your team understands the field's origin. For multi-location DSO setups, we also add a Practice_Location__c tagging field on the Person object at this stage.
Extract patient records, insurance data, and appointments in dependency order
We extract data in the following sequence: (1) Providers and staff by email for owner resolution, (2) Patients with guarantor and contact information, (3) Insurance records linked to patients, (4) Appointments with procedure codes and provider assignments, (5) Treatment plans and perio chart summaries, (6) Ledger balance snapshots. This sequence ensures that when we write a Nutshell Person record, all linked data (custom fields, activities, notes) can attach to a valid record. Owner resolution runs concurrently — unmatched providers are flagged for your team to create Nutshell accounts or assign to a fallback owner.
Extract and re-upload dental images with person-level associations
Dental imaging files (x-rays, intraoral photos) are decoded from Dentrix's proprietary file-reference format and re-uploaded to Nutshell's file storage. Each file is associated with the corresponding Person record. For CBCT volumetric files exceeding Nutshell's 100 MB file limit, we store a URL reference to your separate file repository (PACS system or S3 bucket) in a custom field rather than uploading the file directly. This step runs in parallel with the data extraction to manage API rate limits.
Run sample migration with field-level reconciliation
A representative sample — typically 100–300 patient records spanning multiple providers, insurance configurations, and appointment histories — migrates into Nutshell first. We generate a field-level reconciliation report comparing source values against destination values for every mapped field, including custom fields, activity timestamps, and note attachments. You verify the mapping before the full migration commits. Any custom field corrections or insurance field additions identified in the sample are applied to the full mapping before the next step.
Execute full migration with delta-pickup window and rollback readiness
The full dataset migrates into Nutshell. During the cutover window (typically 24–48 hours), any new patients added or appointment changes made in Henry Schein One are captured by our delta-pickup process and written to Nutshell before go-live. An audit log records every record written, every custom field populated, and every file uploaded. If reconciliation reveals missing records or mapping errors, one-click rollback reverts the Nutshell instance to its pre-migration state. Post-migration, we deliver a rebuild reference document for clinical note templates and a custom-field setup guide for your Nutshell admin.
Platform deep dives
Henry Schein One
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Nutshell.
Object compatibility
1 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 Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Henry Schein One to Nutshell 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 Nutshell
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.