CRM migration

Migrate from The Case File to Nutshell

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

The Case File logo

The Case File

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between The Case File and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

The Case File organizes data around legal matters: clients, opposing parties, case events, documents, and billing entries tied to specific case numbers. Nutshell is a sales CRM that models People, Companies, Leads, and Deals with pipeline stages, activity tracking, and integrated email. These are fundamentally different data architectures — The Case File has no native equivalent to Nutshell's Deals or pipeline stages, and Nutshell has no concept of legal case numbering, court dates, or matter types. FlitStack AI extracts The Case File records via API or export file, maps parties to Nutshell People and Companies, maps case activities to Nutshell Activities, and maps matter-stage information to a custom pipeline field. We preserve original create dates, owner assignments, and document references. We do not migrate court-specific workflows, filing automations, or billing logic — those require manual rebuild in Nutshell or a separate billing tool. The migration runs as a scoped read on The Case File, with a delta-pickup window capturing in-flight changes during 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

The Case File logo

The Case File

What's pushing teams away

  • Document management limitations make handling extremely large or complex litigation document sets difficult.
  • The platform lacks depth for multi-party or high-volume matters that require advanced workflow automation.
  • Reporting and analytics are basic compared to purpose-built litigation analytics platforms.
  • Limited API documentation and third-party integration ecosystem makes automation difficult.
  • Some firms outgrow the platform as they scale and need more robust matter-level permissions controls.

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

Each row shows how a The Case File 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.

The Case File

Client / Party

maps to

Nutshell

Person

1:1
Fully supported

The Case File clients and named parties map directly to Nutshell People records. Nutshell stores name, email, phone, title, and address as standard fields. Parties without email addresses are migrated with available contact fields and flagged for data enrichment review.

The Case File

Opposing Party / Insurance Carrier

maps to

Nutshell

Company

1:1
Fully supported

Organizations named as opposing parties, insurance carriers, or corporate defendants in The Case File map to Nutshell Companies. Nutshell's Company object stores name, domain, industry, employee count, and annual revenue. Carrier-specific data (policy numbers, coverage limits) migrates as custom fields on the Company record.

The Case File

Matter / Case

maps to

Nutshell

Deal

1:1
Fully supported

The Case File matter records map to Nutshell Deals, which represent client engagements or matters open in the system. Matter number becomes a custom field (Original_Matter_Number__c) for reference. Matter stage (Intake, Active, Pending, Closed) maps to a custom pick-list field mapped to Nutshell pipeline stages.

The Case File

Matter Stage / Status

maps to

Nutshell

Pipeline Stage

1:1
Fully supported

The Case File matter status values (e.g., Active, Discovery, Mediation, Trial, Closed) require explicit value-by-value mapping to Nutshell pipeline stage names. The mapping is configured before migration so each matter lands in the correct pipeline column in Nutshell's Board or List view.

The Case File

Attorney / Staff

maps to

Nutshell

Nutshell User

1:1
Fully supported

Attorneys and staff assigned to matters in The Case File are resolved by email match against existing Nutshell users. Unmatched users are flagged before migration; firms either create Nutshell accounts for them or assign their records to a fallback owner. Owner resolution is validated before any record is written.

The Case File

Case Event / Calendar Entry

maps to

Nutshell

Activity (Task or Event)

1:1
Fully supported

Court dates, filing deadlines, deposition schedules, and attorney notes from The Case File map to Nutshell Activities. Events with a start/end time map to Nutshell Events; discrete action items map to Tasks. Original timestamps and assigned attorneys are preserved on each activity record.

The Case File

Document / Attachment

maps to

Nutshell

Nutshell File

1:1
Fully supported

Documents attached to The Case File matters are re-uploaded as Nutshell Files and attached to the corresponding Person or Deal record. Files over Nutshell's 25MB per-file limit are flagged for pre-split before migration. Nutshell Files support PDF, DOCX, XLSX, and image formats by default.

The Case File

Time Entry / Billing Record

maps to

Nutshell

No Equivalent in Nutshell

1:1
Fully supported

Time entries and billing records tied to The Case File matters cannot migrate to Nutshell because Nutshell lacks native billing or time-tracking objects. These records should be exported as a separate report and archived in a document storage system, or handled by a dedicated billing tool post-migration.

The Case File

Custom Matter Fields

maps to

Nutshell

Custom Fields on Person / Company / Deal

1:1
Fully supported

Practice-area-specific fields on The Case File matters (e.g., statute of limitations, jurisdiction, expert witness names, settlement range) have no direct Nutshell equivalent. These migrate as custom fields on the Deal record, created in Nutshell before the migration run. The firm identifies field types during scoping so Nutshell custom field schemas are ready before data lands.

The Case File

Conflict Check Record

maps to

Nutshell

No Equivalent in Nutshell

1:1
Fully supported

Conflict check records and conflict flags in The Case File are not migratable to Nutshell. Nutshell has no native conflict-check mechanism; firms should run a conflict check in Nutshell before importing and consider a dedicated legal ethics compliance tool for ongoing conflict management.

The Case File

Matter Note / Communication Log

maps to

Nutshell

Activity (Task) with Note

1:1
Fully supported

Case notes and attorney communications logged in The Case File map to Nutshell Tasks with a note body containing the original text. Timestamps and author attribution are preserved. Long notes are truncated if they exceed Nutshell's note field length limits — flagged in the sample migration diff.

The Case File

Medical Record / Evidence Reference

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

Medical record references, evidence identifiers, and exhibit lists on personal-injury or litigation matters migrate as long-text custom fields on the corresponding Deal record. The original text is preserved verbatim; Nutshell's long-text area field type accommodates entries up to 32,768 characters, which is sufficient for most medical records and evidence references. Any references to external document IDs are preserved as linked text for traceability.

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.

The Case File logo

The Case File gotchas

High

No publicly documented API for programmatic data extraction

High

Trust account ledger balances require manual verification

Medium

Custom fields lack a documented export schema

Medium

Document folder structure does not export flatly

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

  • Matter-stage to pipeline mapping requires explicit value-by-value configuration

    The Case File matter stages (Intake, Discovery, Mediation, Trial, Closed) have no native equivalent in Nutshell, which uses sales pipeline stages. FlitStack builds a value-mapping table during scoping — each matter status is assigned a Nutshell pipeline stage by the firm. If a matter status has no defined mapping, records land in a default 'Backlog' stage and are flagged. The mapping table is reviewed in the sample migration diff before the full run commits, so stage routing can be corrected before data lands in Nutshell. This is pair-specific because the mapping logic depends on both the firm's matter status taxonomy and how Nutshell's pipeline is configured.

  • Billing records and time entries have no Nutshell home

    The Case File ties time entries, billing records, and trust accounting to matter records. Nutshell has no native billing, invoicing, or time-tracking objects. FlitStack cannot migrate these — they must be exported as a separate report from The Case File and archived in a document storage system or a dedicated billing tool. Firms that rely on The Case File for client invoicing should plan a parallel billing workflow before the cutover date, as Nutshell will not reflect outstanding balances or trust account status after migration.

  • Large document bundles may exceed Nutshell file size limits

    Legal matters often contain document bundles with exhibits, medical records, and correspondence exceeding individual file size thresholds. Nutshell's default file upload limit is 25MB per file. Files larger than 25MB are flagged during the migration scan and split into volumes before upload, with a reference custom field (Original_File_Split_Ref__c) linking split segments. This is specific to The Case File-to-Nutshell because legal document bundles are systematically larger than typical CRM file attachments.

  • Attorney-to-User email matching is required before migration

    Nutshell assigns records to Users by email match. If an attorney in The Case File does not have a corresponding Nutshell user account, their assigned matters and activities are flagged as 'unresolved owner' and land under a fallback system user. The fallback approach must be decided during scoping — either pre-create Nutshell accounts for all attorneys or accept the fallback assignment. This creates a manual step before migration that is specific to The Case File's attorney-assignment model.

  • Conflict check records cannot migrate and conflict logic must be rebuilt

    The Case File stores conflict check records and conflict flags per matter, tied to the firm's conflict database. Nutshell has no native conflict-check mechanism — conflict records cannot migrate and the logic (checking adverse parties, related entities, and lateral hires) has no Nutshell equivalent. The firm should run a conflict check in Nutshell before importing and consider integrating a dedicated legal ethics compliance tool for ongoing conflict management post-migration. Because Nutshell lacks this capability entirely, the compliance team must establish a new workflow for conflict screening in the CRM environment.

Migration approach

Six steps for a successful The Case File to Nutshell data migration

  1. Export and inventory The Case File data

    FlitStack initiates a scoped read of The Case File via export file or API, extracting all People, Companies, Matters, Activities, and Documents. We produce a data inventory report showing record counts per object, custom field inventory per matter type, and file size distribution for the document set. This inventory drives the field-mapping plan and surfaces any objects that have no Nutshell equivalent before the migration design begins.

  2. Design Nutshell custom field schema

    Based on the inventory findings, FlitStack delivers a detailed Nutshell schema setup plan specifying the exact custom fields required on each object: Person (Party_Type__c), Company (Carrier_Info__c), Deal (Matter_Type__c, Original_Matter_Number__c, Jurisdiction__c, Statute_of_Limitations__c, Opened_Date__c, Closed_Date__c), and Activity (Activity_Type__c). The firm's Nutshell administrator creates these fields in Nutshell before the migration run. We provide precise field names, data types, and pick-list value definitions to streamline the setup and minimize iterative back-and-forth during the configuration phase.

  3. Build value-mapping tables and resolve owners

    FlitStack constructs the matter-status-to-pipeline-stage value-mapping table, defining how each The Case File status (Intake, Active, Discovery, Mediation, Trial, Closed) routes to the appropriate Nutshell pipeline stage column. Simultaneously, we run the complete attorney and staff email list from The Case File against Nutshell's existing user roster to identify email matches and flag any unresolved owners for the firm to address. Both the value-mapping table and the owner-resolution list are delivered as artifacts for the firm to review, validate, and approve before the sample migration is executed.

  4. Run sample migration with field-level diff

    A representative sample — typically 100–500 records spanning clients, companies, matters, activities, and a sample document — migrates to Nutshell first. We generate a field-level diff report showing every mapped field, its source value, its destination value, and any discrepancies. The firm reviews the diff to verify stage mapping, owner resolution, document attachment links, and the handling of custom fields before the full run is authorized.

  5. Execute full migration with delta-pickup window

    The full migration runs against Nutshell. A delta-pickup window (24–48 hours after the primary run) captures any records created or modified in The Case File during the cutover window. All operations are logged to an audit trail. One-click rollback is available if reconciliation identifies missing records or incorrect mappings. After rollback window closes, the firm validates the final Nutshell dataset against the data inventory report.

Platform deep dives

Context on both ends of the pair

The Case File logo

The Case File

Source

Strengths

  • Cloud-native platform with no on-premises infrastructure requirements for the standard edition.
  • Native Full Data Backup tool and export spreadsheets provide a structured data extraction path.
  • Integrated client intake, case management, billing, and time tracking in one platform.
  • Good mobile app availability for attorneys working outside the office.
  • Dedicated Data Migration help center collection suggests some investment in migration tooling.

Weaknesses

  • Limited public API documentation makes programmatic migration and integration work harder to plan.
  • Document management is basic; large-scale litigation document sets are difficult to organize within the platform.
  • Reporting and analytics capabilities are shallow compared to specialized litigation software.
  • Third-party integrations ecosystem is smaller than enterprise-class legal CRMs.
  • Custom field definitions must be reviewed manually during migration scoping as no exportable schema is documented.
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 The Case File 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

    The Case File: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most The Case File to Nutshell migrations complete in 48–72 hours for setups under 25,000 records. Legal-matter structures with high custom-field density, multiple matter types, or large document bundles extend the timeline to 7–14 days. The longest planning step is designing the matter-status-to-pipeline-stage value-mapping table and creating Nutshell custom fields — both happen before the migration run and are included in the overall timeline estimate.

Adjacent paths

Related migrations to explore

Ready when you are

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