CRM migration

Migrate from The Plaintiff to Nutshell

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

The Plaintiff logo

The Plaintiff

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between The Plaintiff and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

The Plaintiff organizes legal work around matters (cases), parties, and billing entries with a structure built for law firm workflows. Nutshell employs a standard CRM model using People (contacts), Companies (accounts), Deals (opportunities), and Activities (tasks and events). The migration transfers all core objects — client records, opposing parties, case references, time entries, and activity history — into their Nutshell counterparts while preserving original create dates, attorney assignments, and case statuses. Custom fields on the People and Companies objects capture legal-specific attributes such as bar numbers, matter types, case roles, and billing rates. Extraction from The Plaintiff occurs through the available export endpoints, and data loads into Nutshell via the Nutshell REST API using bulk import calls. Workflow automation, document templates, and billing calculations are not transferred and must be reconstructed using Nutshell's automation rules and settings. A delta‑pickup window of 24–48 hours after the initial run captures any updates made in The Plaintiff during the cutover, ensuring the final Nutshell dataset reflects the most recent state. FlitStack AI maintains a full audit log of all migration operations and provides rollback capability if data integrity issues arise.

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 Plaintiff logo

The Plaintiff

What's pushing teams away

  • Interface feels outdated compared to modern cloud-based case management platforms, prompting firms to seek updated tooling.
  • Date fields cannot be modified by non-admin users once saved, creating workflow bottlenecks when deadline information changes.
  • Limited automation for document assembly and deadline tracking relative to newer plaintiff-focused platforms.
  • Feature set has not kept pace with integrated tools available in competing legal CRMs, causing growing firms to outgrow the platform.
  • Difficult to scale or customize for plaintiff firms with expanding practice areas or increasing case volume.

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

Each row shows how a The Plaintiff 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 Plaintiff

Client / Party (Plaintiff or Defendant)

maps to

Nutshell

Person

1:1
Fully supported

Individual parties in The Plaintiff migrate to Nutshell People. The party type (plaintiff, defendant, witness) is stored as a custom pick-list field on the Person record. Multiple parties sharing one matter generate separate Person records linked via the associated Deal.

The Plaintiff

Organization Party

maps to

Nutshell

Company

1:1
Fully supported

Corporate parties and law firm organizations migrate as Nutshell Companies. Company name, address, and domain map directly. Attorney firm names associated with parties become Companies with a custom 'Party Role' field set to 'Opposing Counsel' or 'Co-Counsel'. The mapping also includes address fields and any associated phone numbers, which transfer directly to the Company's standard contact fields.

The Plaintiff

Matter / Case

maps to

Nutshell

Deal

1:1
Fully supported

The Plaintiff matters become Nutshell Deals. Matter number maps to Deal name for reference; a custom 'Matter Number' field preserves the original identifier. The primary client Party becomes the Deal's associated Person; opposing parties are linked via activity notes or secondary Person records. Nutshell's Deal stages (Qualifying, Proposal, Negotiation, Closing) require mapping from The Plaintiff's case status values.

The Plaintiff

Time Entry / Billing Record

maps to

Nutshell

Custom Field on Deal + Activity

1:1
Fully supported

The Plaintiff time entries have no native Nutshell equivalent. Hours logged, billing rate, and total fees are stored as custom fields on the associated Deal. Individual time entries are preserved as Nutshell Activities (tasks) with the time entry description as the task subject and hours as a custom numeric field.

The Plaintiff

Calendar Event / Deadline

maps to

Nutshell

Activity (Task/Event)

1:1
Fully supported

Court dates, filing deadlines, and attorney appointments migrate as Nutshell Activities. Events with a start/end time map to Nutshell Events; deadline reminders map to Tasks with a due date. All activities are linked to the associated Matter (Deal) for context. Original timestamps and assigned attorney are preserved.

The Plaintiff

Note / Document Reference

maps to

Nutshell

Note

1:1
Fully supported

The Plaintiff notes attached to matters migrate as Nutshell Notes linked to the corresponding Person, Company, or Deal. Document URLs and file references are stored as text fields since Nutshell does not host attachments from external legal DMS systems natively — your team maps document links manually post-migration.

The Plaintiff

Attorney / Staff User

maps to

Nutshell

Nutshell User

1:1
Fully supported

The Plaintiff users are matched to Nutshell users by email address. If a The Plaintiff user has no matching Nutshell account, they are flagged before migration — your firm creates the Nutshell user first, then the owner assignment maps. Unmatched owners default to the migration admin.

The Plaintiff

Insurance Carrier / Lien Holder

maps to

Nutshell

Company + Custom Field

1:1
Fully supported

Carriers and lien holders are stored as Nutshell Companies with a custom 'Party Role' field set to 'Insurance Carrier' or 'Lien Holder'. Their claim numbers and policy references map to custom fields on the associated Deal. The mapping also captures the carrier's phone and email, populating the Company's primary contact fields for straightforward reference.

The Plaintiff

Custom Matter Types / Case Categories

maps to

Nutshell

Custom Pick-list on Deal

1:1
Fully supported

The Plaintiff's case type taxonomy (e.g., Personal Injury, Employment, Medical Malpractice) maps to a custom pick-list field on the Nutshell Deal object. Each pick-list value is created in Nutshell Settings > Fields before migration; values map directly by name.

The Plaintiff

Medical Records / Evidence Log

maps to

Nutshell

Note + Custom Field

1:1
Fully supported

Evidence indexes and medical record references have no direct Nutshell equivalent. We preserve these as Notes on the Deal with a structured text field containing the record type, provider/facility name, and date. External DMS links are stored as URL fields for manual access. The notes also include a link back to the original DMS for quick access.

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 Plaintiff logo

The Plaintiff gotchas

Medium

Admin-only date field editing creates migration mapping gaps

High

No publicly documented API requires manual export parsing

Medium

Custom field schema varies by firm without documentation

High

Trust account and billing records excluded from standard export

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

  • The Plaintiff matters have no direct deal-stage equivalent in Nutshell

    The Plaintiff tracks case status as a flat pick-list (Open, Pending, Closed, Dismissed) without a sales-pipeline stage model. Nutshell's Deal object uses a stage field tied to the pipeline view. We map case statuses to Nutshell stage values but the firm's attorneys need to decide which Nutshell stage corresponds to each case status — particularly for matters that are 'Pending' awaiting court action versus 'Open' and actively being worked. Without this mapping, all matters land in a default stage and the pipeline board shows no meaningful progress. We deliver the mapping plan before migration and your firm confirms stage assignments per case type.

  • The Plaintiff's party-role model requires custom fields in Nutshell

    The Plaintiff distinguishes between plaintiff parties, defendant parties, witnesses, and opposing counsel within a matter. Nutshell People have no native role field — the standard fields (name, email, phone) carry contact data but not legal role context. We create a custom 'Party Role' pick-list field on the Person object and set values during migration based on The Plaintiff's party_type field. Your Nutshell admin needs to add this custom field before the migration runs. If the field is missing, role data is lost — it cannot be retrofitted after bulk import without re-running affected records.

  • Billing and time-entry data requires a custom schema before migration

    The Plaintiff time entries and billing records are structured around attorney hours and fee schedules — a model Nutshell does not support natively. Nutshell has no billing object, no time-tracking module, and no invoice generation at the Deal level. We carry hours, rates, and total fees into custom fields on the Deal and individual Activities, but Nutshell cannot perform billing calculations from these fields. Your firm should decide whether to use Nutshell's native integration with a billing tool (via Zapier or Make) or accept that fee reporting in Nutshell will be read-only reference data sourced from The Plaintiff's historical records.

  • Opposing counsel contact records may conflict with existing Nutshell data

    Many firms already have opposing counsel contacts in Nutshell from prior business-development activities. The Plaintiff imports will create duplicate Person records for the same attorneys if email addresses match. Nutshell does not have a built-in deduplication engine for bulk imports. We perform a pre-migration audit comparing The Plaintiff party emails against existing Nutshell People and surface duplicates before the run. Your firm decides whether to merge (keeping activity history from both systems) or allow duplicates. If duplicates are allowed, Nutshell's reporting on attorney activity will split across two records.

  • Document and evidence file references cannot be migrated as attachments

    The Plaintiff stores document references (file paths, DMS links, evidence exhibit IDs) that point to external systems. Nutshell's file attachment model supports uploads to Nutshell's own storage or linked files from cloud drives (Google Drive, Dropbox, OneDrive). There is no native migration path for document references stored as text strings in The Plaintiff. We preserve document paths and URLs in Note records on the associated Deal, but your team must re-link documents in Nutshell's file management after migration or configure a DMS integration to surface the documents within Nutshell's interface.

Migration approach

Six steps for a successful The Plaintiff to Nutshell data migration

  1. Audit The Plaintiff data export and Nutshell schema readiness

    FlitStack AI extracts a full export from The Plaintiff covering parties, organizations, matters, time entries, activities, and notes via the available export endpoints. We simultaneously review your Nutshell instance — identifying existing People, Companies, and Deals, and confirming that custom fields (Party Role, Case Type, Billing Rate, Total Fees, Court, Date Filed) are created in Nutshell Settings > Fields. If the custom fields are not yet created, we deliver a setup checklist before any records move.

  2. Resolve owner assignments and deduplicate existing contacts

    The Plaintiff users are matched to Nutshell users by email. We generate a pre-migration owner resolution report flagging any The Plaintiff user without a corresponding Nutshell account — your firm creates those users before migration day. Separately, we run an email-dedup report comparing The Plaintiff party emails against existing Nutshell People to surface potential duplicates. Your team decides whether to merge or allow duplicates, and we apply the resolution rule before the import runs.

  3. Run a sample migration with field-level diff on 50–100 records

    A representative slice of matters — spanning different case types, party counts, and billing volumes — migrates first into your live Nutshell instance (test environment preferred). We generate a field-level diff report showing source values mapped to destination fields for every record. Your firm's point of contact reviews party-role assignments, case-type values, billing field accuracy, and activity links. We adjust the mapping configuration based on feedback before the full migration commits.

  4. Execute full migration with delta-pickup window

    The full export from The Plaintiff runs against Nutshell using the validated mapping configuration. Companies import first (since People require an associated Company), then People with party-role assignments, then Deals with all linked activities. A delta-pickup window of 24–48 hours after the initial run captures any changes made in The Plaintiff during cutover. All operations are logged in FlitStack's audit trail, and one-click rollback reverts the Nutshell instance to its pre-migration state if reconciliation reveals data integrity issues.

  5. Reconcile record counts and validate deal pipeline integrity

    FlitStack AI compares record counts by object type (Parties → People, Organizations → Companies, Matters → Deals) between The Plaintiff export and Nutshell import. We surface any records that failed to import or landed with null required fields. The final reconciliation report is delivered alongside the audit log, giving your firm's administrators a signed-off record of what migrated and what requires manual follow-up in Nutshell.

Platform deep dives

Context on both ends of the pair

The Plaintiff logo

The Plaintiff

Source

Strengths

  • Clean, focused case dashboard that displays essential litigation information without visual clutter.
  • Date entry designed for straightforward input by legal staff with minimal software experience.
  • Standard legal terminology and workflow conventions that align with traditional plaintiff practice expectations.
  • Lightweight platform that loads quickly and runs reliably without heavy infrastructure requirements.

Weaknesses

  • Modern UI design is absent; interface appears dated relative to contemporary legal software alternatives.
  • Admin-only restriction on editing saved dates creates friction for attorneys who need to update deadline information independently.
  • Limited API documentation and export capability means migration tooling must parse the platform's flat file format directly.
  • Custom field schema is not publicly documented, requiring manual discovery during each migration scoping phase.
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 Plaintiff 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 Plaintiff: Not publicly documented — no published quotas. The platform is a packaged practice-management suite, not an API-first product..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most The Plaintiff to Nutshell migrations complete within 48–72 hours for firms with under 10,000 records across parties, matters, and activities. Firms with complex multi-party matters, high time-entry volumes, or 50,000+ records extend to 5–10 days. The longest single step is usually the owner resolution and deduplication audit before any data moves — that phase runs in parallel with your Nutshell custom field setup and typically takes 1–2 days to complete.

Adjacent paths

Related migrations to explore

Ready when you are

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