CRM migration

Migrate from The Practice to Nutshell

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

The Practice logo

The Practice

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

11 of 11

objects map 1:1 between The Practice and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

The Practice logo

The Practice

What's pushing teams away

  • Email reminders send from a generic 'Practice' sender name rather than the practitioner's own name or business name, which clients sometimes ignore or mark as spam.
  • The platform has no public API, which frustrates power users and teams that need to connect The Practice to their existing analytics, billing, or telephony stack.
  • Storage limits on file uploads are not clearly communicated at signup, leading to surprise billing when coaches try to store session recordings or large PDFs.
  • The reporting and export features are limited compared to purpose-built CRM platforms, making it difficult to generate clean data for business reviews or tax preparation.

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

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

maps to

Nutshell

People

1:1
Fully supported

Practice 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

maps to

Nutshell

People custom fields

1:1
Fully supported

Practice 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

maps to

Nutshell

Company

1:1
Fully supported

Practice 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

maps to

Nutshell

Company custom fields

1:1
Fully supported

Any 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

maps to

Nutshell

Lead

1:1
Fully supported

Practice 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)

maps to

Nutshell

Deal

1:1
Fully supported

Practice 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)

maps to

Nutshell

Activity (call, email, note, task)

1:1
Fully supported

Practice 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

maps to

Nutshell

File attachment

1:1
Fully supported

Practice 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

maps to

Nutshell

Note

1:1
Fully supported

Practice 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

maps to

Nutshell

User

1:1
Fully supported

Practice 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

maps to

Nutshell

Not migratable

1:1
Fully supported

Practice 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.

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.

The Practice logo

The Practice gotchas

High

No public API means all migration data must be extracted manually

Medium

Session recordings and large files require separate manual download

Medium

Client group and tag inheritance is not automatically preserved in exports

Low

Contract PDFs are stored as linked files, not embedded records

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

  • Nutshell plan-tier custom field limits may require field consolidation before migration

    Practice allows unlimited custom fields per client record. Nutshell's Essential plan caps custom fields at 5 per module (People, Company, Lead, Deal). Practices using 10–30 custom fields (therapy_modality, session_rate, referral_source, billing_info, emergency_contact, insurance_group, etc.) must assess their target Nutshell plan before migration. FlitStack delivers a custom field inventory from Practice, maps it to the target plan's field count, and provides a consolidation recommendation — collapsing lower-priority fields into a Note record — before data moves. Failing to pre-assess plan tier results in migration errors or truncated custom fields at load time.

  • Practice tag labels have no direct Nutshell equivalent and require a disposition decision

    Practice users frequently tag clients with labels like 'VIP', 'referral partner', 'billing issue', or 'inactive'. Nutshell has no native tag or label system for People or Company records — tags from Practice cannot be mapped to a built-in equivalent. We migrate tag strings as Note records attached to the relevant Person, but this is a reference-only preservation, not an active tagging system. Teams that depend heavily on Practice tags should review the tag inventory during the planning phase and decide whether to select the top 5–10 most critical tags for dedicated custom pick-list fields, collapsing the rest into notes. This decision must be made before migration runs to avoid post-migration data cleanup.

  • Practice workflows and automations do not migrate and require manual rebuild in Nutshell

    Practice stores client onboarding sequences, session reminder automations, and billing follow-up workflows as platform-native automation objects. Nutshell has its own workflow builder for automation, but no workflow definitions transfer between platforms. We export Practice workflow definitions — trigger conditions, action steps, timing rules, and recipient logic — as a structured reference document that the practice admin can use to rebuild equivalent automations in Nutshell's workflow tool. This is a manual step requiring practice admin involvement; automation rebuilding effort is not included in standard migration pricing.

  • Nutshell file attachment size limit may require pre-migration file handling

    Practice stores client documents (session PDFs, signed forms, assessment instruments) as file attachments on Person records. Nutshell enforces a 25MB per-file size limit on attachments. Practices with large session recordings, comprehensive intake PDFs, or multi-page assessment documents exceeding 25MB will encounter upload errors during migration. We flag files exceeding the Nutshell size limit before migration runs and provide two options: split the file into smaller chunks before upload, or store oversized files externally with a link note in the Nutshell People record. This pre-migration file audit adds a planning step but prevents failed migration runs.

  • Nutshell's single-pipeline model differs from multi-pipeline CRM structures

    Practice supports tracking multiple deal types (session packages, sliding-scale agreements, corporate contracts) without enforcing a single pipeline structure. Nutshell uses one pipeline per account with configurable stages — all deals route through the same stage list. If Practice tracks fundamentally different deal types with distinct stage sets, those distinctions do not map natively into Nutshell's single pipeline. We handle this by mapping all Practice deals into one Nutshell pipeline and adding a Deal_Type__c custom field to distinguish between session packages, sliding-scale records, and corporate agreements. This preserves the business logic but requires the practice admin to use the custom field filter in Nutshell's pipeline views instead of separate pipelines.

Migration approach

Six steps for a successful The Practice to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

The Practice logo

The Practice

Source

Strengths

  • Unlimited contacts and storage on all plans without per-record billing
  • Built-in scheduler with automated appointment reminders via email and SMS
  • Private client messaging integrated into the platform
  • Contract signing and management with document storage
  • Responsive customer support reported across multiple review sources

Weaknesses

  • No public REST API for bulk data export or third-party integrations
  • Email reminder sender name does not include the practitioner's business name
  • Limited reporting and analytics beyond basic client summaries
  • File storage has undocumented size limits that can trigger surprise overages
  • No migration tooling or official export path for switching platforms
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 The 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

    The Practice: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most Practice to Nutshell migrations complete within 24–72 hours for databases under 10,000 records with standard field mapping and fewer than 10 custom fields. Setups exceeding 10,000 records, or those with 15–30 custom fields requiring plan-tier consolidation analysis, extend to 5–10 days. The custom field consolidation decision — which fields migrate as custom fields versus collapsing into notes — is the longest planning step. The actual data load is typically the fastest phase once the field map is approved.

Adjacent paths

Related migrations to explore

Ready when you are

Move from The 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