CRM migration

Migrate from My Dental Clinic to Nutshell

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 logo

My Dental Clinic

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between My Dental Clinic and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

My Dental Clinic logo

My Dental Clinic

What's pushing teams away

  • Customer service scores lag behind category leaders, with users reporting slow response times and difficulty reaching support during urgent issues.
  • Feature set feels limiting as practices grow beyond single-location operations, with fewer advanced reporting and multi-location management tools than competitors.
  • Lower value-for-money ratings compared to platforms offering broader feature bundles at similar price points.
  • Integration ecosystem is narrower than major dental platforms, making connectivity to specialized imaging or lab systems a friction point.

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 My Dental Clinic objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

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

maps to

Nutshell

Person (Custom Fields)

many:1
Fully supported

Insurance 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

maps to

Nutshell

Deal

1:1
Fully supported

A 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

maps to

Nutshell

Deal Line Item / Custom Field

1:1
Fully supported

Individual 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

maps to

Nutshell

Activity (Task/Event)

1:1
Fully supported

Appointment 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

maps to

Nutshell

Activity + Custom Field

1:1
Fully supported

Ledger 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

maps to

Nutshell

Company

1:1
Fully supported

Referring 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

maps to

Nutshell

Custom Field / Attachment

1:1
Fully supported

Clinical 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

maps to

Nutshell

Activity

1:1
Fully supported

Lab 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

maps to

Nutshell

Nutshell User

1:1
Fully supported

Provider 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

maps to

Nutshell

Custom Field on Person/Company

1:1
Fully supported

Any 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

maps to

Nutshell

Attachment on Person/Deal

1:1
Fully supported

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

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.

My Dental Clinic logo

My Dental Clinic gotchas

High

Dental ledgers are structurally complex to migrate accurately

Medium

Tooth-numbering systems differ between dental platforms

Medium

Insurance carrier IDs must be re-mapped post-migration

Medium

Custom clinical note templates may not map directly

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

  • Clinical notes and tooth-chart data cannot be represented in Nutshell's data model

    My Dental Clinic stores clinical data — perio charting, tooth-surface notations, procedure codes, clinical notes, and imaging references — in fields that have no structural equivalent in Nutshell. Nutshell's Person object has no tooth-chart model, no CDT-code field, and no perio-depth column. FlitStack exports this data as a PDF or structured file and attaches it to the Nutshell Person record as a reference document. The clinical record must remain accessible in My Dental Clinic or an archived system. This is not a data-loss risk if handled proactively — it is an architectural constraint of moving dental clinical data into a general-purpose CRM.

  • Recall and appointment reminder workflows are dental-domain logic that Nutshell cannot replicate

    My Dental Clinic's recall system tracks when each patient is due for a cleaning, exam, or procedure based on interval rules set per patient. Nutshell has no native recall engine — its task and activity automation (Pro+ plan) can trigger follow-ups based on pipeline stage changes or Activity completion, but not based on a per-patient recall interval stored on the Person record. We export your recall interval settings and last-appointment date as custom fields on each Person so your team can build Nutshell-based recall workflows using those fields as triggers. The logic itself must be rebuilt in Nutshell's automation layer or maintained externally.

  • Insurance ledger entries do not map to Nutshell's financial model

    My Dental Clinic tracks insurance claim status, paid amounts, adjustments, and outstanding balances per patient in a formal ledger. Nutshell has no ledger object, no accounts-receivable model, and no claim-status tracking. We migrate a financial summary (outstanding balance, last payment date, insurance carrier) as custom fields on the Person record. Detailed claim-by-claim history should be exported as a report from My Dental Clinic and attached to the Person as a PDF. Your billing workflow will need to live in a separate dental billing tool or be managed manually in Nutshell's Activity and Note model.

  • Appointment scheduling is one-directional; calendar sync requires post-migration configuration

    Nutshell does not have a native appointment scheduling engine. Appointment records from My Dental Clinic migrate as Activity records with due dates, provider assignments, and status, but Nutshell will not generate future appointments or send reminders from those records without additional configuration. If your practice uses Nutshell's built-in calendar sync (Google Calendar or Outlook), you will need to re-establish that sync post-migration and map provider calendars to the correct Nutshell Users. Appointment reminders will not fire automatically from migrated records.

  • Provider seats in Nutshell are a billing decision, not a technical one

    My Dental Clinic typically includes all providers under one practice subscription. Nutshell charges per seat — each provider who needs to log in, assign themselves to Deals, or manage Activities requires a Nutshell seat on your plan. Providers who only appear as data (e.g., a provider who has left the practice) can be stored as custom owner fields without consuming a seat. During migration planning, we flag every provider in My Dental Clinic against your intended Nutshell seat count so there are no surprise billing additions at go-live.

Migration approach

Six steps for a successful My Dental Clinic to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

My Dental Clinic logo

My Dental Clinic

Source

Strengths

  • Web-based, browser-accessible interface requiring no local server installation or maintenance overhead.
  • Automated patient communication tools including appointment reminders and intake form collection reduce front-desk workload.
  • Specialized dental workflow features including tooth charting and perio charting built into the core product rather than add-ons.

Weaknesses

  • Narrower third-party integration ecosystem compared to major dental platforms, limiting connectivity with specialized imaging and lab vendors.
  • Per-feature pricing model can become unpredictable in cost as practices add modules over time.
  • Customer service responsiveness scores trail category competitors, creating risk for practices that need timely support during transitions.
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 My Dental Clinic 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

    My Dental Clinic: Not publicly documented..

  • Data volume sensitivity

    B

    My Dental Clinic doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your My Dental Clinic 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 My Dental Clinic to Nutshell data migrations

Answers to the questions buyers ask most during My Dental Clinic to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most My Dental Clinic to Nutshell migrations complete in 24–72 hours for practices with fewer than 25,000 patient records. The longest phase is typically the pre-migration assessment and sample migration, which takes 1–3 business days of planning and review before data starts moving. Practices with more than 25,000 records, multiple providers, or extensive custom field schemas extend to 5–10 days. The delta-pickup window (24–48 hours) runs concurrently with go-live preparation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from My Dental Clinic.
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