CRM migration

Migrate from Henry Schein One to Nutshell

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 logo

Henry Schein One

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Henry Schein One and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Henry Schein One logo

Henry Schein One

What's pushing teams away

  • Legacy on-premise Dentrix installations accumulate database bloat over time, causing sluggishness that drives practices toward cloud alternatives like Dentrix Ascend or competing platforms.
  • Henry Schein One has tightened integration restrictions — third-party vendors like Vyne Dental report missing API data elements for claims workflows and requirements to discontinue existing integration methods.
  • Practices report difficulty extracting complete data from Dentrix when evaluating a switch, with the migration path treated as a competitive moat rather than an open standard.
  • Annual subscription costs for cloud tiers ($800–$1,400/month) plus module add-ons create budget pressure for small solo practices comparing total cost of ownership.
  • Internal staffing complaints on Glassdoor and Indeed — unattainable targets, finance team issues — reflect onto customer perception of account management and support quality.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Henry Schein One objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Each 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

maps to

Nutshell

Custom Fields on Person

1:1
Fully supported

Henry 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

maps to

Nutshell

Activity

1:1
Fully supported

Appointment 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

maps to

Nutshell

Custom Fields + Note on Person

1:1
Fully supported

Treatment 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

maps to

Nutshell

Custom Fields on Person

1:1
Fully supported

Outstanding 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

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

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

maps to

Nutshell

File Attachment on Person

1:1
Fully supported

We 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

maps to

Nutshell

Note on Person

1:1
Fully supported

Periodontal 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

maps to

Nutshell

Not Migrated

1:1
Fully supported

Clinical 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

maps to

Nutshell

Person (Team Member)

1:1
Fully supported

Henry 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

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Recall 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

maps to

Nutshell

Not Migrated

1:1
Fully supported

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

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.

Henry Schein One logo

Henry Schein One gotchas

High

Proprietary image encoding breaks image links post-migration

High

Insurance EDI re-enrollment required with every payer

Medium

API Exchange restrictions limit third-party data access

Medium

PCI compliance does not transfer between systems

Low

Jarvis Analytics generates derived data that does not export

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Dental imaging file encoding requires decoding before re-upload

    Henry Schein One (Dentrix) stores imaging file references using proprietary internal encoding for x-rays, intraoral photos, and CBCT scans. The file path stored in the patient chart is not a standard filesystem path — it references Dentrix's internal image management system. We decode these references during extraction and re-upload the binary files to Nutshell's file storage. If your practice uses CBCT volumetric files larger than Nutshell's 100 MB per-file limit, those files require a separate file-hosting plan (S3 bucket, PACS system) with a link stored in the Person record.

  • Nutshell has no native insurance data model — custom fields carry all insurance data

    Nutshell does not include a native insurance or benefits object. All insurance data from Henry Schein One — carrier name, group number, subscriber ID, effective dates, coverage percentages — must be stored as custom fields on the Person record. There is no native eligibility check, claim history, or EOB tracking in Nutshell. Your team should plan to either use a dental-specific EDI integration post-migration or accept that insurance verification will run outside Nutshell. We set up all insurance custom fields during migration but do not configure third-party EDI connections.

  • Clinical note templates and treatment-planning logic do not migrate

    Henry Schein One encodes clinical note templates, treatment-planning decision rules, and clinical alerts as platform-specific configuration. These are not data records — they are application logic. Nutshell has no clinical note template system; it supports plain-text Notes and HTML-formatted notes attached to Person records. We export your Henry Schein One template field names and structure as a JSON reference document so your admin can recreate equivalent templates in Nutshell or a connected documentation tool. This is a manual rebuild step your team must plan for.

  • Henry Schein One API Exchange requires vendor partnership for bulk export

    The Henry Schein One API Exchange enforces access controls that require a formal vendor partnership agreement for high-volume programmatic data extraction in some configurations. For practices using on-premise Dentrix (as opposed to Dentrix Ascend cloud), data export may require a server-side connection by a migration engineer rather than a direct API pull. We handle this access complexity during discovery and sequence the extraction accordingly. Practices using Dentrix Ascend cloud can typically authorize API access directly.

  • Multi-location DSO data requires separate Nutshell account scoping

    If your Henry Schein One setup spans multiple practice locations — each with its own patient database, provider roster, and insurance configurations — Nutshell's single-account model requires you to decide how to structure locations: as separate Nutshell accounts (with cross-account reporting challenges), as Nutshell Teams within one account, or as tagging custom fields on Person records. We include a location-tagging step in the migration plan, but the organizational decision on Nutshell account structure must be made before the migration runs.

Migration approach

Six steps for a successful Henry Schein One to Nutshell data migration

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

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

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

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

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

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

Context on both ends of the pair

Henry Schein One logo

Henry Schein One

Source

Strengths

  • Widest installed base of any dental PMS in North America, making integrations and staff familiarity a practical advantage.
  • Integrated ecosystem covering PMS, billing, analytics, marketing, and specialty workflows under one vendor umbrella.
  • API Exchange with SOC 2 Type II compliance and 700 endpoints — meaningful for practices that depend on third-party integrations.
  • Dentrix Ascend eliminates on-premise server hardware and remote desktop dependencies for cloud-oriented practices.
  • OMSVision offers purpose-built surgical scheduling and AAOMS-aligned workflows unavailable in general-purpose dental PMS products.

Weaknesses

  • On-premise Dentrix requires server maintenance, backups, and IT staff that many small practices lack internal capacity to manage.
  • Henry Schein One has restricted third-party API access — Vyne Dental and others cite missing claims workflow data elements and integration discontinuation requirements.
  • Image migration from Dentrix is technically complex due to proprietary file naming, making it the most common source of post-migration data integrity failures.
  • Insurance EDI re-enrollment with payers is required when switching PMS systems, adding 4–8 weeks of administrative work that is not always disclosed upfront.
  • Pricing is opaque and subscription-based ($800–$1,400/month for cloud tiers), with modules priced individually, making total cost unpredictable for small practices.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 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 Henry Schein One and Nutshell.

  • Object compatibility

    B

    1 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

    Henry Schein One: Not publicly documented per-org limits; enterprise customers receive dedicated API capacity.

  • Data volume sensitivity

    A

    Henry Schein One exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Henry Schein One to Nutshell 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 Henry Schein One to Nutshell data migrations

Answers to the questions buyers ask most during Henry Schein One to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Henry Schein One to Nutshell migrations complete in 48–72 hours of clock time for practices with fewer than 5,000 patient records. Multi-location DSO setups or practices with extensive appointment history (over 50,000 appointment records) extend to 5–10 days. The longest single step is usually the data audit and API credential setup, which can add 2–3 business days before extraction begins. Nutshell's contact-volume tiers also influence timeline if your patient count exceeds your current plan's contact limit.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Henry Schein One.
Land in Nutshell, 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