CRM migration

Migrate from MyCase to Nutshell

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

MyCase logo

MyCase

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between MyCase and Nutshell.

Complexity

BStandard

Timeline

48–96 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

MyCase organizes legal practices around Clients (contacts), their associated Companies, and Matters (cases) with built-in time tracking, billing, document management, and a QuickBooks sync. Nutshell is a general SMB sales CRM built around People, Companies, Leads, and Deals, with integrated email marketing, pipeline views (List, Map, Chart, Board), and a JSON-RPC API for integrations. These platforms serve different markets and their data models reflect that: MyCase's Matter-centric structure has no direct equivalent in Nutshell's Deal model, and MyCase's billing and time-entry records have to become custom fields or activity notes in Nutshell since Nutshell has no native legal billing engine. We migrate all standard MyCase objects — contacts, companies, cases, tasks, and activities — via MyCase's OAuth API using 25 requests per second rate-limited batching, into Nutshell's JSON-RPC API with user impersonation for owner resolution. Custom fields transfer as Nutshell custom fields; MyCase's QuickBooks sync does not have a Nutshell equivalent and must be rebuilt. A sample migration with field-level diff runs first; a 24–48 hour delta-pickup window captures in-flight changes at 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

MyCase logo

MyCase

What's pushing teams away

  • QuickBooks integration syncs one direction only—deleting a transaction in MyCase does not remove it in QuickBooks, and the sync can get stuck, forcing manual reconciliation that solo practitioners find disruptive.
  • Users report missing billing features that mid-size firms require: inability to bulk-update rates on past time entries, limited flat-fee case management, and manual invoice adjustments across multiple sections.
  • UI changes between releases (especially around notifications and client message navigation) create friction for staff trained on earlier layouts, per Capterra and G2 reviews.
  • Advanced features including the open API are gated behind the $109/user/month Advanced tier, so growing firms hit feature ceilings on lower plans and face a pricing cliff.
  • Firms outgrowing the platform report that Clio's integration marketplace and enterprise features better support scaling case volume, which drives switchers toward larger legal CRMs.

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

Each row shows how a MyCase 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.

MyCase

Client (Contact)

maps to

Nutshell

Person

1:1
Fully supported

MyCase Clients map to Nutshell People directly — first name, last name, email, phone, address, title, and social handles transfer as-is. MyCase's client portal access flag and billing status fields have no Nutshell equivalent; we preserve them as custom Person fields for reference. Any MyCase contact without an email is flagged because Nutshell People require an email for full CRM functionality.

MyCase

Company

maps to

Nutshell

Company

1:1
Fully supported

MyCase Companies map to Nutshell Companies directly — name, domain, industry, employee count, and revenue transfer as-is. MyCase supports multiple contacts per company; Nutshell Person records carry a single primary CompanyId. We select the most recently updated MyCase contact as the primary and surface the others as secondary company associations in a custom field for manual review.

MyCase

Matter (Case)

maps to

Nutshell

Deal

1:1
Fully supported

MyCase Matters map to Nutshell Deals using the Matter name as Deal name, estimated value or fee amount as Deal amount, and Matter status (Open, Pending, Closed) mapped to Nutshell pipeline stage values. MyCase practice-area, court, opposing counsel, and hearing-date fields have no Nutshell Deal equivalent — these become Nutshell custom fields on the Deal record. The Matter number is stored as a custom field for reference and reconciliation.

MyCase

Task

maps to

Nutshell

Task

1:1
Fully supported

MyCase Tasks map to Nutshell Tasks directly — title, due date, status, priority, and assigned user transfer. Nutshell Tasks do not have a native case/deal link field; we store the source Matter ID as a custom field on each Nutshell Task so the association can be manually re-established in Nutshell's Activity view if needed.

MyCase

Time Entry

maps to

Nutshell

Activity Note

1:1
Fully supported

MyCase time entries (hours, description, billing rate, attorney assigned) have no native Nutshell equivalent — Nutshell has no time-tracking engine. We convert each MyCase time entry into a structured Activity note on the linked Deal, preserving hours logged, description, and rate. The firm's team reviews these notes to determine whether to bill them manually or export to their accounting tool.

MyCase

Invoice / Flat Fee Record

maps to

Nutshell

Custom Field on Deal + Activity Note

1:1
Fully supported

MyCase billing records — invoices, flat fee tracking, trust account entries, and IOLTA status — do not exist as a data type in Nutshell. We migrate invoice total, balance due, and payment status as custom fields on the associated Deal, and store a summary of the billing record as an Activity note. The firm's accounting team rebuilds invoices in their preferred billing tool post-migration.

MyCase

Document / File Attachment

maps to

Nutshell

File / Attachment

1:1
Fully supported

MyCase Drive documents and file attachments are downloaded and re-uploaded to Nutshell's file storage linked to the corresponding Person, Company, or Deal record. MyCase's auto-generated case folder structure (top-level folders created when a Matter is opened) does not map to Nutshell; documents are attached individually to the migrated Deal record.

MyCase

Custom Field (Matter)

maps to

Nutshell

Custom Field (Deal)

1:1
Fully supported

MyCase custom fields on Matters — practice area, court location, opposing counsel, filing deadline, judge name — become Nutshell custom fields on the Deal record. Nutshell custom fields support text, number, date, and pick-list types; MyCase field types map to the nearest Nutshell equivalent. Nutshell's field-level security and visibility settings must be configured manually after migration.

MyCase

Custom Field (Contact / Company)

maps to

Nutshell

Custom Field (Person / Company)

1:1
Fully supported

MyCase custom fields on Clients and Companies migrate as Nutshell custom fields on Person and Company records. Both platforms support custom fields on these objects, so the mapping is direct in structure. Any MyCase pick-list custom field values are preserved as Nutshell pick-list options; the firm adds missing values manually in Nutshell's settings.

MyCase

Activity (Email, Note, Call Log)

maps to

Nutshell

Activity

1:1
Fully supported

MyCase email logs, call notes, and general notes associated with a Client or Matter migrate as Nutshell Activity records attached to the corresponding Person or Deal. Original timestamps and the creating user are preserved. Nutshell does not support email threading or full email body display in the same way MyCase does — activity notes show the logged description but not the full email MIME content.

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.

MyCase logo

MyCase gotchas

High

QuickBooks sync is strictly one-directional

High

Advanced API access is tier-gated

Medium

Document migration requires offline file transfer

Medium

Bulk rate updates on historical time entries are not supported

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

  • Billing and time-entry records have no native Nutshell home

    MyCase bakes legal billing into its core data model — flat fee tracking, time entries, trust account balances, IOLTA status, and invoice totals are all first-class MyCase records. Nutshell is a sales CRM with no billing engine. FlitStack converts MyCase billing data into structured activity notes and custom Deal fields, but the firm's accounting team must rebuild invoice generation, trust accounting, and billing workflows in their preferred tool post-migration. MyCase's bidirectional QuickBooks sync does not have a Nutshell equivalent and requires a fresh QuickBooks connection and mapping configuration.

  • MyCase's 25 req/sec API rate limit extends export duration for large databases

    MyCase enforces 25 requests per second per OAuth client. For firms with 20,000+ matters and hundreds of thousands of time entries, this rate limit means a single full export can take multiple hours. FlitStack batches MyCase API calls with backoff logic to stay within the limit without triggering 429 errors. Nutshell's API is not the bottleneck — its rate limits apply to find operations (getLeads, findPeople with stubResponses=false) which we do not invoke during import, only during optional post-migration reconciliation.

  • N:N client-to-company relationships collapse to a single primary company

    MyCase allows a Client record to be associated with multiple Companies simultaneously — a common pattern for attorneys who represent the same client across multiple business entities. Nutshell Person records support a single primary CompanyId. FlitStack designates the most recently modified MyCase company association as the primary Nutshell company link and stores all secondary company names as a comma-separated custom field on the Person record for manual disambiguation. After migration, the firm should review these secondary associations and create additional Person records or update company links in Nutshell's UI to ensure each business entity relationship is properly captured in the CRM.

  • Matter-based task associations require post-migration manual linking

    MyCase tasks are scoped to a specific Matter, giving them implicit legal context. Nutshell Tasks exist as standalone records and are linked to Deals (and Persons) through the Nutshell UI, not through a native matter_id foreign key. FlitStack stores the source MyCase matter ID as a custom Task field during migration, but the firm's team must manually associate each task to its corresponding Nutshell Deal using Nutshell's Activity linking feature after migration.

Migration approach

Six steps for a successful MyCase to Nutshell data migration

  1. Audit MyCase data volume and custom field inventory

    FlitStack runs a pre-migration discovery scan against your MyCase instance via the OAuth API. We count contacts, companies, matters, tasks, activities, and time-entry records; inventory all custom fields across each object type; and identify any billing records (invoices, flat-fee setups, trust entries) that require transformation. We also flag MyCase-to-Nutshell user email mismatches so your team can create or invite Nutshell users before the migration window opens. The audit report is shared for your review before any data moves.

  2. Configure Nutshell target schema

    Based on the audit, FlitStack delivers a Nutshell schema setup plan listing the custom fields to create (Deal-level fields for practice area, court, matter number, flat fee amount, and original open/close dates; Person-level fields for client portal flag and billing status). Your Nutshell admin creates these fields in the Settings panel before the migration runs. We also identify the best-fit Nutshell pipeline stage values for each MyCase matter status so the stage mapping is ready before records land.

  3. Migrate Companies first, then People, then Deals

    Migration follows a strict foreign-key sequence. Companies (Nutshell Account equivalent) are migrated first so Person records can link to them via companyId. People are migrated next with primary company assignment resolved by name matching. Deals are migrated third with owner resolution by email match against Nutshell users. Tasks and activity notes are migrated last, attached to the resolved Person or Deal records. This sequence prevents orphaned records and broken lookups.

  4. Run a sample migration with field-level diff

    A representative slice — typically 100–500 records spanning contacts, companies, matters, tasks, and activities — migrates first. FlitStack generates a field-level diff showing every mapped field, its source value in MyCase, and its destination value in Nutshell. You verify that practice-area custom fields landed correctly, matter status mappings match your pipeline expectations, and owner resolution produced expected assignments. Changes to the mapping plan are applied before the full run.

  5. Execute full migration with delta-pickup and rollback

    The full migration runs against Nutshell using the validated field mapping. A delta-pickup window of 24–48 hours captures any records created or modified in MyCase during the cutover period so Nutshell reflects your final MyCase state at go-live. FlitStack maintains an audit log of every record created, updated, or skipped. If reconciliation fails — record counts do not match, duplicate detection flags are triggered — one-click rollback reverts all Nutshell changes so the migration can be rerun with corrected mapping without data loss.

Platform deep dives

Context on both ends of the pair

MyCase logo

MyCase

Source

Strengths

  • All-in-one practice management combines case files, client comms, billing, and docs in a single platform.
  • Client portal with secure document sharing reduces reliance on third-party file-sharing tools.
  • Built-in texting and e-signature are included at all tiers, avoiding per-transaction fees.
  • Workflow automation auto-generates tasks and calendared deadlines on new case creation.
  • AffiniPay parentage ties payments tightly to practice management through LawPay integration.

Weaknesses

  • Open API and advanced document management require the Advanced tier at $109/user/month.
  • One-way QuickBooks sync means billing deletions in MyCase must be manually voided in QuickBooks.
  • Cannot bulk-update rates on past time entries—each record requires individual editing.
  • UI changes between releases have caused navigation friction, especially around notifications.
  • Document automation templates are tied to the original creator's machine and cannot be exported.
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. 2 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 MyCase and Nutshell.

  • Object compatibility

    B

    2 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

    MyCase: 25 requests per second per client.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your MyCase to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most MyCase-to-Nutshell migrations complete within 48–96 hours of clock time for databases under 30,000 records. Larger setups with 100,000+ records, extensive time-entry histories, or complex custom field configurations extend to 7–12 days. The longest planning step is mapping MyCase matter statuses and custom billing fields to Nutshell Deal fields — this happens before any data moves during the schema setup phase.

Adjacent paths

Related migrations to explore

Ready when you are

Move from MyCase.
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