CRM migration
Field-level mapping, validation, and rollback between Clio and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Clio
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Clio and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Clio is a legal practice management platform built around matters, clients, billing, and document management. Nutshell is a sales CRM organized around people, companies, leads, and deals. The fundamental translation challenge is that Clio's matter-centric model — where attorneys bill time against cases — has no direct equivalent in Nutshell's pipeline-centric sales model. We map Clio clients to Nutshell people (with company associations), Clio matters to Nutshell deals, and Clio time entries to custom fields or activity logs. The critical disclosure is that Clio's accounting history (trust balances, operating account transactions, invoices, billed time entries) cannot migrate to Nutshell because Nutshell has no accounting module. We preserve a snapshot of outstanding balances as a reference custom field. Clio's document management maps to Nutshell file attachments; original timestamps and creator attribution are preserved. User and staff accounts in Clio resolve to Nutshell users by email match, with unresolvable staff members flagged for manual assignment. The migration runs against Clio's REST API (50 req/min peak limit) with exponential backoff, then lands data into Nutshell via their JSON-RPC API. We run a sample migration first, generate a field-level diff, and close with a 24–48 hour delta pickup window to capture in-flight changes during cutover.
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 Clio 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.
Clio
Client
Nutshell
Person
1:1Clio clients map directly to Nutshell people records. The client's display name, primary email address, phone number, and address fields translate directly to Nutshell's corresponding person fields (name, email, phones, address). Any Clio client record lacking an email address is flagged by the migration engine and queued for manual enrichment before the import runs, ensuring no incomplete contact records enter Nutshell without team review.
Clio
Client
Nutshell
Company
1:1When a Clio client represents a business entity (e.g., matters linked to a corporate client rather than an individual), we map it to a Nutshell company record. The client name becomes the company name; we create a corresponding person record for the primary contact within that company.
Clio
Matter
Nutshell
Deal
1:1Clio matters map to Nutshell deals. Matter name becomes deal name; matter description maps to deal description. Matter status (Open, Closed, Pending) is mapped to Nutshell pipeline stage values based on a value-mapping table agreed upon before migration. Closed matters map to Won or Lost stage based on outcome.
Clio
Matter Status
Nutshell
Pipeline Stage
1:1Clio matter status values (Open, On Hold, Closed, Archived) map to Nutshell pipeline stages (Lead, Qualified, Proposal, Won, Lost) per a value-mapping matrix. We preserve the original status-transition timestamps as custom datetime fields on the Nutshell deal for reporting continuity.
Clio
Time Entry
Nutshell
Activity / Custom Field
1:1Clio time entries (billable and non-billable) do not have a native Nutshell equivalent. Billable time entries migrate as custom fields on the related deal (e.g., Total_Billable_Hours__c). Individual time entries are preserved as activity notes with original hours, date, and attorney attribution for historical reference.
Clio
Document
Nutshell
File Attachment
1:1Clio documents attached to matters migrate to Nutshell deal file attachments. We download each file from Clio, re-upload to Nutshell's storage, and link it to the corresponding deal. Original upload timestamps and creator attribution are preserved in the file metadata.
Clio
Billing / Invoice
Nutshell
Custom Field (Reference Only)
1:1Clio invoices, trust balances, accounts receivable, and operating account transactions have no Nutshell equivalent. We export Clio's accounts receivable balance snapshot and outstanding invoice total as custom fields on the client/person record. Full financial history must remain in Clio or be exported to an accounting tool.
Clio
Staff / User
Nutshell
User
1:1Clio staff members resolve to Nutshell users by email address. Staff members without a corresponding Nutshell user are flagged before migration; their matters and time entries can be reassigned to a fallback Nutshell user or remain unattributed pending team invitation.
Clio
Task
Nutshell
Task
1:1Clio tasks assigned to matters map directly to Nutshell tasks linked to their corresponding deal record. Core task attributes including due dates, descriptions, and owner assignment translate to Nutshell's task fields. Completed task status is preserved in the migration; open or in-progress tasks migrate with a pending status in Nutshell. Task priority levels and recurrence patterns are noted for manual recreation since Nutshell handles these fields differently than Clio's task model.
Clio
Custom Field (Matter)
Nutshell
Custom Field (Deal)
1:1Clio custom fields on matters (e.g., case type, court jurisdiction, opposing counsel) require pre-creation of equivalent Nutshell custom fields on the deal object before migration. We deliver a custom field creation guide as part of the migration plan so fields exist before the import runs.
Clio
Custom Field (Client)
Nutshell
Custom Field (Person)
1:1Clio custom fields on clients (e.g., referral source, client type, intake date) migrate to Nutshell custom fields on the person record. Field type conversion is applied: Clio text fields become Nutshell text fields, pick-lists become Nutshell choice fields, date fields become Nutshell date fields.
Clio
Matter-Client Relationship
Nutshell
Deal-Person Association
1:1Clio's matter-to-client links translate to Nutshell deal-person associations. When a matter has a primary client, that person is linked to the deal as the primary contact. Secondary clients on a matter are added as additional contacts on the Nutshell deal.
| Clio | Nutshell | Compatibility | |
|---|---|---|---|
| Client | Person1:1 | Fully supported | |
| Client | Company1:1 | Fully supported | |
| Matter | Deal1:1 | Fully supported | |
| Matter Status | Pipeline Stage1:1 | Fully supported | |
| Time Entry | Activity / Custom Field1:1 | Fully supported | |
| Document | File Attachment1:1 | Fully supported | |
| Billing / Invoice | Custom Field (Reference Only)1:1 | Fully supported | |
| Staff / User | User1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Custom Field (Matter) | Custom Field (Deal)1:1 | Fully supported | |
| Custom Field (Client) | Custom Field (Person)1:1 | Fully supported | |
| Matter-Client Relationship | Deal-Person Association1: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.
Clio gotchas
API rate limit of 50 req/min per OAuth application
Trust accounting data requires separate ledger treatment
Rate hierarchy complexity causes billing mismatches
Client portal does not transfer between platforms
Flat-rate and contingency matter billing requires explicit mapping
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 Clio data and design the Nutshell schema
We run a discovery scan of the Clio instance — counting clients, matters, time entries, documents, tasks, and custom fields. We then design the Nutshell custom field structure (per person, per deal) based on the Clio custom field inventory. We deliver a schema setup guide so your Nutshell admin creates the required fields before data migration begins. We also agree on the matter-status-to-pipeline-stage value-mapping matrix during this phase.
Run sample migration with field-level diff
We migrate a representative slice — typically 100–500 records across clients, matters, time entries, tasks, and a sample of documents. The field-level diff report shows exactly what landed in each Nutshell field, including custom field values, stage mappings, and document links. You review the sample in Nutshell and confirm mapping accuracy before the full run commits. Any field mapping corrections are applied before proceeding.
Execute full migration with rate-limited export from Clio
The full migration runs against Clio's API with throttling (50 req/min peak, backoff on 429). We sequence the load: clients and companies first, then matters linked to their primary clients, then time entries and tasks, then documents. Foreign-key relationships (matter-to-client, document-to-matter) resolve as each batch lands. Clio accounting data is exported as a reference snapshot CSV rather than loaded into Nutshell.
Delta pickup and audit log delivery
After the full migration completes, we open a 24–48 hour delta pickup window. Any Clio records created or modified during the migration window are captured and synced to Nutshell. We deliver a full audit log listing every record migrated, its source Clio ID, its destination Nutshell ID, and the migration timestamp. One-click rollback is available if reconciliation identifies missing or mis-mapped records.
Platform deep dives
Clio
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 Clio 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
Clio: 50 requests per minute per OAuth application, shared across all users of the application.
Data volume sensitivity
Clio 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 Clio to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Clio 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 Clio
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.