CRM migration
Field-level mapping, validation, and rollback between My Dental Clinic and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
My Dental Clinic
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between My Dental Clinic and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
My Dental Clinic is a dental-practice management system that centres on patient records, treatment plans, appointment scheduling, insurance ledgers, and billing — plus a thin contact layer for patient names, phone numbers, and email addresses. Nutshell is a general-purpose CRM with People, Companies, Leads, Deals, and Activities as its primary objects. The two data models overlap only in the contact and company layers; clinical data (treatment history, tooth charts, imaging references, clinical notes) has no equivalent in Nutshell and cannot be faithfully represented in a standard CRM field. We extract patient demographics and contact information via API or structured export from My Dental Clinic, resolve them against Nutshell's People and Companies objects, and map appointment and deal history into Nutshell Activities and Deals. Insurance carrier data, treatment codes, and clinical free-text notes migrate as custom fields on the Person record so staff have reference access without re-entering data manually. Practice-management automations (recall reminders, treatment-plan workflows, insurance claim routing) are dental-domain logic and cannot be replicated in Nutshell's automation layer — we export those 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 My Dental Clinic 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.
My Dental Clinic
Patient Record
Nutshell
Person
1:1Patient first name, last name, date of birth, phone number, email address, street address, and contact preferences map directly to the corresponding Nutshell Person standard fields. The patient's active/inactive status from My Dental Clinic maps to a custom pick-list field (Patient_Status__c) on the Nutshell Person record to preserve workflow visibility.
My Dental Clinic
Patient Record (Insurance Block)
Nutshell
Person (Custom Fields)
many:1Insurance carrier name, subscriber ID, group number, and subscriber relationship merge into a custom field group on the Nutshell Person record. We store each insurance attribute as a separate custom field so staff can query by carrier or subscriber ID within Nutshell.
My Dental Clinic
Treatment Plan
Nutshell
Deal
1:1A My Dental Clinic treatment plan with proposed procedures, estimated amounts, and case stages maps to a Nutshell Deal. The deal name uses the patient name + treatment type. Estimated fee maps to Deal amount. Treatment-plan stage (Proposed, Accepted, Scheduled, In Progress, Completed) maps to Nutshell Deal Stage via value mapping.
My Dental Clinic
Treatment Procedure Line Item
Nutshell
Deal Line Item / Custom Field
1:1Individual procedure codes from My Dental Clinic (CDT codes in Dxxxx format) and associated fees map to a custom text area field on the Nutshell Deal record. This field lists each procedure code alongside its fee for clinical reference during case review. Since Nutshell Deals do not include a native line-item sub-object at the standard plan level, this custom field approach provides the necessary granularity.
My Dental Clinic
Appointment Record
Nutshell
Activity (Task/Event)
1:1Appointment date, time, provider, and procedure type migrate as Nutshell Activity records linked to the Person. Appointment status (Completed, No Show, Cancelled) maps to a custom pick-list field on the Activity. Full clinical notes attached to appointments do not migrate — see gotchas.
My Dental Clinic
Ledger Entry / Payment Record
Nutshell
Activity + Custom Field
1:1Ledger balances, outstanding amounts, and last payment date migrate as a custom financial summary field on the Person record. Detailed payment history lines are too granular for Nutshell's data model — we recommend exporting the full ledger as a PDF and attaching it to the Person record.
My Dental Clinic
Referring Dentist / Referral Source
Nutshell
Company
1:1Referring dentists and referral-source organizations from My Dental Clinic map to Nutshell Companies. The practice or dentist name, address, and contact information map to the Nutshell Company name and standard address fields, with the individual dentist added as a primary contact Person record linked to that Company. The referral relationship type (e.g., Referring Dentist, Lab, Specialist) maps to a custom pick-list field on the Company record to enable segmentation.
My Dental Clinic
Clinical Notes / Tooth Chart
Nutshell
Custom Field / Attachment
1:1Clinical notes, periodontal charting, and tooth-chart data have no equivalent in Nutshell. We export these as a PDF or structured file and attach them to the Person record as a reference document. The original clinical record must remain accessible in My Dental Clinic or be archived per your retention policy.
My Dental Clinic
Lab Case / Impression Record
Nutshell
Activity
1:1Lab case status values from My Dental Clinic (such as Impression Taken, Sent to Lab, Received, and Delivered) migrate as a chronological series of Nutshell Activity records with timestamps and provider assignments preserved. The lab name and lab case number are stored in custom fields on the related Person record for quick reference when following up on outstanding lab work.
My Dental Clinic
Provider / Staff Record
Nutshell
Nutshell User
1:1Provider names and staff assignments in My Dental Clinic resolve to Nutshell Users by email match. If providers do not have Nutshell accounts, their records attach to the relevant Person or Activity as a custom owner field. Nutshell's per-seat model means each active provider needs a seat if they will interact with the CRM.
My Dental Clinic
Custom Patient Field
Nutshell
Custom Field on Person/Company
1:1Any custom fields defined in My Dental Clinic (e.g., Preferred Contact Method, Recall Interval, Last Cleaning Date) map to identically named custom fields on the Nutshell Person record. We create these during the pre-migration schema setup phase before data loads.
My Dental Clinic
Document / Attachment
Nutshell
Attachment on Person/Deal
1:1Patient documents stored in My Dental Clinic — including consent forms, insurance cards, treatment consent PDFs, and other attachments — are re-uploaded as file attachments on the corresponding Nutshell Person record. Nutshell supports file attachments on both People and Deals objects, subject to its standard storage limits per your Nutshell plan tier.
| My Dental Clinic | Nutshell | Compatibility | |
|---|---|---|---|
| Patient Record | Person1:1 | Fully supported | |
| Patient Record (Insurance Block) | Person (Custom Fields)many:1 | Fully supported | |
| Treatment Plan | Deal1:1 | Fully supported | |
| Treatment Procedure Line Item | Deal Line Item / Custom Field1:1 | Fully supported | |
| Appointment Record | Activity (Task/Event)1:1 | Fully supported | |
| Ledger Entry / Payment Record | Activity + Custom Field1:1 | Fully supported | |
| Referring Dentist / Referral Source | Company1:1 | Fully supported | |
| Clinical Notes / Tooth Chart | Custom Field / Attachment1:1 | Fully supported | |
| Lab Case / Impression Record | Activity1:1 | Fully supported | |
| Provider / Staff Record | Nutshell User1:1 | Fully supported | |
| Custom Patient Field | Custom Field on Person/Company1:1 | Fully supported | |
| Document / Attachment | Attachment on Person/Deal1: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.
My Dental Clinic gotchas
Dental ledgers are structurally complex to migrate accurately
Tooth-numbering systems differ between dental platforms
Insurance carrier IDs must be re-mapped post-migration
Custom clinical note templates may not map directly
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
Assess My Dental Clinic export feasibility
We begin by evaluating how your My Dental Clinic instance stores data — via direct API access, structured export, or manual file generation. Not all My Dental Clinic deployments expose the same export interfaces. We request a sample export of patient demographics, treatment plans, and appointment history, then validate field coverage against your custom field list. If the export format is non-standard, we build a transformation pipeline before any data moves. This step typically takes 1–2 business days.
Create Nutshell custom fields and map pipeline stages
Before data loads, we create every custom field identified in the mapping plan — Insurance_Carrier__c, Recall_Interval_Months__c, Patient_Status__c, and so on — on the Nutshell Person, Company, and Deal objects. We also configure the Deal pipeline stages to match your My Dental Clinic treatment-plan stages, adjusting probabilities and stage names per your input. This pre-staging ensures the data lands in correctly typed fields from the first migration run, eliminating re-import correction cycles.
Run a sample migration with field-level diff
A representative slice of 50–200 patient records migrates first, spanning active patients, patients with outstanding treatment plans, and patients with insurance on file. We generate a field-level diff between the My Dental Clinic source values and the Nutshell destination values for every mapped field. You review the diff, confirm that treatment-plan stage mapping and insurance field population look correct, and flag any adjustments before the full run. This step is the quality gate for the entire migration.
Execute full migration with delta-pickup window
The full dataset migrates from My Dental Clinic to Nutshell: Patient records to People, treatment plans to Deals, appointments to Activities, and referring dentists to Companies. A delta-pickup window of 24–48 hours runs simultaneously, capturing any new patients or modified treatment plans created in My Dental Clinic during the migration window. We generate an audit log of every record inserted, updated, or skipped, with source system IDs preserved for reconciliation. One-click rollback is available if the reconciliation count shows unexpected variance.
Reconcile, attach clinical references, and hand off rebuild specs
We run a record-count reconciliation comparing My Dental Clinic totals (patients, treatment plans, appointments) against Nutshell totals (People, Deals, Activities). Any gaps are investigated and corrected. Clinical notes, tooth charts, and ledger PDFs are attached to the corresponding Person records. We deliver a rebuild specification document listing every My Dental Clinic automation — recall reminders, appointment confirmations, treatment-plan progression triggers — as a reference for your team to reconstruct in Nutshell's automation layer. Post-migration support is available for 5 business days following go-live.
Platform deep dives
My Dental Clinic
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 My Dental Clinic 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
My Dental Clinic: Not publicly documented..
Data volume sensitivity
My Dental Clinic 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 My Dental Clinic to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your My Dental Clinic 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 My Dental Clinic
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.