CRM migration
Field-level mapping, validation, and rollback between MyCase and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
MyCase
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between MyCase and Nutshell.
Complexity
BStandard
Timeline
48–96 hours
Overview
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.
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 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)
Nutshell
Person
1:1MyCase 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
Nutshell
Company
1:1MyCase 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)
Nutshell
Deal
1:1MyCase 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
Nutshell
Task
1:1MyCase 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
Nutshell
Activity Note
1:1MyCase 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
Nutshell
Custom Field on Deal + Activity Note
1:1MyCase 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
Nutshell
File / Attachment
1:1MyCase 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)
Nutshell
Custom Field (Deal)
1:1MyCase 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)
Nutshell
Custom Field (Person / Company)
1:1MyCase 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)
Nutshell
Activity
1:1MyCase 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.
| MyCase | Nutshell | Compatibility | |
|---|---|---|---|
| Client (Contact) | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Matter (Case) | Deal1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Time Entry | Activity Note1:1 | Fully supported | |
| Invoice / Flat Fee Record | Custom Field on Deal + Activity Note1:1 | Fully supported | |
| Document / File Attachment | File / Attachment1:1 | Fully supported | |
| Custom Field (Matter) | Custom Field (Deal)1:1 | Fully supported | |
| Custom Field (Contact / Company) | Custom Field (Person / Company)1:1 | Fully supported | |
| Activity (Email, Note, Call Log) | Activity1: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.
MyCase gotchas
QuickBooks sync is strictly one-directional
Advanced API access is tier-gated
Document migration requires offline file transfer
Bulk rate updates on historical time entries are not supported
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 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.
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.
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.
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.
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
MyCase
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 MyCase 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
MyCase: 25 requests per second per client.
Data volume sensitivity
MyCase 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 MyCase to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your MyCase 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 MyCase
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.