CRM migration
Field-level mapping, validation, and rollback between Case UI and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Case UI
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between Case UI and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Case UI is a practice management system built for solo practitioners and law firms — it models legal work as Matters tied to Clients, with billing, documents, and calendar events nested inside each matter. Nutshell is a B2B sales CRM that models business relationships as People linked to Companies, with Deals tracked through customizable Pipelines and Stages. These data models share structural DNA (contacts, companies, activities, attachments) but diverge sharply on the legal-specific objects: Case UI Matters, Client Billing, and Attorney Assignments have no native equivalent in Nutshell. FlitStack AI maps Case UI Clients to Nutshell People (with Company links where applicable), Case UI Matters to a combination of Deals and custom fields, and Case UI Activities to Nutshell's native Activity model. The harder translation work is preserving matter metadata — case number, case type, opposing counsel, court jurisdiction, statute of limitations — as Nutshell custom fields so the historical context survives the migration. We also handle Case UI document attachments by re-hosting them in Nutshell Files and linking them to the correct People or Deal records. What does NOT migrate: Case UI's billing ledger, trust accounting, conflict-check records, and legal-specific workflows (case intake automation, document generation rules). Those have to be rebuilt in Nutshell's automation tools or handled separately. Our migration runs against Case UI's export API and bulk-loads into Nutshell via their REST API, with a 24–48 hour delta window capturing any records created or modified during the 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 Case UI 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.
Case UI
Case UI Client
Nutshell
Nutshell Person + Company
many:1Individual clients map to Nutshell People; organizational clients (corporate legal departments, law firm partnerships) map to Nutshell Companies with a linked Person record for the primary contact. Attorney contacts from opposing firms or internal counsel become separate People records. We preserve the original Case UI client ID in Nutshell's Source_System_ID__c custom field for traceability.
Case UI
Case UI Matter
Nutshell
Nutshell Deal + Custom Fields
1:1Case UI Matters do not have a native Nutshell equivalent since Nutshell's Deals are sales-opportunity objects rather than legal case files. We map each Matter to a Nutshell Deal and attach Case UI's case number, case type, court jurisdiction, opposing counsel, and statute of limitations as custom fields on the Deal. The Deal name defaults to the Matter name, and the responsible attorney becomes the Deal owner.
Case UI
Case UI Attorney
Nutshell
Nutshell User
1:1Case UI attorney records (name, email, bar number, firm affiliation) resolve by email match to existing Nutshell users. If no match exists, we flag the attorney for your admin to either invite to Nutshell or assign to a fallback user. Case UI attorney roles per matter (lead counsel, associate, of counsel) are stored as custom fields on the associated Matter/Deal.
Case UI
Case UI Activity (Calls, Emails, Meetings)
Nutshell
Nutshell Activity
1:1Case UI logged calls, emails, and meetings map to Nutshell Activities attached to the corresponding Person or Deal. Original timestamps, duration, and subject line are preserved. Email bodies and call notes migrate as Activity notes. Nutshell's activity timeline on each record shows the full client engagement history after migration.
Case UI
Case UI Document
Nutshell
Nutshell File
1:1Case UI documents (pleadings, contracts, correspondence) re-upload to Nutshell Files and attach to the appropriate Person or Deal record. We preserve the original file name, upload date, and file size. Nutshell's 25MB per-file limit applies; files exceeding this are flagged for splitting before migration. E-filing metadata (filing date, court, docket number) is stored as custom fields on the attached Deal.
Case UI
Case UI Calendar Event
Nutshell
Nutshell Activity (Meeting)
1:1Case UI calendar events (depositions, court dates, client meetings) migrate as Nutshell Meetings with start/end time, location, and linked Person or Deal. Reminder settings and recurrence patterns are noted as activity description text since Nutshell's native recurrence model differs from Case UI's.
Case UI
Case UI Task
Nutshell
Nutshell Task
1:1Open and completed Case UI tasks migrate to Nutshell Tasks with the original due date, assigned user (resolved by email match), priority flag, and linked Person or Deal. Completed tasks preserve their completion timestamp. Task description and notes transfer as-is.
Case UI
Case UI Billing / Invoice
Nutshell
Nutshell Custom Fields on Deal
1:1Case UI's billing ledger, trust account balances, and invoice line items have no native Nutshell equivalent. We preserve invoice amounts, status (paid/unpaid/overdue), and payment dates as custom fields on the corresponding Deal. The detailed billing ledger must be exported separately and managed in accounting software post-migration.
Case UI
Case UI Custom Fields (Matter-level)
Nutshell
Nutshell Custom Fields on Deal
1:1Case UI allows firms to define custom fields on Matters for case-specific data (e.g., case category codes, referral source, insurance carrier). We create matching Nutshell custom fields on the Deal object and migrate the values. Custom field types (text, date, pick-list) map to Nutshell's corresponding field types.
Case UI
Case UI Notes
Nutshell
Nutshell Note
1:1Case UI free-form notes attached to Matters or Clients migrate to Nutshell Notes linked to the corresponding Person or Deal. Original author (resolved by email match) and creation date are preserved. Rich-text formatting is retained where Nutshell's note format allows.
| Case UI | Nutshell | Compatibility | |
|---|---|---|---|
| Case UI Client | Nutshell Person + Companymany:1 | Fully supported | |
| Case UI Matter | Nutshell Deal + Custom Fields1:1 | Fully supported | |
| Case UI Attorney | Nutshell User1:1 | Fully supported | |
| Case UI Activity (Calls, Emails, Meetings) | Nutshell Activity1:1 | Fully supported | |
| Case UI Document | Nutshell File1:1 | Fully supported | |
| Case UI Calendar Event | Nutshell Activity (Meeting)1:1 | Fully supported | |
| Case UI Task | Nutshell Task1:1 | Fully supported | |
| Case UI Billing / Invoice | Nutshell Custom Fields on Deal1:1 | Fully supported | |
| Case UI Custom Fields (Matter-level) | Nutshell Custom Fields on Deal1:1 | Fully supported | |
| Case UI Notes | Nutshell Note1: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.
Case UI gotchas
No public API documentation found
On-Premise perpetual license has upgrade isolation risk
No verified public reviews or G2/Capterra feedback
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 Case UI data model and map to Nutshell schema
We connect to Case UI's export API and pull a full inventory of Clients, Matters, Activities, Documents, and custom fields. We cross-reference this against Nutshell's standard object model and identify gaps (billing ledger, attorney roles, case metadata). We deliver a mapping plan specifying which Nutshell custom fields to create, which existing Nutshell fields to use, and which Case UI data objects have no Nutshell equivalent and require custom field or separate-export handling.
Create Nutshell custom fields and configure Deal pipeline
Before data moves, your Nutshell admin (or our team with delegated access) creates the custom fields identified in the mapping plan: Case_Number__c, Case_Type__c, Court_Jurisdiction__c, Opposing_Counsel__c, Statute_of_Limitations__c, Client_Type__c, and billing/status fields on the Deal object. We also configure a Nutshell Deal Pipeline with stages reflecting your matter lifecycle ( Intake, Active, Pending, Closed ) so Matter status maps cleanly to pipeline stages.
Resolve users and create Companies before importing People and Deals
Nutshell requires Companies to exist before linking People (via companyName lookup), and Deals require at least one linked Person. We sequence the migration: (1) create Nutshell Companies for organizational clients, (2) migrate Case UI People with company links resolved, (3) migrate Case UI Matters as Deals with responsible attorney set as Deal owner, (4) link activities and documents to the correct Person and Deal records. Unmatched attorneys are flagged before migration so your team can invite them or assign a fallback owner.
Run sample migration with field-level diff
A representative slice migrates first — typically 100–500 records spanning individual clients, corporate clients, active matters, and document attachments. We generate a field-level diff comparing Case UI source values against Nutshell destination values so you can verify that case metadata (court jurisdiction, opposing counsel) landed in the correct custom fields, that Matter status mapped to the right pipeline stage, and that attorney assignments resolved correctly before the full run commits.
Execute full migration with delta-pickup and rollback plan
Full migration runs against Case UI's data export, bulk-loading into Nutshell via their REST API. A delta-pickup window (typically 24–48 hours) captures any Case UI records created or modified during the cutover window. Audit log captures every operation with source record ID and destination record ID. One-click rollback is available if reconciliation fails — the audit log lets us identify affected records and revert to pre-migration state without data loss.
Platform deep dives
Case UI
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Case UI and Nutshell.
Object compatibility
3 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
Case UI: Not publicly documented.
Data volume sensitivity
Case UI 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 Case UI to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Case UI 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 Case UI
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.