CRM migration
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
Source
Nutshell
Destination
Compatibility
10 of 12
objects map 1:1 between Dent-O-Soft and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Dent-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
Nutshell
Lead
1:manyPatients 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
Nutshell
Company
1:1The 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
Nutshell
Deal
1:1Each 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)
Nutshell
Custom Field on Deal
1:1American 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
Nutshell
Task / Event
1:1Dent-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
Nutshell
Note
1:1Clinical 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
Nutshell
Company
many:1Dent-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
Nutshell
Custom Field on Deal
1:1Patient 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
Nutshell
Person (User reference)
1:1Dentists 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
Nutshell
Custom Field on Lead / Person
1:1Referral 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
Nutshell
File attachment on Person / Company
1:1Treatment 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.
| Dent-O-Soft | Nutshell | Compatibility | |
|---|---|---|---|
| Patient | Person1:1 | Fully supported | |
| Patient | Lead1:many | Fully supported | |
| Practice / Clinic | Company1:1 | Fully supported | |
| Treatment Plan | Deal1:1 | Fully supported | |
| Procedure Code (ADA) | Custom Field on Deal1:1 | Fully supported | |
| Appointment | Task / Event1:1 | Fully supported | |
| Clinical Note | Note1:1 | Fully supported | |
| Insurance Provider | Companymany:1 | Fully supported | |
| Billing / Claim | Custom Field on Deal1:1 | Fully supported | |
| Provider / Dentist | Person (User reference)1:1 | Fully supported | |
| Referral Source | Custom Field on Lead / Person1:1 | Fully supported | |
| Document / Attachment | File attachment on Person / Company1: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.
Dent-O-Soft gotchas
No API and no documented bulk export path
On-premises deployment with limited remote access
No free trial and no published pricing
Single-language support (English) and small distribution footprint
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
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.
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.
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.
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.
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
Dent-O-Soft
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Dent-O-Soft and Nutshell.
Object compatibility
1 of 8 objects need a manual workaround.
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
Dent-O-Soft: N/A.
Data volume sensitivity
Dent-O-Soft 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 Dent-O-Soft to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Dent-O-Soft
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.