CRM migration

Migrate from Core Practice to Nutshell

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

Core Practice logo

Core Practice

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

11 of 11

objects map 1:1 between Core Practice and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Core Practice and Nutshell occupy different functional niches: Core Practice is dental practice management software combining clinical records, patient scheduling, and practice operations in one platform; Nutshell is a general-purpose CRM optimized for sales pipeline management, contact tracking, and sales automation for small to medium businesses. The data models share only the foundational CRM objects — People (contacts), Companies (accounts), and Activities (tasks/events) — but Core Practice's clinical data layer (treatment plans, clinical notes, tooth charts, appointment types) has no native equivalent in Nutshell's schema. FlitStack AI's migration carries Core Practice contacts and companies as direct maps into Nutshell People and Companies, translates appointments into Nutshell Events with original timestamps and assigned owners, and preserves clinical fields as Nutshell custom fields. However, treatment records, clinical notes, and tooth-chart data cannot be rendered in Nutshell's structure — these require either a separate clinical system, manual re-entry, or a referral to your next dental practice management tool. We handle the migration via Nutshell's JSON-RPC API using the account's API credentials, preserving original create dates as custom fields, matching owners by email, and running a delta-pickup window before cutover so in-flight appointments during the transition window are captured.

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

Core Practice logo

Core Practice

What's pushing teams away

  • Excessive clicks and overcomplicated workflows frustrate staff and slow down appointment booking.
  • Patients are reported lost due to poor data integrity and unreliable patient record management.
  • The platform scores poorly on ease of use, value for money, and customer service compared to competitors.
  • Low review volume (6 verified reviews) suggests limited adoption and a lack of community resources.
  • Users report the software is useless at making appointments, directly undermining core dental practice operations.

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 Core Practice objects map to Nutshell

Each row shows how a Core Practice 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.

Core Practice

Patient

maps to

Nutshell

Person

1:1
Fully supported

Core Practice Patient maps directly to Nutshell Person. Demographics (name, phone, email, address) transfer as standard Person fields. Nutshell does not have a patient/clinical concept — medical history and clinical flags transfer as custom fields on the Person record for reference and historical tracking purposes.

Core Practice

Company / Dental Practice

maps to

Nutshell

Company

1:1
Fully supported

Core Practice stores referring practices and partner organizations as Company entities. These map 1:1 to Nutshell Company records. Company phone, website, address, and industry fields align directly with Nutshell's standard Company field set for immediate usability.

Core Practice

Appointment

maps to

Nutshell

Event

1:1
Fully supported

Core Practice Appointments carry provider name, procedure code, chair time, and clinical notes. These translate to Nutshell Events with original start/end times preserved, owner matched by email, and appointment type stored as a custom field. Clinical notes move to a custom field; they cannot render as native Nutshell activity content.

Core Practice

Treatment Plan

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Core Practice treatment plans (procedures, diagnoses, clinical notes) have no Nutshell equivalent. We preserve treatment plan summaries and key procedure codes as custom fields on the Person record. Full clinical documentation requires a separate clinical system or manual re-entry.

Core Practice

Insurance / Billing Record

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Core Practice insurance carrier, policy number, group number, and billing status have no Nutshell equivalent. We map these to custom fields on the Person record for contact reference. Nutshell does not support insurance billing workflows, claims tracking, or coverage verification.

Core Practice

Lead / Referral Source

maps to

Nutshell

Lead

1:1
Fully supported

Core Practice referral sources and incoming leads map to Nutshell Leads. Referral source name and lead status transfer as standard Nutshell Lead fields. Leads without a converted opportunity remain in the Nutshell Lead queue for follow-up.

Core Practice

Provider / Staff Member

maps to

Nutshell

Nutshell User (via Person)

1:1
Fully supported

Core Practice providers and staff map to Nutshell Users for activity assignment. Owner resolution uses email match — Core Practice staff email addresses are matched against Nutshell user emails. Unmatched staff become inactive Person records flagged for admin review.

Core Practice

Custom Patient Field

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Core Practice custom fields on patients (clinical flags, internal IDs, referral tracking) require corresponding Nutshell custom fields. We create these via Nutshell's Settings → Customize → People before migration and map values field-by-field.

Core Practice

Clinical Note / Tooth Chart

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Core Practice clinical notes and tooth chart data have no Nutshell structural equivalent. We export these as text blobs in custom fields on the Person record for historical reference. This data is not actionable in Nutshell — practices requiring clinical workflows should retain a separate clinical system.

Core Practice

File Attachment

maps to

Nutshell

Nutshell Attachments

1:1
Fully supported

Core Practice file attachments on patient records re-upload to Nutshell as file attachments on the corresponding Person record. We download files, re-upload to Nutshell, and maintain the association by record link. Original file names and content types are preserved.

Core Practice

Appointment Reminder / Communication

maps to

Nutshell

Task

1:1
Fully supported

Core Practice appointment reminders and patient communications map to Nutshell Tasks with Type='Other'. Original sent dates and communication content are preserved. SMS reminders do not transfer — Nutshell's SMS module requires separate configuration.

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.

Core Practice logo

Core Practice gotchas

High

No publicly documented public API for direct data extraction

High

Proprietary patient archiving logic can silently drop records

Medium

Appointment booking reliability is a documented weakness

Medium

Limited review volume limits migration confidence

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 data has no structural home in Nutshell

    Core Practice stores treatment plans, clinical notes, tooth charts, procedure histories, and medical history flags as core data — these are the primary value of the dental practice management system. Nutshell has no clinical object, no procedure code model, and no tooth-chart structure. FlitStack preserves these as text blobs in custom fields on the Person and Event records, but they are reference-only. Practices that rely on Core Practice for clinical documentation must plan a parallel clinical system or accept that this data will not be actionable in Nutshell. This is not a migration gap — it is a fundamental platform incompatibility that must be addressed before migration day.

  • Nutshell's per-contact pricing tier affects total cost after migration

    Nutshell bills per user plus per-contact tiers (up to 100, 500, 1,000, 2,500, 5,000+ contacts). Core Practice migrations that bring large patient databases into Nutshell may push teams into higher contact tiers, adding $5–$67/month in email marketing costs depending on volume. We surface the projected Nutshell contact tier during scoping so teams can model the post-migration cost before committing. The data migrates regardless, but the billing tier change should be anticipated.

  • Appointment-to-Event mapping loses clinical context flags

    Core Practice appointment records carry clinical flags (procedure completed, treatment needed, insurance verified) that determine clinical workflow. When these map to Nutshell Events, the flags become static custom field values — there is no way to trigger Nutshell workflows or tasks from clinical flags because Nutshell has no clinical automation model. Practices using appointment flags to drive downstream clinical tasks will need to rebuild that logic manually in Nutshell or retain a separate clinical tracking system.

  • Owner resolution by email may leave orphaned activities

    Nutshell's activity model requires an owner (user) on every Event. Core Practice providers and staff map to Nutshell users by email match. Staff records without valid email addresses or without a corresponding Nutshell user account are flagged before migration. Any appointments assigned to unresolved staff land as Events under a fallback owner — we surface the count during scoping so your team can decide whether to pre-create Nutshell users for all providers or accept the fallback assignment.

  • Insurance billing data is reference-only post-migration

    Core Practice insurance records (carrier, policy number, group number, subscriber info, coverage percentages) are practice-operation data with no Nutshell equivalent. We migrate these fields as custom fields on the Person record for contact reference. However, Nutshell does not have a billing module, claims tracking, or coverage verification workflow. Practices that use Core Practice for insurance management must plan a separate billing workflow solution — the insurance data in Nutshell serves as a lookup only.

Migration approach

Six steps for a successful Core Practice to Nutshell data migration

  1. Audit Core Practice data model and export schema

    We extract Core Practice data via the platform's export tools and API, cataloging all patient fields, company fields, appointment fields, custom fields, and file attachments. We identify which fields have clinical content (treatment plans, tooth charts, procedure codes) versus operational content (contact info, scheduling). This audit produces the field-level mapping plan and surfaces which data will land as Nutshell custom fields versus standard fields.

  2. Create Nutshell custom fields and configure schema

    Before data moves, we create all required Nutshell custom fields — custom fields on Person for insurance data, treatment summaries, and clinical notes; custom fields on Event for procedure codes, appointment types, and clinical flags; custom fields for original create dates and source system IDs. We use Nutshell's Settings → Customize interface to pre-build the schema so the data lands in the correct fields on the first migration run.

  3. Resolve Core Practice providers to Nutshell users by email

    Core Practice staff and provider records are matched against Nutshell user accounts by email address. Unmatched providers are flagged with a pre-migration report — your team either creates Nutshell user accounts for them or designates a fallback owner before migration. No appointment Event lands without an owner; unresolved records are held until the fallback owner is confirmed to prevent orphaned activities.

  4. Run sample migration with field-level diff

    A representative slice of 100–500 records (mix of patients, companies, appointments, and leads) migrates first. We generate a field-level diff comparing source values to destination values across all standard and custom fields, verifying that appointment timestamps, provider ownership, custom field content, and file attachments all landed correctly. You review the diff before the full migration is scheduled.

  5. Execute full migration with delta-pickup cutover window

    Full migration runs against Nutshell via the JSON-RPC API. A delta-pickup window (24–48 hours after the initial run) captures any Core Practice records created or modified during the cutover. All operations are logged in an audit report. One-click rollback is available if reconciliation identifies unexpected gaps. Post-migration, we deliver a reconciliation report comparing record counts and field-level coverage between source and destination.

Platform deep dives

Context on both ends of the pair

Core Practice logo

Core Practice

Source

Strengths

  • Cloud-based with no server maintenance or upfront capital costs.
  • No lock-in contracts allow month-to-month commitment.
  • Australian-hosted infrastructure for local data residency compliance.
  • All-in-one bundling of commercial, clinical, and clerical functions.
  • Real-time access from any device for multi-location practices.

Weaknesses

  • Extremely low review rating (2.7/5) indicating widespread user dissatisfaction.
  • Only 6 verified reviews exist, making independent evaluation difficult.
  • Poor ease-of-use scores (3.0/5) reflect overcomplicated workflows.
  • Weak customer service ratings (2.6/5) from the small reviewer base.
  • Minimal third-party integrations and limited API documentation published.
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 Core Practice 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

    Core Practice: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Core Practice 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 Core Practice to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Core Practice to Nutshell migrations complete in 24–72 hours for setups under 25,000 records. Larger practices with 25,000+ records, multiple custom fields on patients and appointments, and extensive appointment history extend to 5–10 days. The longest planning step is creating Nutshell custom fields for clinical reference data and resolving provider-to-user mappings before migration day. The actual data transfer runs relatively quickly once schema configuration is complete.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Core Practice.
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