CRM migration

Migrate from Dental-Exec to Nutshell

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

Dental-Exec logo

Dental-Exec

Source

Nutshell

Destination

Nutshell logo

Compatibility

93%

13 of 14

objects map 1:1 between Dental-Exec and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Dental-Exec structures its data around dental-practice operations — patients as primary records, treatment plans, production goal tracking, and drug interaction flags. Nutshell models everything as standard CRM objects: People (contacts), Companies (practices or insurance carriers), Leads, Deals (treatment-case or production tracking), Activities (appointments and calls), Tasks, and Notes. The migration maps Dental-Exec patient fields to Nutshell People, insurance carrier references to Companies with custom fields for carrier-specific data, production metrics to custom fields on Deals, and treatment-plan notes to Nutshell Notes or custom fields. We use Dental-Exec's API or CSV export to extract all records, transform field names and data types to match Nutshell's schema, create any required custom fields (Person, Company, or Lead tabs) before import, then load data in dependency order — Companies first, then People, then Leads, then Deals, then Activities. A delta-pickup window captures any records modified during cutover. Workflows, automation rules, and drug interaction logic in Dental-Exec do not have equivalents in Nutshell and must be rebuilt manually post-migration using Nutshell's automation tools.

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

Dental-Exec logo

Dental-Exec

What's pushing teams away

  • With only 6 verified reviews and a 3.2 rating, Dental-Exec has a thin track record that raises concerns about long-term vendor stability and support responsiveness.
  • Customer service scores of 3.0 on Capterra indicate slow support response times and difficulty reaching a knowledgeable representative for configuration issues.
  • The platform lacks a documented public API, limiting automation and forcing practices to rely on manual data entry for tasks and scheduling.
  • Offices outgrowing basic task management report that Dental-Exec does not scale into patient relationship marketing, multi-location dashboards, or insurance claim workflows.

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

Each row shows how a Dental-Exec 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.

Dental-Exec

Patient

maps to

Nutshell

Person

1:1
Fully supported

Dental-Exec patients map directly to Nutshell People. All core fields — name, date of birth, phone, email, and address — transfer as‑is. The original patient ID is stored as Source_System_ID__c on the Nutshell Person for traceability, and the original create date is preserved in Original_Create_Date__c. Owner assignment (provider) is resolved via email match and recorded on the Person record.

Dental-Exec

Patient.phone

maps to

Nutshell

Person.phone

1:1
Fully supported

Primary phone number on the Dental‑Exec patient record maps to Nutshell Person.phone without transformation. If Dental‑Exec stores a mobile or secondary phone number in separate fields, those values are mapped to Person.alt_phone or a custom phone field as appropriate. Any missing phone field results in a blank entry in Nutshell; no data is dropped.

Dental-Exec

Patient.email

maps to

Nutshell

Person.email

1:1
Fully supported

Email address moves directly from Dental‑Exec to Nutshell Person.email. Nutshell enforces uniqueness per account, so if the same email appears on multiple patient records, the migration pauses the duplicate record and flags it for your admin to resolve before the final commit. This prevents duplicate contacts while preserving the original email data.

Dental-Exec

Patient.insurance_carrier

maps to

Nutshell

Company + custom field

1:1
Fully supported

Dental-Exec insurance carrier references (a lookup or string field on the patient) become a Company record in Nutshell representing the insurance carrier, plus a custom field (Insurance_Carrier__c) on the Person linking back. This lets practices track carrier-specific data separately from patient records.

Dental-Exec

Treatment Plan

maps to

Nutshell

Deal

1:1
Fully supported

Dental-Exec treatment plans map to Nutshell Deals. Deal name derives from the treatment plan description or a patient-name + date composite. Deal.Amount maps from the treatment plan estimated cost if present. Deal.stage maps from the treatment plan status (proposed, in-progress, completed).

Dental-Exec

Treatment Plan.stage

maps to

Nutshell

Deal.stage

1:1
Fully supported

Dental‑Exec treatment plan status values such as 'Scheduled', 'In Progress', 'Completed', or 'Cancelled' map to corresponding Nutshell Deal stage values through a value‑by‑value lookup. If Dental‑Exec uses custom status labels beyond these defaults, we create a custom mapping table during discovery, ensuring each label resolves to the most appropriate Nutshell stage or a custom stage when necessary.

Dental-Exec

Provider / Dentist

maps to

Nutshell

User (Owner)

1:1
Fully supported

Dental‑Exec provider records are matched to Nutshell Users by email address, the preferred key for owner resolution. When a provider record lacks an email, we fall back to name matching and flag the record for your admin to either map to an existing Nutshell user or invite the provider as a new user before the migration runs. All resolved owners are set on the related Deals, Activities, and Tasks, preserving accountability across the CRM.

Dental-Exec

Appointment

maps to

Nutshell

Activity

1:1
Fully supported

Dental‑Exec appointments convert to Nutshell Activities, preserving the appointment type (checkup, cleaning, procedure) as the Activity type field. Start and end times are transferred directly, linked to the corresponding Person (patient) and, when present, to a Company (insurance carrier or practice). The owning User is set to the provider who performed the appointment, and original timestamps are retained for historical reporting.

Dental-Exec

Production Goal

maps to

Nutshell

custom fields on Deal + custom field on User

1:1
Fully supported

Dental-Exec production goal tracking per provider has no native Nutshell equivalent. We create custom fields — Production_Goal__c and Production_Actual__c — on Nutshell Deals to capture the goal context, and link to the responsible User. Nutshell's reporting can then surface provider performance by querying these custom fields.

Dental-Exec

Task / Reminder

maps to

Nutshell

Task

1:1
Fully supported

Dental‑Exec tasks and reminders migrate to Nutshell Tasks with subject, due date, assigned User, and completion status all transferred directly. Completed tasks retain their original completion timestamp, while open tasks keep their due date and owner. Each task is linked to the associated Person (patient) record so that the task appears in the patient’s activity feed within Nutshell.

Dental-Exec

Clinical Note

maps to

Nutshell

Note + custom field on Person

many:1
Fully supported

Dental-Exec clinical notes (drug interactions, clinical observations) merge into Nutshell Notes attached to the Person record. For compliance-relevant notes (e.g., allergy flags), we also populate a custom field on Person (e.g., Clinical_Flag__c) so the flag surfaces without opening the note.

Dental-Exec

Custom Field (Patient-level)

maps to

Nutshell

custom field on Person

1:1
Fully supported

Dental-Exec custom fields on patient records map to Nutshell Person-level custom fields. Each custom field gets created in Nutshell under the Person tab before migration. Field type is preserved — text, number, date, pick-list — using Nutshell's corresponding field types.

Dental-Exec

Custom Field (Treatment-level)

maps to

Nutshell

custom field on Deal

1:1
Fully supported

Dental‑Exec custom fields attached to treatment plans are recreated as custom fields on the corresponding Nutshell Deal. Field types such as text, number, date, or pick‑list are matched to Nutshell’s equivalent field types during the discovery phase. If the custom field holds provider‑specific metrics or compliance data (e.g., a drug‑interaction flag), we map it to a custom field with an appropriate type and include it in Deal reporting views.

Dental-Exec

Attachment / File

maps to

Nutshell

File attachment on Person / Deal

1:1
Fully supported

Dental‑Exec file attachments such as treatment images, consent forms, and insurance documents are migrated as file attachments on the related Nutshell Person or Deal record. File size is limited to the standard upload limit defined by the Nutshell plan tier; files exceeding this limit are flagged for your admin to upload manually after cutover or to increase storage. Original file names and creation timestamps are preserved where possible.

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.

Dental-Exec logo

Dental-Exec gotchas

High

No public API for automated exports

Medium

Recall and hygiene data embedded in task records

Medium

Drug interaction flags are binary, not structured

Low

Thin vendor footprint raises continuity risk

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-Exec has no documented public API — export-based migration is the primary path

    Dental-Exec does not publish a public REST or GraphQL API with full CRUD coverage. The migration relies on Dental-Exec's built-in export function (CSV or backup) to extract patient records, treatment plans, and activity history. If the export omits certain fields due to Dental-Exec's own schema limitations, those fields cannot be migrated. We document which fields are present in the export during the discovery phase and flag any gaps before committing to scope. The risk is mitigated by requesting a full data export early in the project so your team can review what Dental-Exec actually holds.

  • Production goal tracking requires custom fields on Nutshell Deals — no native equivalent

    Dental-Exec's production goal tracking per provider is a core feature for dental practices, but Nutshell has no native field for production targets or actuals. We create Production_Goal__c and Production_Actual__c as custom currency fields on Nutshell Deals, but Nutshell's native pipeline reporting cannot automatically calculate goal attainment against these fields. Your team will need to use Nutshell's custom reporting or a third-party BI tool (e.g., Databox, Geckoboard) to build provider performance dashboards from these custom fields. We surface this as a post-migration reporting recommendation during the migration plan review.

  • Insurance carrier references require a two-step mapping to Nutshell Companies

    Dental-Exec stores insurance carrier as a string field or lookup on the patient record. In Nutshell, carrier information is best stored as a Company record (representing the insurance company) linked to the Person via a custom field. This means we first create Company records for every unique carrier name found in Dental-Exec, then link each patient Person record to the appropriate carrier Company. If Dental-Exec stores carrier data inconsistently (e.g., free-text carrier name with spelling variations), these variants create duplicate Company records in Nutshell. We deduplicate by normalizing carrier names before creating Companies, but your team should review the carrier list during the discovery phase.

  • Drug interaction flags and clinical notes cannot fully replicate Dental-Exec's compliance logic

    Dental-Exec embeds drug interaction checking and clinical flag logic into its workflow. Nutshell has no native drug interaction or clinical compliance module — it is a general CRM. We migrate allergy flags and clinical notes as custom fields and Note attachments on Person records, but the enforcement logic (e.g., alerts when a specific drug is prescribed) does not exist in Nutshell. Your clinical team must maintain a separate reference process for drug interactions post-migration, or evaluate a dedicated dental compliance tool to complement Nutshell.

  • Dental-Exec workflows and automations have no Nutshell equivalent and must be rebuilt

    Any automated reminders, escalation rules, or workflow triggers configured in Dental-Exec (e.g., automated appointment reminders, production goal alerts, task routing based on treatment stage) do not migrate. Nutshell's automation tools (sequences, workflow rules, task triggers) must be rebuilt from scratch. We provide an exported inventory of Dental-Exec's automation rules as a reference document for your Nutshell admin to use during the rebuild phase. The rebuild is not included in the standard migration scope.

Migration approach

Six steps for a successful Dental-Exec to Nutshell data migration

  1. Request and audit Dental-Exec full data export

    FlitStack AI requests a complete data export from Dental-Exec — typically a CSV backup covering patients, treatment plans, appointments, tasks, clinical notes, and any custom fields. We audit the export for field completeness, identify any fields Dental-Exec omits from its export, and document which objects have data. If the export is incomplete, we surface gaps before scope is finalized. This step also identifies the unique carrier names used in insurance fields so we can plan the Company deduplication logic before import.

  2. Create Nutshell custom fields and Company records

    Before any data loads into Nutshell, we create all required custom fields: Production_Goal__c and Production_Actual__c on Deal, Insurance_Carrier__c and Allergy_Flag__c on Person, and any dynamic custom fields discovered in the Dental-Exec export. We also pre-create Company records for every unique insurance carrier name found in the export, normalizing spelling variations to avoid duplicates. This ensures the Person import can resolve carrier lookups correctly on first pass.

  3. Resolve owners and users by email match

    Dental-Exec provider and staff IDs are matched to Nutshell Users by email address. If a Dental-Exec provider has no associated email in the export, we flag the record and your admin either maps it to an existing Nutshell user or creates a new Nutshell user before migration. No Deal, Activity, or Task lands in Nutshell without a valid owner assignment — unresolved assignments are held in a staging queue for manual resolution.

  4. Run a sample migration with field-level diff

    A representative slice of records — typically 100–300 patients, their associated treatment plans, appointments, and tasks — migrates first. We generate a field-level diff showing source value, transformed value, and destination value for every mapped field. You review the diff to verify production goal mapping, insurance carrier linking, clinical note attachment, and stage assignment before the full run commits. This is the validation checkpoint where adjustments to value-mapping tables or custom field creation are made.

  5. Execute full migration with delta-pickup window

    The full migration runs against Nutshell's API in dependency order: Companies (carriers) first, then People (patients), then Leads, then Deals (treatment plans), then Activities (appointments), then Tasks, then Notes and attachments. A delta-pickup window of 24–48 hours after the full run captures any records created or modified in Dental-Exec during cutover. An audit log records every operation; one-click rollback is available if reconciliation fails.

Platform deep dives

Context on both ends of the pair

Dental-Exec logo

Dental-Exec

Source

Strengths

  • Production goal tracking per provider gives small practices quantified output metrics rather than purely clinical recording
  • Multi-screen support lets front-desk staff manage patient information across simultaneous screens during consultations
  • Embedded drug reference (Lexicomp) and dental-benefit verification reduce reliance on separate point tools
  • Perio charting with customisable formatting is highlighted by reviewers as a strong clinical feature
  • Long-standing dental-industry support reputation — reviewers cite 35+ years of responsive support from DSN Dental Software

Weaknesses

  • Capterra rating sits at 3.2/5 across only 6 reviews — sparse track record raises evaluation confidence concerns
  • Reviewers report performance issues including slowness and program crashes that can cause data loss
  • No documented public API or bulk export, blocking automation and modern integration workflows
  • Cost is described by some reviewers as expensive relative to delivered functionality
  • Reports are flagged as hard to navigate, limiting practice-management analytics without external tooling
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. 2 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 Dental-Exec and Nutshell.

  • Object compatibility

    B

    2 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

    Dental-Exec: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Dental-Exec to Nutshell migrations complete in 24–72 hours of clock time for practices with under 25,000 patient records. The timeline is dominated by the discovery and field-mapping phase (1–3 days) and the sample migration validation checkpoint. Larger practices with over 25,000 records, multiple custom fields, or hundreds of treatment plans extend to 5–10 days. The delta-pickup window adds 24–48 hours after the full run.

Adjacent paths

Related migrations to explore

Ready when you are

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