CRM migration
Field-level mapping, validation, and rollback between The Practice and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
The Practice
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between The Practice and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
The Practice stores coaching-client records as People, practices as Companies, sessions and notes as Activities, and custom fields for therapy modality, session rate, and client status. Nutshell models the same data as People (Contacts), Companies, Activities (calls/notes/tasks), and custom fields scoped per plan tier. We map Practice People directly to Nutshell People with all standard contact fields preserved, Company records map to Nutshell Companies, custom practice fields (therapy_modality, session_rate, client_status) migrate as Nutshell custom fields, and session/activity history transfers as Nutshell Activities with original timestamps. Nutshell's pipeline model is simpler than multi-pipeline CRMs — one pipeline with configurable stages — so deal data from Practice routes into a single Nutshell pipeline. Workflows, automations, and client-portal settings do not transfer; we export definitions as a rebuild reference for Nutshell automation setup. We read from Practice via scoped API access, transform records to Nutshell's schema, and load via Nutshell's JSON-RPC API with field-level validation before commit.
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 The 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.
The Practice
Person
Nutshell
People
1:1Practice Person records migrate directly to Nutshell People. Standard contact fields—first name, last name, email, phone, address, job title—map to their Nutshell equivalents. The original Practice person record ID is stored in a custom Source_ID__c field, enabling delta-run de-duplication and allowing the migration tool to reference the source ID via Nutshell's JSON-RPC API when loading data.
The Practice
Person custom fields
Nutshell
People custom fields
1:1Practice therapy_modality, session_rate, referral_source, primary_insurance, and client_status fields require Nutshell custom fields. We assess the target Nutshell plan's field limits (5 on Essential, 20 on Pro, more on Business/Enterprise) and produce a consolidation map if the practice exceeds the target plan's limits before migration runs.
The Practice
Company
Nutshell
Company
1:1Practice Company records map to Nutshell Company records. Name, website, industry, phone, and address fields carry over directly. If Practice stores multiple locations of the same practice under separate Company records, they remain separate Companies in Nutshell — no hierarchical collapse occurs since Nutshell supports flat company records.
The Practice
Company custom fields
Nutshell
Company custom fields
1:1Any Practice Company-level custom fields—such as practice_type, npi_number, or tax_id—are mapped to Nutshell Company custom fields, respecting plan-tier limits (5 on Essential, 20 on Pro, more on Business/Enterprise). The migration audit compares the practice’s field count to the target plan and flags any that exceed the limit, supplying a consolidation recommendation—merging values or storing overflow in a Note—before migration.
The Practice
Lead / unqualified person
Nutshell
Lead
1:1Practice leads that have not converted to active clients migrate as Nutshell Lead records. Lead name, contact info, source, and status map to Nutshell Lead fields. We preserve the original lead creation date as a custom Lead_Created_Date__c field since Nutshell Lead CreatedDate is set at migration time.
The Practice
Deal (session package, billing record)
Nutshell
Deal
1:1Practice deal records (session packages, billing agreements, recurring payment plans) map to Nutshell Deals. Practice deal stage (e.g., 'Active', 'Completed', 'Cancelled') maps to Nutshell Deal stage values via value mapping. Amount fields transfer directly; if Practice stores recurring amounts, we map to Nutshell Deal amount and note the periodicity in a custom field.
The Practice
Activity (session log, note, task)
Nutshell
Activity (call, email, note, task)
1:1Practice session logs, notes, and tasks migrate as Nutshell Activities with type classification (Call for session logs, Note for notes, Task for action items). Original timestamps, owner email addresses, and associated Person/Company links are preserved. Nutshell's activity feed attaches each record to the correct People or Company page.
The Practice
Attachment / file
Nutshell
File attachment
1:1Practice file attachments on client records (session PDFs, signed forms, assessment documents) re-upload to Nutshell as file attachments on the corresponding People record. Nutshell's file size limits (25MB per file) apply; files exceeding the limit are flagged for manual handling or split before upload.
The Practice
Tag / label
Nutshell
Note
1:1Practice tag labels (e.g., 'VIP client', 'referral partner', 'billing issue') have no direct Nutshell equivalent. We migrate tag names as Nutshell Note records attached to the Person record, storing the original tag string for reference. Clients who rely heavily on tags should review the tag list before migration and decide whether to collapse into a smaller set or preserve as note history.
The Practice
User / owner
Nutshell
User
1:1Practice user accounts are resolved against Nutshell users by email match. Active Practice users must have Nutshell user accounts created before migration; unmatched owners are flagged and assigned to a fallback Nutshell user. We capture the Practice owner ID in a custom Original_Owner_ID__c field on each record for post-migration audit.
The Practice
Workflow / automation
Nutshell
Not migratable
1:1Practice workflows (client onboarding reminders, session follow-up automations, billing notifications) do not transfer. We export the workflow definitions including trigger conditions, action steps, and timing rules as a structured PDF reference document that the practice admin can use to rebuild equivalent automations in Nutshell's workflow builder.
| The Practice | Nutshell | Compatibility | |
|---|---|---|---|
| Person | People1:1 | Fully supported | |
| Person custom fields | People custom fields1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Company custom fields | Company custom fields1:1 | Fully supported | |
| Lead / unqualified person | Lead1:1 | Fully supported | |
| Deal (session package, billing record) | Deal1:1 | Fully supported | |
| Activity (session log, note, task) | Activity (call, email, note, task)1:1 | Fully supported | |
| Attachment / file | File attachment1:1 | Fully supported | |
| Tag / label | Note1:1 | Fully supported | |
| User / owner | User1:1 | Fully supported | |
| Workflow / automation | Not migratable1: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.
The Practice gotchas
No public API means all migration data must be extracted manually
Session recordings and large files require separate manual download
Client group and tag inheritance is not automatically preserved in exports
Contract PDFs are stored as linked files, not embedded records
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 Practice data and assess Nutshell plan-tier field limits
FlitStack connects to Practice via scoped read access and exports a full inventory of People, Companies, Deals, Activities, and all custom field definitions. We cross-reference the custom field count against the target Nutshell plan's field limits (Essential: 5, Pro: 20, Business/Enterprise: more). If the practice exceeds the target plan's limits, we produce a consolidation map identifying which fields to migrate as custom fields and which to collapse into Note records. This audit also flags files exceeding Nutshell's 25MB attachment limit and identifies any Practice workflows for the export-for-rebuild reference document.
Resolve owner and user mapping between Practice and Nutshell
Before any records move, we match Practice user accounts against Nutshell user accounts by email address. Each Practice owner must have a corresponding Nutshell user account created. Unmatched owners are flagged with the owner's Practice email and name — the practice admin creates the Nutshell user or assigns a fallback Nutshell user before migration. No record migrates without a resolved owner; this prevents orphaned records in Nutshell and maintains accountability on activity history.
Migrate Companies first, then People and Leads, then Deals and Activities
Nutshell requires Company records to exist before People can be associated via the Company field. We sequence the migration as follows: (1) Companies — all practice company records and their custom fields; (2) People — all client Person records linked to Companies, with custom fields and original create dates preserved; (3) Leads — unqualified prospects that have not converted to clients; (4) Deals — session packages and billing records linked to the correct Person; (5) Activities — session logs, notes, and tasks with original timestamps and owner links. This sequence ensures foreign-key integrity throughout the load.
Run a sample migration with field-level diff before full commit
A representative slice of Practice data — typically 100–300 records spanning People, Companies, Deals, and Activities — migrates first. We generate a field-level diff comparing source values in Practice against destination values in Nutshell. The practice admin reviews custom field mapping, tag-to-note conversion, deal stage values, and owner resolution. Any mapping corrections are applied before the full migration runs. This step is the quality gate that prevents bulk data from landing incorrectly.
Execute full migration with delta-pickup window and audit log
The full migration runs against Nutshell's JSON-RPC API. A delta-pickup window (typically 24–48 hours after the main load) captures any Practice records created or modified during the cutover period, so Nutshell reflects Practice's final state at go-live. Every migration operation is recorded in an audit log — record counts, field mapping applied, owner resolution results, and any errors encountered. One-click rollback is available if post-migration reconciliation identifies data integrity issues.
Platform deep dives
The 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 The 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
The Practice: Not publicly documented.
Data volume sensitivity
The 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 The Practice to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your The 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 The 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.