CRM migration

Migrate from Curve Dental to Nutshell

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

Curve Dental logo

Curve Dental

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

13 of 13

objects map 1:1 between Curve Dental and Nutshell.

Complexity

BStandard

Timeline

3–5 business days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Curve Dental is a cloud-native dental practice management system — it owns the clinical layer (patient records, treatment plans, tooth charts, insurance, billing, and imaging) plus scheduling and daily ops. Nutshell is a general SMB CRM with People, Companies, Deals, and Activities — it has no native dental object equivalents. FlitStack AI migrates the data that fits: patient demographics, addresses, contact methods, company records, deal pipelines, appointments, and activities. The dental-specific layer (treatment plans, clinical notes, tooth charts, x-rays, insurance eligibility, billing ledgers) gets mapped to Nutshell People custom fields and file attachments, or surfaced as a manual-rebuild checklist since Nutshell's schema does not support clinical workflow primitives. We use Curve's export tools and API for extraction, then bulk-load into Nutshell via their JSON-RPC API respecting rate limits. A scoped-read delta window (24–48 hours) captures records created or modified during cutover, and an audit log plus one-click rollback covers reconciliation failures.

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

Curve Dental logo

Curve Dental

What's pushing teams away

  • Reporting module is slow and cumbersome on large databases. Users report that reports timeout before loading, cannot be filtered before running, and lack preview functionality — a significant pain point for practices that rely on data-driven decision-making.
  • Customization limits frustrate power users. Practices that need to modify workflows, build custom integrations, or tweak the system beyond Curve's opinionated defaults find the platform constraining compared to open-source alternatives.
  • Confusing billing and payment workflows generate negative reviews. Multiple Capterra reviewers cite the billing and payment processes as a pain point, with complexity around claims posting, insurance reconciliation, and patient invoices.
  • Pricing transparency is limited — no public tier structure. Prospective customers must speak with a sales representative, and some reviews mention uncertainty about what they were paying for versus what was included.

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

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

Curve Dental

Patient / Person Record

maps to

Nutshell

People

1:1
Fully supported

Patient demographics (name, DOB, address, phone, email) map directly to Nutshell People fields with the same names. Clinical sub-records including treatment plans, tooth charts, and clinical notes are stored as custom text fields on the People record since Nutshell has no native clinical object model. Imaging files and x-rays attach as Nutshell Files to the associated People record for complete patient document retention.

Curve Dental

Appointment Record

maps to

Nutshell

Task

1:1
Fully supported

Curve appointments containing date, time, provider, operatory, and procedure type become Nutshell Tasks with a custom Procedure_Type__c field capturing the appointment category. OwnerId assignment uses email matching to resolve each provider against existing Nutshell Users. Recurring recall appointments map as repeating Tasks or as a custom recall schedule field on the associated People record for ongoing patient follow-up.

Curve Dental

Company / Referring Practice

maps to

Nutshell

Company

1:1
Fully supported

Referral source companies and group dental practices map directly to Nutshell Companies using direct field mapping for address, domain, and industry. Multi-location assignments requiring assignment to specific practice sites are stored as a custom Locations__c field or a separate Locations custom object to maintain accurate location records for multi-office dental groups.

Curve Dental

Treatment Plan

maps to

Nutshell

People custom_field_required

1:1
Fully supported

Curve stores treatment plans as clinical sub-records with procedure codes, tooth numbers, and fee estimates. Nutshell has no treatment plan object — all fields including procedure code, tooth number, fee, status, and provider assignment map to custom fields on the associated People record. The treatment plan data serializes as structured text for provider reference.

Curve Dental

Clinical Note / Progress Note

maps to

Nutshell

People custom_field_required

1:1
Fully supported

Clinical notes containing provider narrative, procedure codes, and SOAP format notes become a custom Clinical_Notes__c long-text area on the People record. Original timestamps from the Curve system and provider names are preserved as separate custom datetime and user fields to maintain full audit trail and provider attribution for clinical documentation.

Curve Dental

Insurance / Payer Record

maps to

Nutshell

People custom_field_required

1:1
Fully supported

Insurance payer name, group number, subscriber ID, and eligibility dates all become custom fields on the People record using the Insurance_Payer__c, Group_Number__c, Subscriber_ID__c, Eligibility_Start__c, and Eligibility_End__c field names. Curve's eligibility status logic maps to a custom Eligibility_Status__c pick-list capturing active, inactive, or pending states for each patient's coverage.

Curve Dental

Billing / Payment Ledger

maps to

Nutshell

People custom_field_required

1:1
Fully supported

Outstanding balance, total charges, and last payment amount become custom currency fields on the People record (Outstanding_Balance__c, Total_Charges__c, Last_Payment_Amount__c, Last_Payment_Date__c). Nutshell has no native billing ledger — the complete ledger history is preserved as a long-text area or exported as a PDF and attached to the People record for financial record retention.

Curve Dental

Imaging / X-Ray File

maps to

Nutshell

People File Attachment

1:1
Fully supported

X-rays and intraoral photos are exported from Curve and re-uploaded as Nutshell Files attached to the corresponding People record for direct patient access. Files exceeding Nutshell's 25MB per-file limit are flagged during pre-migration audit for external storage in Google Drive, Dropbox, or a PACS system, with a URL reference stored in a custom Imaging_URL__c field on the People record.

Curve Dental

Deal / Opportunity

maps to

Nutshell

Deal

1:1
Fully supported

Dental service deals such as comprehensive treatment plans sold as bundled packages map directly to Nutshell Deals using standard Name, Amount, Stage, and Close Date fields. Custom fields capture treatment type and provider assignment for deal-specific tracking. This allows dental groups to track treatment plan conversions and revenue opportunities within Nutshell's native pipeline management.

Curve Dental

Activity (Call, Email, Note)

maps to

Nutshell

Task

1:1
Fully supported

Phone calls, emails, and notes from the Curve activity log migrate as Nutshell Tasks attached to the corresponding People or Company record. Original timestamps and owner emails are preserved during migration. Nutshell does not support clinical activity types natively — these use standard Task Type values to maintain activity history within the CRM.

Curve Dental

Tooth Chart / Clinical Diagram

maps to

Nutshell

People custom_field_required

1:1
Fully supported

Curve tooth chart records containing per-tooth conditions, missing teeth, restored teeth, and treatment codes cannot map to any native Nutshell field or visualization. We map them as a custom Tooth_Chart__c text field storing per-tooth notation as a structured string (e.g., UR1:R, UR2:M, UR3:ML), or alternatively attach the chart image as a Nutshell File on the People record.

Curve Dental

Recall / Maintenance Appointment

maps to

Nutshell

People custom_field_required

1:1
Fully supported

Recall intervals such as 6-month hygiene recalls and annual periodontal maintenance become a custom Recall_Due_Date__c date field and Recall_Type__c pick-list on the People record. Once stored, Nutshell's Workflow Rules can trigger automated email sequences for recall follow-up based on the recall due date, helping maintain patient retention without manual tracking.

Curve Dental

Provider / Staff Record

maps to

Nutshell

Nutshell User

1:1
Fully supported

Curve providers and staff members are resolved by email matching against existing Nutshell Users during migration. Unmatched staff records are flagged and assigned to a fallback Nutshell user before migration completes so all associated tasks and appointments have an assigned owner. Provider specialties store as a custom Provider_Specialty__c field on the User record for reference.

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.

Curve Dental logo

Curve Dental gotchas

High

Reporting timeout on large databases

Medium

Image and x-ray migration requires chunked transfer and post-migration validation

Medium

Accounts receivable balances drift after payment ledger migration

Low

Custom form structure and Smart Forms do not export

Low

Curve Pay dispute fee of $25 per chargeback

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 sub-records have no native Nutshell home — custom fields absorb the schema gap

    Curve Dental stores treatment plans, clinical notes, tooth charts, and SOAP notes as clinical sub-records attached to patient records. Nutshell has no clinical object model — there is no Treatment_Plan__c, Tooth_Chart__c, or Clinical_Note__c out of the box. FlitStack maps these to People custom fields and stores the data as structured text. The tradeoff is that Nutshell cannot enforce procedure-code-level validation or display a graphical tooth chart in its native UI. Practices relying heavily on clinical documentation for case acceptance workflows should treat this as a functional gap and plan to supplement Nutshell with a dental-specific tool or a PDF reference library.

  • Dental imaging files face Nutshell's 25MB per-file attachment limit

    Curve Dental x-rays and intraoral photos can be multi-megabyte files — full-mouth series and CBCT scans regularly exceed 25MB. Nutshell's file attachment mechanism enforces a 25MB per-file size limit for records uploaded via the UI and API. Files exceeding this limit must be handled separately: either exported to an external DMS (Google Drive, Dropbox, or a PACS system) with a URL reference stored in a custom Imaging_URL__c field on the People record, or split into smaller sub-files before upload. We flag every file above 20MB in the pre-migration audit so this decision is made before the cutover begins.

  • Insurance and billing data collapse to flat text fields on People

    Curve Dental maintains insurance payer records, group numbers, eligibility dates, treatment ledgers, and payment posting history as separate native fields with relationship integrity. Nutshell has no Insurance or Billing object — all of this maps to flat custom text, date, and currency fields on the People record. The eligibility status workflow (checking active/inactive per visit) cannot be replicated in Nutshell without manual follow-up or a custom integration. The treatment ledger history is stored as a long-text custom field or attached as a PDF, which limits reporting on historical payment patterns within Nutshell itself.

  • Multi-location assignments require a custom field or Locations object

    Curve Dental supports multi-location practice configurations with separate databases or a centralized location record for each practice site. Nutshell does not have a native multi-location concept — location assignments must be captured via a custom Locations__c field on the People record or a separate Locations custom object with a lookup relationship. We create the custom field during schema setup. Practices with more than three locations should consider a dedicated Locations custom object to avoid a long pick-list on the People record.

  • Appointment scheduling is one-directional with no operatory or provider conflict logic

    Curve Dental's scheduling engine enforces operatory availability, provider schedules, and procedure-time blocks natively. Nutshell has no native scheduling module — appointments migrate as Tasks with custom date and procedure fields, but Nutshell does not prevent double-booking or enforce operatory capacity. The recall workflow can be rebuilt using Nutshell Workflow Rules triggered by Recall_Due_Date__c, but real-time scheduling conflicts require either a Nutshell-connected scheduling tool (e.g., ScheduleOnce, Calendly integration) or a manual process during the go-live period.

Migration approach

Six steps for a successful Curve Dental to Nutshell data migration

  1. Audit and scope the Curve Dental export

    FlitStack requests a full data export from Curve Dental covering patient records, appointment history, company/referral records, insurance entries, treatment plans, clinical notes, tooth chart data, billing ledgers, and file attachments. We inventory record counts per object type, flag imaging files exceeding 25MB, and identify multi-location configurations. This produces a migration scope document that defines the field-level mapping plan before any transformation code is written.

  2. Create Nutshell custom fields and schema objects

    Before data moves, we create all required Nutshell custom fields on the People and Company objects via Settings > Data > Custom Fields: Treatment_Plan__c, Clinical_Notes__c, Tooth_Chart__c, Insurance_Payer__c, Group_Number__c, Subscriber_ID__c, Eligibility_Start__c, Eligibility_End__c, Eligibility_Status__c, Outstanding_Balance__c, Total_Charges__c, Recall_Due_Date__c, Recall_Type__c, and Imaging_URL__c. For multi-location practices, we also create a Locations custom object with a lookup to People. The custom field creation plan is delivered to your Nutshell admin for pre-approval before the migration run.

  3. Build transformation scripts and run a sample migration

    FlitStack extracts data from Curve via your exported files and transforms each record according to the field mapping plan. Appointments become Tasks with owner assignment by email match to Nutshell users. Treatment plans, clinical notes, and tooth charts serialize into the People custom text fields. Insurance and billing data map to their respective custom fields. A representative sample (typically 100–300 patient records plus a cross-section of appointments and companies) migrates first, and we generate a field-level diff report so you can verify mapping accuracy before the full run commits.

  4. Execute full migration with delta-cutover window

    The full record set loads into Nutshell via the JSON-RPC API. Nutshell enforces per-key rate limits — FlitStack batches and throttles requests to avoid 429 errors. A delta-cutover window (24–48 hours) keeps Curve Dental accessible to your team for any final record modifications during the cutover; FlitStack captures these changes and applies them to Nutshell after the initial load. An audit log records every operation. If reconciliation fails, one-click rollback reverts all migrated records to their pre-migration state.

  5. Validate, reconcile, and deliver manual-rebuild checklist

    Post-migration, FlitStack runs a reconciliation check: record counts per object, spot-checks on custom field values for Treatment_Plan__c and Insurance_Payer__c, and file attachment verification. Imaging files exceeding 25MB are reported with their external storage URL. We deliver a manual-rebuild checklist covering dental workflows that cannot migrate — automated appointment reminders, recall campaigns, treatment-plan-triggered sequences, and any integration with dental imaging PACS — so your team has a complete rebuild roadmap from the start.

Platform deep dives

Context on both ends of the pair

Curve Dental logo

Curve Dental

Source

Strengths

  • Cloud-native architecture eliminates server hardware and enables access from any browser or mobile device
  • Fast onboarding with guided implementation: dedicated Project Manager, Data Migration Specialist, and 90-day Account Manager
  • Established conversion process from 90+ source systems with 4,000+ completed migrations documented on their website
  • All-in-one platform integrates charting, scheduling, imaging, billing, payments, and patient engagement under one login and one monthly price
  • AI partnership with Pearl for diagnostic assistance and modern patient engagement tools including Smart Forms and text-to-pay

Weaknesses

  • Reporting module is slow and limited — large database reports timeout, cannot filter before running, and lack preview
  • Billing and payment workflows are a recurring pain point with 70% negative reviews citing confusion
  • Customization limits make Curve constraining for practices that need to modify workflows or build custom integrations
  • No public pricing — all tier information requires a sales conversation, making budget comparison difficult
  • Custom form layout and conditional logic do not export, requiring manual rebuild in the destination PMS
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 Curve Dental 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

    Curve Dental: Not publicly documented.

  • Data volume sensitivity

    A

    Curve Dental exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Curve Dental to Nutshell migrations complete within 3–5 business days for practices with fewer than 25,000 patient records and a standard dental field set. Multi-location practices or those with heavy custom schemas (40+ clinical custom fields, imaging files, multi-insurance records) extend to 7–14 days. The longest phase is the pre-migration audit and schema setup — once Nutshell custom fields are approved and the sample migration validates the mapping, the full load runs in hours. Imaging review and external storage decisions for files exceeding 25MB add 1–2 days if needed.

Adjacent paths

Related migrations to explore

Ready when you are

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