CRM migration

Migrate from MerusCase to Nutshell

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

MerusCase logo

MerusCase

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between MerusCase and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

MerusCase logo

MerusCase

What's pushing teams away

  • Annual subscription required — payments must be made annually in advance unless a separate Order Form is negotiated.
  • Per-case Document Archive is the primary data export path; there is no one-click full firm data dump, making migrations out manual and time-consuming.
  • Credit card payments incur a 3% transaction fee plus variable network fees deducted monthly, adding cost for high-volume billing firms.
  • Third-party migrations (moving away from MerusCase) are not supported by MerusCase's own migration team — the firm must handle or hire independently.
  • Built-in CSV import tools are documented as not easy to use, pushing firms toward paid white-glove onboarding for any data loading.

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

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)

maps to

Nutshell

Person

1:1
Fully supported

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

maps to

Nutshell

Company

1:1
Fully supported

MerusCase 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

maps to

Nutshell

Custom field group on Person

1:1
Fully supported

MerusCase 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

maps to

Nutshell

Custom field (text or pick-list)

1:1
Fully supported

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

maps to

Nutshell

Activity (Call)

1:1
Fully supported

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

maps to

Nutshell

Activity (Email)

1:1
Fully supported

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

maps to

Nutshell

Activity (Meeting)

1:1
Fully supported

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

maps to

Nutshell

Activity (Note)

1:1
Fully supported

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

maps to

Nutshell

Custom Fields

1:1
Fully supported

MerusCase 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

maps to

Nutshell

File Attachments on Person

1:1
Fully supported

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

maps to

Nutshell

No Equivalent — Custom Field Reference

1:1
Fully supported

MerusCase 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

maps to

Nutshell

No Equivalent

1:1
Fully supported

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

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.

MerusCase logo

MerusCase gotchas

High

Annual subscription and data access tied together

High

Outbound migration is not supported by MerusCase

High

Document Archive exports are per-case, not bulk

Medium

Built-in CSV import tools are not easy to use

Medium

Custom Fields apply to Cases only and have a 50-field cap

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

  • MerusCase Cases have no Nutshell equivalent — case metadata scatters across person records

    Nutshell has no native case or matter object. MerusCase cases carrying multiple parties, a case type, case status, filing date, opposing counsel, and UTBMS billing codes must be decomposed. We assign case metadata to the primary party (typically the plaintiff or retained client), and other parties reference the primary party's case number. Firms with complex multi-party litigation must decide which party is the primary record holder before migration — we surface this decision during the planning call and include a case-ownership mapping worksheet in the migration plan.

  • UTBMS L-codes and A-codes have no native home in Nutshell

    MerusCase encodes legal billing with UTBMS L-codes (task) and A-codes (activity) per time entry in the case ledger. Nutshell has no billing module and no UTBMS support. Time entries and their UTBMS codes cannot be imported as billable items — they land as reference-only data. We export the full case ledger as a CSV and attach it to the primary person record, but the firm must handle billing reconciliation outside Nutshell or through a legal-specific billing integration. This is disclosed upfront during scoping so the firm can export their ledger from MerusCase before the migration window closes.

  • MerusCase Immigration tabs and specialty fields require manual Nutshell setup

    Immigration-specific MerusCase tabs (prior addresses, employment history, hearing scheduling) are implemented as custom fields in MerusCase's case-type configuration. These do not map to any Nutshell feature — immigration-specific data like A-number, visa type, or immigration court appear as text or date custom fields on the person record with no structured immigration workflow. Firms doing immigration work should plan for a manual review of all specialty fields post-migration to ensure data is readable in Nutshell's flat custom-field model.

  • MerusCase workflows and statute reminders do not transfer — Nutshell has no equivalent trigger model

    MerusCase Workflows activate when an activity tag or description text is entered, automatically creating tasks, calendar entries, and statute-of-limitations reminders tied to filing dates. Nutshell's automation is limited to personal email sequences (Pro plan) and basic task assignment — there is no event-driven workflow engine. Workflow definitions export as a text document from MerusCase, but the firm must rebuild triggers manually in Nutshell or adopt a third-party automation layer. Statute-of-limitations tracking requires a separate legal calendar tool or manual Nutshell task creation.

  • MerusCase Document Archives require manual re-upload and per-case folder structure is lost

    MerusCase's Document Archives generate a per-case ZIP containing all case documents and a CSV of case activities. Nutshell has no case-level document folder structure — documents attach directly to a Person record as a flat list. When migrating, we download each Document Archive, extract the files, and re-upload them as individual attachments on the corresponding Nutshell Person. The original folder hierarchy (pleadings/, discovery/, correspondence/) is flattened. Firms with large document sets should plan for a bulk upload session and should retain the original Document Archive ZIPs for reference.

Migration approach

Six steps for a successful MerusCase to Nutshell data migration

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

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

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

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

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

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

Context on both ends of the pair

MerusCase logo

MerusCase

Source

Strengths

  • Fully HIPAA-compliant cloud platform with bank-grade encryption across all stored firm data.
  • Integrated billing ledger with UTBMS task, activity, and expense code support out of the box.
  • Document automation, batch scanning, and EAMS integration built into the core platform.
  • Dedicated migration coordinator assigned to each firm transitioning from another system.
  • Monthly product updates with new features and refinements across case types.

Weaknesses

  • Annual subscription model requires prepayment; no month-to-month flexibility for smaller firms.
  • Primary data export is per-case Document Archive — no single full-firm export without contacting support and paying a manual processing fee.
  • MerusCase's own migration team only supports inbound migrations, not outbound.
  • Built-in CSV import tools are explicitly documented as not easy to use, requiring white-glove service for most data loading tasks.
  • Workflows and Statutes cannot be exported or migrated programmatically — they are platform-native and must be rebuilt from scratch.
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 MerusCase 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

    MerusCase: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most MerusCase-to-Nutshell migrations complete in 48–72 hours for firms with under 25,000 parties and a single case type. Multi-case-type firms with 100,000+ activity records extend to 7–14 days because each case type requires its own custom field configuration and UTBMS mapping pass. The longest step is typically the custom field setup in Nutshell and the document re-upload from Document Archives — both depend on how many files are stored per case.

Adjacent paths

Related migrations to explore

Ready when you are

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