CRM migration
Field-level mapping, validation, and rollback between PracticeHub and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
PracticeHub
Source
Nutshell
Destination
Compatibility
10 of 11
objects map 1:1 between PracticeHub and Nutshell.
Complexity
BStandard
Timeline
24–48 hours
Overview
PracticeHub and Nutshell occupy fundamentally different problem spaces: PracticeHub is a healthcare practice-management platform centered on patient appointments, clinical notes, and clinic-facing workflows, while Nutshell is a sales CRM built around People, Companies, Leads, and multi-pipeline Deal management. When migrating from PracticeHub to Nutshell, the core CRM objects — people records and company records — map directly. Appointment summaries, patient library references, and any clinical context stored in PracticeHub custom fields become Nutshell Notes attached to the corresponding People record, preserving the original content without forcing it into a schema that was never designed for clinical data. FlitStack AI extracts data from PracticeHub via its REST API, respecting the 1 request per second rate limit by pacing export runs. We build a pre-migration field map against Nutshell's custom-field model (People, Company, Lead tabs), create any missing custom fields in your Nutshell account before the load, then push records through Nutshell's JSON-RPC API. Workflows, automations, and patient-library binaries (images, exercise routines) do not have equivalents in Nutshell — we export definitions for rebuild reference but they cannot be transferred. Files and attachments re-upload to Nutshell Files or attach to the relevant record. A sample migration with field-level diff runs first so you can verify the People/Company split and note-style storage of appointment data before the full cutover commits.
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 PracticeHub 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.
PracticeHub
Person (patient)
Nutshell
Person
1:1PracticeHub person records (patients) map one‑to‑one to Nutshell People, preserving first name, last name, email address, phone numbers, and street details as native fields. Patient‑specific attributes such as date of birth, medical notes, or insurance identifiers are transferred to pre‑created custom fields on the Person object, keeping the core contact profile clean while retaining clinical context.
PracticeHub
Company (clinic or referring practice)
Nutshell
Company
1:1PracticeHub clinic and referring‑organisation records map directly to Nutshell Companies, carrying over company name, primary address, website domain, and industry classification as standard fields. When the source includes a parent‑clinic relationship, we link the child record to the parent via Nutshell's Parent Company field, preserving multi‑location hierarchies and ensuring that organisational structure is reflected in the CRM.
PracticeHub
Appointment
Nutshell
Note (attached to Person)
1:1Each appointment (date, time, practitioner, type, status) becomes a Note attached to the corresponding Nutshell Person. We preserve the original appointment date as a formatted line inside the note body. If appointments are numerous, we can consolidate them into a single summary note per person with a table of all appointment dates.
PracticeHub
Patient library (images, exercise routines)
Nutshell
File attachment on Person
1:1PracticeHub's patient library stores clinical images and exercise routines. Nutshell has no clinical document concept. We download each file, re-upload it to Nutshell Files, and attach it to the corresponding Person record. Your team decides which files to keep for non-clinical reference.
PracticeHub
Practitioner / staff member
Nutshell
Person (tagged with role custom field)
many:1Practitioners and staff members are contacts in PracticeHub but not clinical patients. We migrate them as Nutshell People with a Role custom field set to 'Practitioner' or 'Staff'. Owner resolution (which Nutshell user maps to each practitioner) uses email matching.
PracticeHub
Lead (referral source)
Nutshell
Lead
1:1Referral sources and inbound enquiries stored as leads in PracticeHub transfer directly to Nutshell Leads, preserving the lead’s name, email, phone, source tag, and any custom lead‑specific attributes. We resolve the status pick‑list values against Nutshell’s lead status options during mapping, ensuring that the original lead stage is reflected accurately in the CRM without manual re‑entry.
PracticeHub
Custom field (patient-specific)
Nutshell
Custom field on Person
1:1Any custom fields on PracticeHub patient records (for example, insurance provider, emergency contact, preferred language) require pre-created custom fields in Nutshell. We inventory all custom fields during discovery, create them in Nutshell (People tab), then map values field-by-field during the load.
PracticeHub
Clinic messaging thread
Nutshell
Note (attached to Person)
1:1PracticeHub's in-app clinic messaging threads are not email-equivalent in Nutshell. We export the full thread as plain text and attach it as a Note to the relevant Person. The note header records the thread date range so context is not lost.
PracticeHub
Intake form submission
Nutshell
Note (attached to Person)
1:1Completed intake forms are exported as a formatted note attached to the corresponding Nutshell Person record. Each form field label is paired with its entered value in a clear key‑value layout, allowing your team to review the full intake context directly in Nutshell without needing to refer back to the original PracticeHub system.
PracticeHub
Billing / payment record
Nutshell
Note (attached to Person)
1:1Payment history and billing records do not have a native CRM object in Nutshell, so we export a concise billing summary as a Note attached to the Person record. The note captures the invoice date, amount, and payment status, while your primary billing or accounting system continues to hold the authoritative financial record for audit and compliance.
PracticeHub
PracticeHub owner / practitioner
Nutshell
Nutshell user
1:1PracticeHub practitioner and admin accounts are matched to Nutshell users using the email address as the unique key. Before the migration begins, any practitioner lacking a corresponding Nutshell user account is flagged for resolution; you can either create the user in Nutshell in advance or assign the records to a designated fallback owner, ensuring no data is left without a responsible user after the cutover.
| PracticeHub | Nutshell | Compatibility | |
|---|---|---|---|
| Person (patient) | Person1:1 | Fully supported | |
| Company (clinic or referring practice) | Company1:1 | Fully supported | |
| Appointment | Note (attached to Person)1:1 | Fully supported | |
| Patient library (images, exercise routines) | File attachment on Person1:1 | Fully supported | |
| Practitioner / staff member | Person (tagged with role custom field)many:1 | Fully supported | |
| Lead (referral source) | Lead1:1 | Fully supported | |
| Custom field (patient-specific) | Custom field on Person1:1 | Fully supported | |
| Clinic messaging thread | Note (attached to Person)1:1 | Fully supported | |
| Intake form submission | Note (attached to Person)1:1 | Fully supported | |
| Billing / payment record | Note (attached to Person)1:1 | Fully supported | |
| PracticeHub owner / practitioner | Nutshell user1: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.
PracticeHub gotchas
1 req/sec API rate limit severely restricts bulk migration speed
Region-specific API base URLs must be resolved before extraction
Patient Library assets export as separate binary blobs
Prescription records may reference external Chewy pharmacy integration
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
Inventory PracticeHub records and create Nutshell custom fields
FlitStack AI exports a full record inventory from PracticeHub via the REST API — people, companies, appointments, leads, and all custom fields. We pace the export to respect the 1 req/s rate limit. Against that inventory, we compare Nutshell's standard field list and create any missing custom fields (date of birth, preferred language, insurance provider, emergency contact, and source system ID) in your Nutshell account under Settings > Custom Fields before the first record is loaded. This pre-creation step is required because Nutshell does not auto-provision custom fields during API inserts.
Map and resolve owner accounts by email
PracticeHub practitioner and admin accounts are matched against Nutshell users by email address. Any practitioner in PracticeHub who does not have a corresponding Nutshell user is flagged with a pre-migration warning — you either provision the Nutshell user first or assign their records to a fallback owner during the load. No record lands without a resolved owner, which prevents orphaned records in Nutshell's assignment model.
Run a sample migration with field-level diff
A representative slice — typically 100–300 records across people, companies, and leads — migrates first. We generate a field-level diff showing every PracticeHub field and its resolved Nutshell value. You verify appointment-to-note conversion, custom field population, and owner resolution before we commit to the full run. This is the checkpoint where we confirm that the appointment-summary note format meets your team's readability requirements.
Execute full migration with delta-pickup window
The full dataset loads through Nutshell's JSON-RPC API. A delta-pickup window (typically 24–48 hours) captures any new or modified records created in PracticeHub during the cutover period. All file attachments are downloaded from PracticeHub, re-uploaded to Nutshell Files, and attached to the corresponding Person record. An audit log records every operation; one-click rollback is available if reconciliation reveals record counts or field-population issues.
Deliver reconciliation report and rebuild reference export
FlitStack AI delivers a post-migration reconciliation report comparing PracticeHub record counts and key field values against Nutshell. We export PracticeHub workflow definitions and intake-form templates as a structured reference document so your team can rebuild appointment-reminder sequences and intake automations in Nutshell's personal email sequences tool. Reports, dashboards, and billing records are not migrated — the export document captures their structure for manual recreation.
Platform deep dives
PracticeHub
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 PracticeHub and Nutshell.
Object compatibility
2 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
PracticeHub: 1 request per second per account.
Data volume sensitivity
PracticeHub 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 PracticeHub to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your PracticeHub 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 PracticeHub
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.