CRM migration

Migrate from Dr.DENTES to Nutshell

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

Dr.DENTES logo

Dr.DENTES

Source

Nutshell

Destination

Nutshell logo

Compatibility

93%

14 of 15

objects map 1:1 between Dr.DENTES and Nutshell.

Complexity

BStandard

Timeline

5–10 business days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Dr.DENTES is dental-specific practice management software storing patient records, appointment histories, treatment plans, and associated contacts. Nutshell is an SMB-focused CRM with standard objects for People (contacts), Companies, Leads, and Deals, plus customizable fields across all three person-facing objects. Dr.DENTES does not publish a self-service export tool — API access requires contacting their support directly, which adds planning steps before migration can begin. FlitStack AI extracts data from Dr.DENTES via their API (credentials obtained by request) or through structured manual export, then maps patient records to Nutshell People, Dr.DENTES companies or practice entities to Nutshell Companies, and appointment activities to Nutshell Events and Tasks. Custom dental fields — such as insurance carrier, treatment codes, referral source, and HIPAA compliance flags — are preserved as Nutshell custom fields created during migration setup. Owner assignments in Dr.DENTES map to Nutshell users by email match, with unmatched staff flagged for team configuration before go-live. Automations, email templates, and dental-specific workflow triggers do not migrate — these require rebuild in Nutshell using Nutshell's automation tools or a third-party integration layer. Reports and dashboards are rebuilt using Nutshell's native reporting and external spreadsheet analysis. We run a sample migration first with field-level diff, then execute the full migration with a 24–48 hour delta pickup window capturing in-flight changes during cutover. Nutshell's open API at app.nutshell.com/api/v1/json supports post-migration verification and ongoing sync if required.

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

Dr.DENTES logo

Dr.DENTES

What's pushing teams away

  • Geographic focus is Turkey first; the compliance integrations (USS/e-Nabız, e-Reçete) are irrelevant outside Turkey, and English-speaking dental practices typically need different e-prescribing connectors.
  • Very thin public review footprint — G2, Capterra, Software Advice, and GetApp list the product but with minimal reviewer feedback, so prospective buyers cannot easily compare against Curve, Open Dental, or Dentrix.
  • No documented public API or developer portal limits integration with practice analytics, marketing platforms, or imaging hardware vendors.
  • Single-vendor lock-in for the e-Nabız/USS bridge means migrations off Dr.DENTES require rebuilding the Turkish compliance integration in whatever dental PM replaces it.
  • Lightweight reporting and analytics versus enterprise-tier dental PMs; reviewers and the vendor's own feature page describe analytics as 'detailed reporting' rather than a configurable BI layer.

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 Dr.DENTES objects map to Nutshell

Each row shows how a Dr.DENTES 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.

Dr.DENTES

Patient Record

maps to

Nutshell

Person

1:1
Fully supported

Dr.DENTES patient records map directly to Nutshell People. Each patient becomes one Person record, preserving name, contact details, address, and original Dr.DENTES patient ID in a custom field for traceability. Unmatched email addresses are flagged for manual review. During migration, any duplicate records are identified and resolved before final import.

Dr.DENTES

Patient Record

maps to

Nutshell

Lead

1:many
Fully supported

Dr.DENTES patients who have not completed a treatment plan route to Nutshell Lead status. Patients with completed treatments and active recall dates route to Nutshell Person records with a treatment-completed flag stored in a custom field. The routing logic is based on the treatment status and recall schedule fields present in the source data.

Dr.DENTES

Practice / Clinic Entity

maps to

Nutshell

Company

1:1
Fully supported

Dr.DENTES practice or clinic records map to Nutshell Companies. Practice name, address, phone, and website transfer as Company fields. If Dr.DENTES stores referring practices separately, each becomes its own Company record linked to the primary patient Person. This ensures that referral networks are represented accurately in Nutshell's company hierarchy.

Dr.DENTES

Treatment Plan

maps to

Nutshell

Deal

1:1
Fully supported

Dr.DENTES treatment plans become Nutshell Deals. Treatment plan name maps to Deal name, total estimated cost maps to Deal amount, and the treatment status maps to Nutshell pipeline stage values. Dr.DENTES treatment codes are preserved in a custom field. The Deal amount is set to the estimated cost, and the actual paid amount is captured separately in a custom field after treatment completion.

Dr.DENTES

Appointment

maps to

Nutshell

Event

1:1
Fully supported

Dr.DENTES appointment records migrate as Nutshell Events with original start and end times, appointment type (exam, cleaning, procedure), and linked Person preserved. The original appointment ID is stored in a custom field for reconciliation against Dr.DENTES records. All Events are linked to the corresponding Person record to maintain a complete activity timeline.

Dr.DENTES

Appointment Activity Notes

maps to

Nutshell

Task

1:1
Fully supported

Treatment notes, clinical observations, and post-appointment notes from Dr.DENTES migrate as Nutshell Tasks attached to the Person or Deal record. Original timestamps and staff author information are preserved from Dr.DENTES. Each Task includes a category field to differentiate clinical notes, administrative comments, and follow-up actions for straightforward reporting.

Dr.DENTES

Insurance Information

maps to

Nutshell

Custom Fields on Person/Company

1:1
Fully supported

Dr.DENTES insurance carrier, policy number, and coverage details have no direct Nutshell equivalent. We create custom fields (Insurance_Carrier__c, Policy_Number__c, Coverage_Type__c) on the Person object to preserve this data for billing reference. These fields are indexed for searchability and can be included in Nutshell reports for insurance reconciliation.

Dr.DENTES

Referral Source

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Dr.DENTES referral source tracking (patient referral, external referral, marketing campaign) maps to a custom Referral_Source__c pick-list field on Nutshell Person. Referral source history is preserved as a text field for reporting continuity. The pick-list values are configured to match the source options, and a fallback text field captures any non-standard entries.

Dr.DENTES

Recall Schedule

maps to

Nutshell

Task + Custom Field

1:1
Fully supported

Dr.DENTES recall schedules for hygiene appointments and follow-up care become Nutshell Tasks with due dates set from the recall interval, attached to the Person record. Recall type (6-month cleaning, annual exam, perio maintenance) is stored in a custom field. These Tasks are set to repeat based on the recall interval, and automated reminders can be configured in Nutshell to support patient re-engagement.

Dr.DENTES

Staff / Practitioner

maps to

Nutshell

Nutshell User

1:1
Fully supported

Dr.DENTES staff and practitioner records map to Nutshell users by email address match. Unmatched staff members are flagged before migration — teams either invite them to Nutshell or assign their patient records to a fallback owner to ensure accountability continuity.

Dr.DENTES

Treatment History

maps to

Nutshell

Task Log on Person

1:1
Fully supported

Completed procedures and treatment history from Dr.DENTES migrate as completed Tasks on the Person record with original treatment dates, procedure codes, and assigned practitioner preserved. This maintains complete clinical records accessible in Nutshell. The Task description includes the procedure description for quick reference, and the related Deal is linked for full context.

Dr.DENTES

Custom Dental Fields

maps to

Nutshell

Custom Fields on Person/Company/Lead

1:1
Fully supported

Dr.DENTES custom fields specific to dental practice (procedure codes, HIPAA consent flags, treatment stage, preferred provider) require custom field creation in Nutshell before migration. We document each field's Dr.DENTES name, data type, and pick-list values for admin setup. The documentation also includes validation rules to ensure imported values conform to the defined pick-list options.

Dr.DENTES

Document / Attachment

maps to

Nutshell

File Attachment on Person/Company

1:1
Fully supported

Patient documents, consent forms, and clinical images attached to Dr.DENTES records are downloaded and re-uploaded as file attachments in Nutshell, linked to the corresponding Person record. File size limits and format compatibility are checked during extraction. We preserve original file names and folder structures to maintain organization and ease of retrieval after migration.

Dr.DENTES

Communication Log

maps to

Nutshell

Task (Type: Email/Call)

1:1
Fully supported

Phone calls, emails, and text message logs from Dr.DENTES migrate as Nutshell Tasks with Type set to Email, Call, or Message. Original timestamps and staff owner are preserved, and tasks are linked to the corresponding Person record. Each Task records the direction (inbound or outbound) for accurate communication history tracking.

Dr.DENTES

Billing / Payment Record

maps to

Nutshell

Deal + Custom Fields

1:1
Fully supported

Dr.DENTES billing and payment records related to treatment plans map to Nutshell Deal custom fields (Amount_Paid__c, Balance_Due__c, Payment_Status__c). Individual payment transactions are preserved as Notes on the Deal for accounting reference. These custom fields enable finance teams to generate aging reports and track outstanding balances directly within 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.

Dr.DENTES logo

Dr.DENTES gotchas

High

Turkish-compliance integrations are not portable

High

No published API

Medium

AI radiograph analysis is configuration, not patient data

Low

Voice-capture metadata may not transfer

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

  • Dr.DENTES API access requires direct contact — no self-service developer portal

    Dr.DENTES does not offer a public-facing developer portal or self-service API key issuance. Teams must contact Dr.DENTES via email to request API access and obtain their base URL and endpoint credentials. This adds 3–7 business days to project timelines before FlitStack AI can begin data extraction. If API access is denied or unavailable, migration falls back to structured manual CSV export with field mapping developed from Dr.DENTES record inspection — which extends planning time and may limit field coverage.

  • Dental-specific fields require Nutshell custom field pre-setup before migration

    Dr.DENTES stores insurance carrier, policy number, procedure codes, HIPAA consent dates, referral source, and recall intervals as native patient record properties. Nutshell's standard Person and Company objects have no direct equivalents for these dental-specific fields. We create custom fields (Insurance_Carrier__c, Policy_Number__c, Referral_Source__c, HIPAA_Consent_Date__c, Treatment_Code__c, Next_Recall_Date__c) in Nutshell during migration setup, but these must be configured in your Nutshell account before the migration run executes. If custom field creation is skipped or delayed, dental-specific data is preserved in a staging file for post-migration import.

  • Dr.DENTES recall scheduling maps to Nutshell Tasks, not native appointment scheduling

    Dr.DENTES recall scheduling (hygiene appointments, perio maintenance, annual exams) is a native scheduling construct with interval-based reminders. Nutshell does not have a native recall scheduling feature — recall dates are preserved as custom datetime fields on Person records and hygiene follow-ups become Nutshell Tasks with due dates. If your team relies on Dr.DENTES recall reminders for patient re-engagement, those reminders must be rebuilt using Nutshell Tasks and its automation triggers or a third-party scheduling integration.

  • Treatment plan pipeline stages require custom stage configuration in Nutshell

    Dr.DENTES treatment plan statuses (scheduled, in-progress, completed, recall, cancelled) are fixed workflow stages tied to appointment outcomes. Nutshell's pipeline stages are fully customizable per deal. We map Dr.DENTES treatment status to Nutshell pipeline stage values, but your Nutshell admin must create the corresponding stages (with names, probabilities, and forecast categories) in Nutshell before migration. If stage values are not pre-configured in Nutshell, deals default to the first stage in your pipeline.

  • Dr.DENTES billing and payment data maps to Deal custom fields, not a native billing object

    Nutshell does not have a native dental billing or accounts-receivable module. Dr.DENTES billing records (payments made, outstanding balances, insurance adjustments) are preserved as custom fields on the Nutshell Deal (Amount_Paid__c, Balance_Due__c, Payment_Status__c). Individual payment transactions are stored as Notes on the Deal. If your team needs to track payment plans, insurance write-offs, or aging receivables, these require post-migration configuration or integration with a dedicated dental billing tool. We recommend reviewing the custom field mapping with your finance team before go-live to ensure accurate reporting.

Migration approach

Six steps for a successful Dr.DENTES to Nutshell data migration

  1. Request Dr.DENTES API access and map the data model

    FlitStack AI contacts Dr.DENTES support to request API credentials and endpoint access. We inspect the Dr.DENTES data model to identify all patient record fields, appointment objects, treatment plan structures, custom fields, and activity logs available for export. This step determines whether API access is granted, which objects are accessible, and whether any data requires manual CSV export fallback. We deliver a data discovery report listing every Dr.DENTES field and its proposed Nutshell mapping target.

  2. Configure Nutshell custom fields for dental data

    Before migration runs, your Nutshell admin creates the custom fields identified during discovery — Insurance_Carrier__c, Policy_Number__c, Referral_Source__c, HIPAA_Consent_Date__c, Treatment_Code__c, Treatment_Stage__c, Next_Recall_Date__c, and any other dental-specific fields from Dr.DENTES. We provide a field-creation checklist with field names, data types, and pick-list values so your admin can configure Nutshell correctly. Pipeline stages are also created to match Dr.DENTES treatment plan statuses. All custom fields are tested in a sandbox environment before production migration begins.

  3. Match staff owners and resolve user assignments

    Dr.DENTES staff and practitioner records are matched to Nutshell users by email address. We generate a user-match report showing every Dr.DENTES staff member and their proposed Nutshell user assignment. Unmatched staff members are flagged — your team either invites them to Nutshell first or assigns their patient and deal records to a designated fallback owner. No deal or patient record migrates without a resolved owner to maintain accountability continuity in Nutshell.

  4. Run sample migration with field-level diff

    A representative sample of 50–200 patient records, their associated appointments, treatment plans, and activity notes migrates to Nutshell first. We generate a field-level diff comparing source Dr.DENTES values against destination Nutshell values for every mapped field, including custom fields. You review the sample in Nutshell and approve field mapping adjustments before the full migration run commits. This validation step catches missing custom fields, incorrect value mappings, and owner resolution gaps before record volume scales.

  5. Execute full migration with delta-pickup window

    All Dr.DENTES records — patient Person records, Company entities, treatment Deal records, appointment Events, and activity Tasks — migrate to Nutshell using the validated field mapping. A 24–48 hour delta-pickup window opens simultaneously, capturing any records created or modified in Dr.DENTES during the migration run. After the initial migration completes, delta records are imported to bring Nutshell to the final Dr.DENTES state at go-live. The audit log records every operation, and one-click rollback is available if reconciliation identifies data discrepancies.

Platform deep dives

Context on both ends of the pair

Dr.DENTES logo

Dr.DENTES

Source

Strengths

  • Cloud-based, multi-device (phone, tablet, PC, smart TV) access with unlimited users, devices, and patients.
  • Long product tenure since 1992 inside Sanal Software, giving a stable feature catalogue.
  • Built-in Turkish-compliance integrations (USS/e-Nabız, e-Reçete, e-Invoice).
  • AI-based radiograph analysis, voice-driven photo capture, and multi-language UI (9 languages) included.
  • Subscription pricing from $120/year with a no-credit-card free trial.

Weaknesses

  • Geography- and compliance-tied to Turkey; less relevant for clinics outside that market.
  • Minimal public review footprint compared with Western dental PMs.
  • No documented public API or developer portal; integrations rely on the vendor.
  • Reporting is descriptive rather than a configurable BI layer.
  • Turkish-compliance bridges are non-portable and must be rebuilt in the destination during migration.
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 Dr.DENTES 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

    Dr.DENTES: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Dr.DENTES 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 Dr.DENTES to Nutshell data migrations

Answers to the questions buyers ask most during Dr.DENTES to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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

Book a free 30 minute consultation

Most Dr.DENTES to Nutshell migrations complete in 5–10 business days for record volumes under 10,000. The timeline extends to 10–15 business days when custom field configuration, multi-stage pipeline setup, and delta-pickup validation are included. Dr.DENTES API access requests add 3–7 days before extraction begins. Practices with complex recall schedules or multi-location data require additional scoping time. These estimates assume the API is available; otherwise, manual export timelines may add an extra week.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Dr.DENTES.
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