CRM migration

Migrate from Dent-O-Soft to Nutshell

Field-level mapping, validation, and rollback between Dent-O-Soft and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Dent-O-Soft logo

Dent-O-Soft

Source

Nutshell

Destination

Nutshell logo

Compatibility

83%

10 of 12

objects map 1:1 between Dent-O-Soft and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Dent-O-Soft organizes dental practice data around clinical workflows: patients with oral charts, treatment plans, insurance claims, and appointment schedules. Nutshell uses a CRM model built around people, companies, leads, and deals with custom fields and activity logging. FlitStack AI maps Dent-O-Soft patients to Nutshell People, referring practices to Nutshell Companies, and treatment procedure codes to custom fields on deal records or as standalone custom fields. Appointment history migrates as Task and Event records with original timestamps and assigned owners. We preserve original create dates, clinical notes, and treatment status flags as custom fields in Nutshell since no native dental schema exists in the CRM. Workflows, insurance claim logic, and clinical charting rules do not migrate — they require manual rebuild using Nutshell's automation rules and custom field configurations. We use Nutshell's JSON-RPC API for data ingestion with a 48–72 hour delta-pickup window capturing any records modified during cutover, and quality assurance.

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

Dent-O-Soft logo

Dent-O-Soft

What's pushing teams away

  • When practices grow to multiple locations or add specialists, Dent-O-Soft does not appear to have published multi-site management or role-based access controls that large dental groups typically require.
  • Integration options with third-party imaging systems, e-prescribing platforms, and clearinghouses are not clearly documented, leading some practices to switch to platforms with more active marketplace ecosystems.
  • Support responsiveness and the availability of certified implementation consultants appear inconsistent compared to larger dental software vendors with formal channel partner networks.
  • Pricing structure is not transparently published, making it difficult for practices to compare total cost of ownership including modules for patient communication, insurance eligibility, and analytics.

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 Dent-O-Soft objects map to Nutshell

Each row shows how a Dent-O-Soft 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.

Dent-O-Soft

Patient

maps to

Nutshell

Person

1:1
Fully supported

Dent-O-Soft patients map directly to Nutshell People. Patient name, date of birth, contact phone, email, and address fields translate as direct field mappings. The Person record carries forward the original patient ID as a custom field for traceability. This ID mapping enables accurate record matching during delta syncs.

Dent-O-Soft

Patient

maps to

Nutshell

Lead

1:many
Fully supported

Patients with unscheduled treatment plans or inactive status route to Nutshell Leads. Active patients with open appointments route to People. The split is based on appointment status at migration time — practices choose the threshold rule during planning. This routing ensures your sales pipeline reflects the true status of each patient relationship.

Dent-O-Soft

Practice / Clinic

maps to

Nutshell

Company

1:1
Fully supported

The Dent-O-Soft practice entity (clinic name, address, NPI number) maps to a Nutshell Company record. Multi-location setups create multiple Company records with parent-child relationships using Nutshell's Account model. The NPI number is preserved as a custom field on the Company record for regulatory compliance and insurance verification purposes.

Dent-O-Soft

Treatment Plan

maps to

Nutshell

Deal

1:1
Fully supported

Each Dent-O-Soft treatment plan becomes a Nutshell Deal. Treatment plan status (proposed, scheduled, completed, cancelled) maps to Deal stage values. The deal Amount field carries the estimated treatment cost. A separate custom field stores the ADA procedure code reference. This mapping preserves the complete treatment history.

Dent-O-Soft

Procedure Code (ADA)

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

American Dental Association procedure codes (D0120, D0150, etc.) have no native equivalent in Nutshell. We create a custom text or pick-list field on the Deal object to store procedure code values for each treatment plan line item. The pick-list option ensures data consistency across all migrated treatment plans.

Dent-O-Soft

Appointment

maps to

Nutshell

Task / Event

1:1
Fully supported

Dent-O-Soft appointment records migrate as Nutshell Task records for completed visits and Event records for future scheduled appointments. Original appointment datetime, provider name, and appointment type (exam, cleaning, surgical) are preserved in Nutshell's activity fields. This preserves the complete appointment history for patient relationship management.

Dent-O-Soft

Clinical Note

maps to

Nutshell

Note

1:1
Fully supported

Clinical notes attached to patient records in Dent-O-Soft migrate as Nutshell Notes linked to the Person record. We preserve the original note date, author (provider), and note type. Rich-text formatting in Dent-O-Soft exports is flattened to plain text in Nutshell Notes.

Dent-O-Soft

Insurance Provider

maps to

Nutshell

Company

many:1
Fully supported

Dent-O-Soft insurance carrier records merge into Nutshell Company records separate from the practice Company. Each insurance Company record stores the carrier name, plan types accepted, and group number as custom fields. Patient-specific insurance details store on the Person record. This separation maintains clean data organization.

Dent-O-Soft

Billing / Claim

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

Patient account balance, claim status, and insurance payment history cannot map to any native Nutshell object. We store these as custom fields on the associated Deal record: Claim_Status__c, Insurance_Paid__c, Patient_Balance__c, and Claim_Submission_Date__c. These custom fields enable financial tracking and reporting within Nutshell's deal management interface.

Dent-O-Soft

Provider / Dentist

maps to

Nutshell

Person (User reference)

1:1
Fully supported

Dentists and hygienists in Dent-O-Soft map to Nutshell Person records with a custom role field (Provider_Role__c). If the provider is also a Nutshell user, we match by email and set the Person record's owner to the corresponding Nutshell user. This dual-role mapping ensures providers can be tracked both as contacts and as system users.

Dent-O-Soft

Referral Source

maps to

Nutshell

Custom Field on Lead / Person

1:1
Fully supported

Referral source flags in Dent-O-Soft (patient origin: new patient, referral, marketing campaign) migrate as a custom pick-list field Referral_Source__c on both Lead and Person records. Marketing attribution data from Dent-O-Soft campaigns stores in a custom field. This allows for detailed marketing ROI analysis and referral tracking.

Dent-O-Soft

Document / Attachment

maps to

Nutshell

File attachment on Person / Company

1:1
Fully supported

Treatment consent forms, insurance cards, and imaging files exported from Dent-O-Soft re-upload to Nutshell as file attachments on the corresponding Person or Company record. File size limits from Nutshell's storage apply — large imaging files may require external hosting with link storage in Nutshell.

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.

Dent-O-Soft logo

Dent-O-Soft gotchas

High

No API and no documented bulk export path

Medium

On-premises deployment with limited remote access

Medium

No free trial and no published pricing

Low

Single-language support (English) and small distribution footprint

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

  • No native dental schema in Nutshell requires comprehensive custom field setup

    Nutshell provides no built-in objects for teeth, procedure codes, insurance carriers, or clinical charts. Every dental data element — ADA procedure codes, tooth numbers, insurance group numbers, claim status, and clinical note types — requires a custom field on Person, Company, or Deal. Practices with 20+ treatment plan custom fields spend additional time in the planning phase defining the custom field schema before migration. We deliver a custom field manifest listing every required field, its type (text, pick-list, date, currency), and which Nutshell object it belongs to before data moves.

  • Appointment history requires activity record linking to both patient and provider

    Dent-O-Soft stores appointments with links to both patient and provider. In Nutshell, Events require a single primary entity link. We create Event records linked to the Person record (patient) and store provider attribution in a custom Provider_Name__c field on the Event. If your practice needs dual-linked activities with both patient and provider visible in Nutshell's activity timeline, your admin must configure a custom activity layout post-migration. This is a design decision that affects reporting visibility.

  • Insurance claim data does not translate to any native Nutshell object

    Dent-O-Soft tracks claim submission dates, insurance payments, patient balances, and claim denial codes. Nutshell has no billing or claims object. We store these as custom currency and text fields on the associated Deal record: Claim_Status__c, Insurance_Paid__c, Patient_Balance__c, and Claim_Submission_Date__c. However, Nutshell's reporting does not natively summarize claim aging or insurance aging buckets — your team must build custom reports or export to a spreadsheet for financial reporting on historical claims.

  • Clinical charting data loses structural context in a flat-note format

    Dent-O-Soft clinical charts store per-tooth status, periodontal readings, existing restorations, and treatment history in a structured clinical chart format. When migrated to Nutshell Notes, this structure flattens to plain text. A chart that previously displayed tooth #3 with MOD amalgam, pocketing 4-5mm, and a pending root canal becomes a text paragraph. We preserve all clinical data — nothing is dropped — but the visual chart context requires reconstruction in Nutshell's custom note templates post-migration.

  • Workflow automation and clinical rules do not migrate and have no Nutshell equivalent

    Dent-O-Soft workflow rules — appointment reminder triggers, insurance verification automations, treatment plan escalation logic — do not have a functional equivalent in Nutshell's automation engine. Nutshell automation rules are trigger-based action sequences (add tag, assign owner, send email) scoped to CRM sales workflows, not clinical practice management. Your team must rebuild clinical workflow logic manually after migration, or accept that appointment reminders and claim triggers will not fire automatically in Nutshell.

Migration approach

Six steps for a successful Dent-O-Soft to Nutshell data migration

  1. Extract Dent-O-Soft data via available export method

    We assess your Dent-O-Soft deployment — on-premises or hosted — and identify the available export path: direct database query, CSV report generation, or manual extraction via the built-in reporting module. We document the schema of every table or report field included in the export and flag any records with incomplete required fields (missing patient name, no contact info) for your team to review before migration begins.

  2. Design Nutshell custom field schema

    Based on the Dent-O-Soft data model, we create a custom field manifest specifying every custom field required in Nutshell: procedure_code__c, tooth_surface__c, claim_status__c, insurance_group__c, referral_source__c, provider_role__c, and others. Your Nutshell admin creates these fields in Settings > Data > Custom Fields before the migration run. We provide step-by-step field creation instructions and validate the schema matches the manifest before proceeding. We also provide a validation checklist to ensure all required fields are created with the correct types before any data migration begins.

  3. Resolve provider records and link to Nutshell users

    Dent-O-Soft providers are matched to Nutshell users by email address. If a provider does not have a Nutshell user account, we create a Person record for them and flag the record for your admin to assign a user account. Provider-person linkage is critical for Deal owner assignment — every treatment plan needs an owner to appear in Nutshell's pipeline view. Unmatched providers are listed in a pre-migration report with resolution instructions.

  4. Run sample migration with field-level diff

    A representative slice of 100–500 records migrates first — spanning patients, companies, treatment plans, and appointments. We generate a field-level diff comparing source values to destination field values, flagging any transformation errors, dropped characters in procedure codes, or incorrectly mapped stage values. You review the diff in Nutshell before the full run commits. Adjustments to mapping logic are applied before the final migration.

  5. Execute full migration with delta-pickup window

    Full data migration runs against Nutshell's JSON-RPC API. A delta-pickup window of 48–72 hours runs concurrently, capturing any patient records, appointments, or treatment plans created or modified in Dent-O-Soft during the cutover period. The delta window ensures Nutshell reflects the final state of Dent-O-Soft at go-live. All operations are logged in an audit trail, and one-click rollback is available if reconciliation fails.

Platform deep dives

Context on both ends of the pair

Dent-O-Soft logo

Dent-O-Soft

Source

Strengths

  • Covers scheduling, clinical charting, patient billing, and lab/vendor management in one database.
  • Per-tooth graphical charting with linked treatment history gives clinicians a visual clinical record.
  • Integrated charge and payment posting against patient accounts.
  • Supplier and dental technician records maintained alongside patient data.
  • Designed for small-to-mid-size single-location dental practices.

Weaknesses

  • No publicly documented API for bulk data export or integration with external systems.
  • Multi-location and DSO-scale role management capabilities are not described.
  • Integration marketplace for imaging, e-prescribing, and clearinghouses is not publicly documented.
  • Pricing tiers and module-level costs are not transparently published on the vendor website.
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 manual workaround.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Dent-O-Soft and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a manual workaround.

  • 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

    Dent-O-Soft: N/A.

  • Data volume sensitivity

    B

    Dent-O-Soft doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Dent-O-Soft 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 Dent-O-Soft to Nutshell data migrations

Answers to the questions buyers ask most during Dent-O-Soft to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Dent-O-Soft to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Dent-O-Soft to Nutshell migrations complete within 48–72 hours for practices with fewer than 25,000 patient records. Larger practices with complex treatment histories — 100,000+ records with extensive custom fields — extend to 5–7 days. The custom field schema setup phase (Step 2 in our approach) is the longest planning step and depends on how many dental data elements require custom fields in Nutshell.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Dent-O-Soft.
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