CRM migration
Field-level mapping, validation, and rollback between MerusCase and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
MerusCase
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between MerusCase and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
MerusCase organizes legal firms around Cases, Parties, and Activities — each case holds parties (plaintiffs, defendants, attorneys), a timeline of activities (filings, hearings, calls, notes), custom case-type fields, and a billing ledger with UTBMS L-codes and A-codes. Nutshell is a sales CRM organized around People, Companies, Leads, and Deals with a lightweight activity feed. The migration extracts MerusCase Parties as Nutshell People (or Leads if they have no open matter), Companies map directly, Activities map to Nutshell's activity log with original timestamps and owners, and MerusCase custom fields migrate as Nutshell custom fields on the People object. Legal-case metadata (case type, case status, opposing counsel, UTBMS billing codes) has no native Nutshell equivalent — we preserve these as custom fields for reference. Workflows, automated statutes, and billing logic built in MerusCase do not transfer; those must be rebuilt in Nutshell's automation tools or handled outside the CRM. We use MerusCase's API and CSV export tools to extract data, then load into Nutshell via its JSON-RPC API or CSV import with field-level validation before commit.
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 MerusCase 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.
MerusCase
Party (Contact)
Nutshell
Person
1:1MerusCase parties (individuals attached to a case) map directly to Nutshell People. We pull name, email, phone, address, and role on the case. Parties without an active case at migration time land as Nutshell People with the original create date preserved in a custom field.
MerusCase
Party (Organization)
Nutshell
Company
1:1MerusCase organizational parties representing law firms, insurance carriers, opposing counsel, and other entities map to Nutshell Companies. We transfer company name, domain, address, and phone directly. Contacts associated with that organization link via Nutshell's Person-Company relationship model, preserving the relational structure between individuals and their affiliated organizations.
MerusCase
Case
Nutshell
Custom field group on Person
1:1MerusCase Cases have no direct Nutshell equivalent. We extract case number, case type, case status, opposing counsel name, and filing date as custom fields on the primary Person record. For matters with multiple parties, the lead party record carries case metadata and other parties reference it.
MerusCase
Case Type
Nutshell
Custom field (text or pick-list)
1:1MerusCase case types (Immigration, Personal Injury, Employment, Workers' Comp, etc.) transfer as a custom pick-list field (Case_Type__c) on the Person record. If Nutshell does not have a pick-list custom field type available on the plan, we use a text field and preserve the original value exactly.
MerusCase
Activity (Call)
Nutshell
Activity (Call)
1:1MerusCase call activities with contact name, date, and description map to Nutshell Call activities on the associated Person record. Original timestamps and assigned staff member are preserved. UTBMS A-codes and task codes are stored as custom fields on the activity.
MerusCase
Activity (Email)
Nutshell
Activity (Email)
1:1MerusCase email activities map to Nutshell Email activities on the associated Person record. The subject line, sent date, and full body text transfer completely. Email attachments are noted as file references in the activity record, and the actual attachment files are re-uploaded to Nutshell's file attachment feature on the corresponding Person record for full access.
MerusCase
Activity (Meeting / Hearing)
Nutshell
Activity (Meeting)
1:1MerusCase meeting and hearing entries with start/end time, location, and description map to Nutshell Meeting activities. For immigration and litigation cases, hearing dates are preserved as meeting entries with the original calendar date. Statute reminder activities convert to standard meetings.
MerusCase
Activity (Note / Filing)
Nutshell
Activity (Note)
1:1MerusCase note entries including internal memos, filing confirmations, and case-specific annotations map to Nutshell Note activities on the Person record. Filing-specific notes include the original filing date and court name as structured metadata within the note body text or as separate custom fields for accurate legal record-keeping.
MerusCase
Custom Fields (up to 50)
Nutshell
Custom Fields
1:1MerusCase custom fields per firm (Date, Currency, Text, Numeric, Yes/No) map to Nutshell custom fields on the Person object. Text fields up to 250 characters map to Nutshell Text. Currency maps to Number with a currency note. Date fields map directly. Yes/No maps to Checkbox. Nutshell may require a plan upgrade for custom field access.
MerusCase
Document Archive
Nutshell
File Attachments on Person
1:1MerusCase Document Archives (ZIP per case) are downloaded and re-uploaded as file attachments on the corresponding Nutshell Person record. Inline images in documents are extracted and re-hosted as standalone attachments. Large document sets may require batch upload over multiple sessions.
MerusCase
Case Ledger (Time Entries)
Nutshell
No Equivalent — Custom Field Reference
1:1MerusCase billing ledger entries with UTBMS L-codes, A-codes, bill-to contacts, and time/expense amounts have no Nutshell equivalent. We export the ledger as a CSV and preserve it as a linked file on the Person record. Firms needing billing reconciliation should export from MerusCase before account closure.
MerusCase
Workflow / Automation
Nutshell
No Equivalent
1:1MerusCase Workflows (triggered by activity tags or description text to auto-create tasks and calendar entries) do not transfer. Nutshell has personal email sequences but no case-triggered automation. We export workflow definitions as a text reference document for the firm to review during Nutshell setup.
| MerusCase | Nutshell | Compatibility | |
|---|---|---|---|
| Party (Contact) | Person1:1 | Fully supported | |
| Party (Organization) | Company1:1 | Fully supported | |
| Case | Custom field group on Person1:1 | Fully supported | |
| Case Type | Custom field (text or pick-list)1:1 | Fully supported | |
| Activity (Call) | Activity (Call)1:1 | Fully supported | |
| Activity (Email) | Activity (Email)1:1 | Fully supported | |
| Activity (Meeting / Hearing) | Activity (Meeting)1:1 | Fully supported | |
| Activity (Note / Filing) | Activity (Note)1:1 | Fully supported | |
| Custom Fields (up to 50) | Custom Fields1:1 | Fully supported | |
| Document Archive | File Attachments on Person1:1 | Fully supported | |
| Case Ledger (Time Entries) | No Equivalent — Custom Field Reference1:1 | Fully supported | |
| Workflow / Automation | No Equivalent1: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.
MerusCase gotchas
Annual subscription and data access tied together
Outbound migration is not supported by MerusCase
Document Archive exports are per-case, not bulk
Built-in CSV import tools are not easy to use
Custom Fields apply to Cases only and have a 50-field cap
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 MerusCase data and map case-party relationships
We connect to MerusCase using scoped API read access and export the full party list, company list, case list, activity log, and custom field definitions. We identify the primary party per case (the retained client or lead plaintiff), map the role assignments for all other parties, and flag any parties without an email address for manual review. The audit output includes a record count by object, a sample of custom field values, and the list of case types in use so we can configure Nutshell custom fields before data lands.
Create Nutshell custom fields for case metadata and UTBMS
Before any records load, we create the custom fields in Nutshell that will hold MerusCase data with no native equivalent: Case_Number__c, Case_Type__c, Case_Status__c, Filing_Date__c, Opposing_Counsel__c, Party_Role__c, UTBMS_L_Code__c, UTBMS_A_Code__c, and any firm-specific custom fields from MerusCase's 50-field limit. We configure field types to match MerusCase's original data types (date for dates, number for currency, checkbox for Yes/No). If Nutshell's plan restricts custom field access, we flag that during scoping so the firm can upgrade before migration day.
Export and stage MerusCase data: parties, companies, activities, documents
We pull party records and organizational parties from MerusCase via API, extract activity histories per case including UTBMS codes and timestamps, and download Document Archives per case. We stage everything in a migration workspace and run a field-level validation pass — checking for duplicate emails, missing required fields, and party records with no case assignment. Any records that fail validation are flagged in a discrepancy report for the firm to resolve before the load begins.
Load Companies and People into Nutshell with case metadata
We load organizational parties into Nutshell as Companies first, then load individual parties as People linked to their Company. For each Person, we assign the case metadata from the corresponding MerusCase Case record (case number, case type, case status, filing date, opposing counsel) to the custom fields we created in Step 2. For parties associated with multiple cases, we attach all case metadata as separate custom field entries and note the multi-case association in the Person record. Staff assignments on activities resolve by email match to existing Nutshell users; unmatched owners are flagged for the firm to assign before activities load.
Load activities and re-upload documents
Activities (calls, emails, meetings, notes) load into Nutshell linked to the correct Person record, with original timestamps and assigned staff preserved. UTBMS L-codes and A-codes populate the custom activity fields created for this purpose. Document Archives are extracted and files are re-uploaded as attachments on the corresponding Person record. Large document sets batch-upload in sessions to stay within Nutshell's file handling limits. The case ledger CSV is attached as a reference file on the primary person record for billing lookup.
Run delta pickup and validate final record counts
After the initial load, we run a delta pickup window (24–48 hours) to capture any parties, activities, or case updates made in MerusCase during the cutover. We compare source and destination record counts for People, Companies, and Activities, and surface any gaps. An audit log records every operation. If reconciliation shows missing records, we re-run the affected object load. Once counts match and field sampling validates data integrity, the firm goes live in Nutshell. We provide a rollback procedure tied to the pre-migration backup snapshot.
Platform deep dives
MerusCase
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 MerusCase 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
MerusCase: Not publicly documented.
Data volume sensitivity
MerusCase 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 MerusCase to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your MerusCase 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 MerusCase
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.