CRM migration
Field-level mapping, validation, and rollback between Core Practice and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Core Practice
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between Core Practice and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Core 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
Nutshell
Company
1:1Core 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
Nutshell
Event
1:1Core 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
Nutshell
Custom Field on Person
1:1Core 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
Nutshell
Custom Field on Person
1:1Core 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
Nutshell
Lead
1:1Core 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
Nutshell
Nutshell User (via Person)
1:1Core 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
Nutshell
Custom Field on Person
1:1Core 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
Nutshell
Custom Field on Person
1:1Core 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
Nutshell
Nutshell Attachments
1:1Core 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
Nutshell
Task
1:1Core 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.
| Core Practice | Nutshell | Compatibility | |
|---|---|---|---|
| Patient | Person1:1 | Fully supported | |
| Company / Dental Practice | Company1:1 | Fully supported | |
| Appointment | Event1:1 | Fully supported | |
| Treatment Plan | Custom Field on Person1:1 | Fully supported | |
| Insurance / Billing Record | Custom Field on Person1:1 | Fully supported | |
| Lead / Referral Source | Lead1:1 | Fully supported | |
| Provider / Staff Member | Nutshell User (via Person)1:1 | Fully supported | |
| Custom Patient Field | Custom Field on Person1:1 | Fully supported | |
| Clinical Note / Tooth Chart | Custom Field on Person1:1 | Fully supported | |
| File Attachment | Nutshell Attachments1:1 | Fully supported | |
| Appointment Reminder / Communication | Task1: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.
Core Practice gotchas
No publicly documented public API for direct data extraction
Proprietary patient archiving logic can silently drop records
Appointment booking reliability is a documented weakness
Limited review volume limits migration confidence
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
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.
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.
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.
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.
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
Core Practice
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Core Practice and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
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
Core Practice: Not publicly documented.
Data volume sensitivity
Core Practice 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 Core Practice to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Core Practice
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.