CRM migration

Migrate from Case UI to Nutshell

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

Case UI logo

Case UI

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between Case UI and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Case UI logo

Case UI

What's pushing teams away

  • Small law firms report outgrowing the platform when they need advanced integrations, custom workflows, or multi-office support that Case UI does not provide.
  • Lack of public API documentation makes Case UI difficult to connect with third-party tools, forcing firms to manually export and re-enter data when workflow needs change.
  • Users with complex practice areas report that the platform lacks depth in features like advanced reporting, conflict checking, or specialized litigation tools.
  • On-Premise customers who lack dedicated IT staff struggle with self-managed security updates and backups, leading some to move to fully managed alternatives.

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 Case UI objects map to Nutshell

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

maps to

Nutshell

Nutshell Person + Company

many:1
Fully supported

Individual 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

maps to

Nutshell

Nutshell Deal + Custom Fields

1:1
Fully supported

Case 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

maps to

Nutshell

Nutshell User

1:1
Fully supported

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

maps to

Nutshell

Nutshell Activity

1:1
Fully supported

Case 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

maps to

Nutshell

Nutshell File

1:1
Fully supported

Case 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

maps to

Nutshell

Nutshell Activity (Meeting)

1:1
Fully supported

Case 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

maps to

Nutshell

Nutshell Task

1:1
Fully supported

Open 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

maps to

Nutshell

Nutshell Custom Fields on Deal

1:1
Fully supported

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

maps to

Nutshell

Nutshell Custom Fields on Deal

1:1
Fully supported

Case 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

maps to

Nutshell

Nutshell Note

1:1
Fully supported

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

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.

Case UI logo

Case UI gotchas

High

No public API documentation found

Medium

On-Premise perpetual license has upgrade isolation risk

Low

No verified public reviews or G2/Capterra feedback

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

  • Case UI Matters lack a native Nutshell Deal equivalent requiring custom field preservation

    Case UI's core object is the Matter — a legal case file containing nested documents, billing, and attorney assignments. Nutshell's Deals are sales-opportunity objects keyed to pipeline stages. We map each Matter to a Nutshell Deal and preserve case-specific metadata (case number, court jurisdiction, opposing counsel, statute of limitations) as custom fields on the Deal. Without this mapping, your Matter history collapses into generic Deals with no legal context. Plan for custom field creation in Nutshell before migration day — Nutshell's field naming follows their internal conventions and your admin needs to configure them first.

  • Case UI billing ledger has no Nutshell equivalent — financial history requires separate handling

    Case UI includes trust accounting, invoice generation, and time tracking as core features. Nutshell has no native billing or accounting module — invoice amounts, payment status, and trust balances must be stored as custom fields on the migrated Deal, and the detailed billing ledger should be exported separately for import into QuickBooks, LawPay, or your accounting software. If your practice relies heavily on Case UI's billing reporting, budget time to rebuild those reports in Nutshell or a connected accounting tool post-migration.

  • Document re-hosting triggers Nutshell's 25MB per-file size limit

    Case UI documents (pleadings, contracts, correspondence) are first-class objects in the legal workflow. Nutshell Files attaches documents to Person or Deal records but enforces a 25MB per-file limit. Large case files, video depositions, or document bundles exceeding this threshold must be split before migration or stored in a linked document management system (Google Drive, SharePoint) with the link stored in Nutshell. We flag files exceeding this limit during the sample migration so your team can decide on splitting or linking strategy before the full run.

  • Nutshell's activity timeline flattens multi-party contact roles that Case UI models explicitly

    Case UI tracks attorney roles per Matter (lead counsel, associate, of counsel, opposing counsel) and associates multiple contacts with a single Matter. Nutshell links People to Deals through the standard activity model but has no native multi-role contact assignment for legal matters. We store attorney role types as a custom pick-list field on the Deal and link each attorney as a Person — but your team will see multiple People attached to one Deal rather than a structured role hierarchy. If role-based reporting is critical, consider building a custom junction object in Nutshell post-migration.

  • Conflict-check records and client intake workflows cannot migrate and must be rebuilt

    Case UI's conflict-check logic, client intake automation, and document generation workflows are platform-native automation rules that do not export. Nutshell's automation tools (Triggers, Workflows, Email Sequences) offer equivalent building blocks but require manual rebuild. We export your Case UI workflow definitions as a text reference document during discovery so your Nutshell admin has a rebuild checklist. Budget 2–4 weeks for automation rebuild depending on workflow complexity — particularly for practices with multi-step intake forms, automated conflict searches, or templated document generation tied to Matter creation.

Migration approach

Six steps for a successful Case UI to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Case UI logo

Case UI

Source

Strengths

  • Clear per-user pricing with no surprise fees or mandatory add-ons on the Cloud plan.
  • On-Premise perpetual option eliminates per-user billing for firms with many attorneys and staff.
  • Free trial lets firms validate fit before committing to a paid subscription.
  • Daily backups and segregated databases reduce data loss risk for solo practitioners.
  • Straightforward interface purpose-built for small law firm workflows.

Weaknesses

  • No publicly documented API limits third-party integrations and automated migration tooling.
  • Limited public documentation and no verified reviews make independent evaluation difficult.
  • Smaller feature set compared to enterprise legal platforms may not support complex or multi-practice operations.
  • On-Premise version requires firm IT staff to manage upgrades, security, and backups independently.
  • No transparent rate limits or SLA terms published on the website for Cloud customers.
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. 3 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 Case UI and Nutshell.

  • Object compatibility

    B

    3 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

    Case UI: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Case UI 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 Case UI to Nutshell data migrations

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

Can't find your answer?

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 consultation

Most Case UI to Nutshell migrations complete in 48–72 hours for under 25,000 records (Clients, Matters, Activities, Documents). Larger practices with 250,000+ records or extensive document archives extend to 5–8 days. The longest step is creating Nutshell custom fields for case metadata and configuring the pipeline stages that map to Case UI matter status. Nutshell's API rate limits on file uploads can extend document migration time for practices with large document volumes.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Case UI.
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