CRM migration

Migrate from Case Status to Nutshell

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

Case Status logo

Case Status

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between Case Status and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Case Status is a client-experience platform built specifically for law firms — it tracks client portals, case stages, matter milestones, engagement activity, and NPS alongside standard contact and company records. Teams migrate to Nutshell when they want a general-purpose CRM with transparent per-seat pricing, native email marketing, and a simpler schema that non-legal-industry staff can navigate without law-firm-specific training. FlitStack AI maps every Case Status contact, company, matter, engagement log, and custom property into Nutshell People, Companies, Deals, and custom fields. Legal-specific concepts like case type, case stage, portal access status, and client milestone dates land as Nutshell custom fields since Nutshell has no native legal-matter object. We preserve the original Case Status IDs on every record for traceability and run a delta-pickup window (24–48 hours) to capture any matter updates made during the cutover window. What does not migrate: Case Status workflow automations (trigger-based client outreach rules), email templates, client-portal configurations, and legal-specific role assignments. Those must be rebuilt manually in Nutshell or exported as reference documentation for your admin. The migration reads Case Status data via scoped API access — your team keeps using Case Status throughout the run.

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

Case Status logo

Case Status

What's pushing teams away

  • Firms report that Case Status is a portal layer rather than a full case management system, so they end up paying for both Case Status AND a separate practice management tool, creating double-licensing costs.
  • Some customers cite frustration that automation options feel limited compared to what they can build in their primary CRM, requiring workarounds or third-party integrations for complex client communication sequences.
  • Pricing is not transparently published on the website, and firms report surprise costs when adding the API access tier, premium support, or migration assistance as separate line items.

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

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

Case Status

Contact

maps to

Nutshell

Person

1:1
Fully supported

Case Status contacts map 1:1 to Nutshell People. All standard contact properties (name, email, phone, title, address) pass through directly. Portal access status and NPS scores land as custom fields since Nutshell has no native client-portal or satisfaction-score object. We also preserve the original Case Status contact ID as a custom field for reference and to support delta-pickup deduplication.

Case Status

Company

maps to

Nutshell

Company

1:1
Fully supported

Case Status companies map to Nutshell Companies directly. The company name, domain, industry, and employee count fields pass through. If the source company has no legal-matter records attached, it migrates as a plain Nutshell Company with no additional custom fields populated.

Case Status

Matter

maps to

Nutshell

Custom Fields on Person / Deal

1:1
Fully supported

Nutshell has no native legal-matter object. We map Case Status matter fields (case_type, case_stage, date_opened, date_closed, milestone_dates) to Nutshell custom fields on the related Person record. Where matters have a financial value or retainer, we map those as Nutshell Deals linked to the Person.

Case Status

Engagement Activity (attorney notes, client interactions)

maps to

Nutshell

Activity

1:1
Fully supported

Case Status engagement activity logs — attorney notes, client check-in calls, email threads, meeting records — migrate as Nutshell Activities. The original timestamp and activity owner are preserved. We tag each activity with a custom field linking it back to the related Case Status matter for traceability.

Case Status

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Prospective client leads in Case Status map to Nutshell Leads. Source lead status values are mapped via value translation to the closest Nutshell Lead status pick-list value. Unconverted leads land in Nutshell as Leads; converted leads route to People based on the source's conversion timestamp.

Case Status

Custom Property (contact-level)

maps to

Nutshell

Custom Field (on Person)

1:1
Fully supported

Case Status custom contact properties — beyond standard name/email/phone — migrate as Nutshell Person custom fields. The field type is inferred from the source value (text, number, date, pick-list). Pick-list values are mapped one-by-one to Nutshell custom field options. During pre-flight we validate that each pick-list value exists in Nutshell; any unmatched values are flagged for manual mapping before the migration run begins.

Case Status

Custom Property (matter-level)

maps to

Nutshell

Custom Field (on Person / Deal)

1:1
Fully supported

Legal-specific custom properties on Case Status matters (e.g., practice_area, referring_attorney, court_location) map to Nutshell custom fields. If a matter has no associated Person record in the destination, we create a placeholder Person and attach the custom fields there. These custom fields are attached to the Person record so that case-level details remain searchable and filterable within Nutshell's list views and reports.

Case Status

Portal Access Status

maps to

Nutshell

Custom Field (on Person)

1:1
Fully supported

Case Status portal_access_status (active/invited/pending) has no Nutshell equivalent. We migrate it as a pick-list custom field on the Person record. Your team decides post-migration whether to recreate the portal workflow using Nutshell's Sales Email sequences or a third-party client portal integration.

Case Status

NPS / Satisfaction Score

maps to

Nutshell

Custom Field (on Person)

1:1
Fully supported

Case Status NPS and satisfaction score fields map to a Number-type custom field on Nutshell People. Historical NPS values are preserved for reporting continuity. Nutshell has no native NPS tracking — this is a reference field only. We recommend adding this field to your Nutshell dashboard to visualize client satisfaction trends over time, even though alerts or automations cannot be triggered directly from it.

Case Status

Staff / Attorney (Case Status user)

maps to

Nutshell

Owner (Nutshell user)

1:1
Fully supported

Case Status staff and attorney records resolve to Nutshell users by email address match. Any staff without a corresponding Nutshell user account is flagged before migration. Your team either creates the Nutshell user first or assigns those records to a fallback owner.

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.

Case Status logo

Case Status gotchas

High

No publicly documented public API for self-service exports

High

Portal data is partially decoupled from source case management

Medium

Add-on pricing model obscures true cost for migration assistance

Medium

Custom properties are stored as JSON key-value pairs with limited schema visibility

Low

Client app notifications and push token state does not transfer

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

  • Legal-matter fields have no native Nutshell destination

    Case Status stores case_type, case_stage, date_opened, and milestone dates on contacts and separate matter records. Nutshell has no legal-matter or case object — all of these fields become Nutshell custom fields on Person records. The migration plan must enumerate every Case Status custom property before schema creation so your Nutshell admin can pre-create the custom fields. If the matter includes a financial value, we create a linked Nutshell Deal — but Nutshell Deals use pipeline-stage semantics that differ from legal case progression.

  • Case Status workflow automations do not migrate

    Case Status automations trigger on client-portal events (e.g., 'send reminder when case stage changes to Discovery'), date-based milestones, and lead-score thresholds. Nutshell Sales Email sequences trigger on stage entry and stop on reply — this is a fundamentally different automation model with no direct equivalent to date-triggered legal workflows. We export your Case Status automation definitions as a rebuild reference document for your Nutshell admin. Any automations relying on legal-specific triggers (court date reminders, bar-deadline alerts) have no native Nutshell equivalent and must be rebuilt with a third-party tool or manual process.

  • Engagement activity loses matter context unless tagged with custom field

    Case Status engagement logs (attorney notes, client calls, meeting records) carry implicit matter context because they are attached to a case record. When these migrate as Nutshell Activities, that context is lost unless we explicitly tag each activity with the Case Status matter ID as a custom field. We do this tagging by default, but Nutshell's Activity UI does not surface this field prominently — your team needs to add the custom field column to the Activity list view to see matter context at a glance. Without this configuration, attorneys lose the quick link between a phone call and the related case.

  • Contact count limits on Nutshell plan tiers may conflict mid-migration

    Nutshell enforces contact limits per plan tier (100 on entry plans, scaling up to 500,000+ on Enterprise). If your Case Status instance has more contacts than your target Nutshell plan allows, the migration will fail or truncate at the plan limit. We flag this before migration begins and recommend a plan upgrade or a contact-cleanup pass to de-duplicate inactive matter contacts. A plan-tier conflict mid-migration can corrupt the record sequence and require a full restart.

  • Client-portal access status is informational, not functional in Nutshell

    Case Status portal_access_status tracks whether a client has accepted their portal invitation. We migrate this as a read-only custom field on Nutshell People. Nutshell has no client-portal feature — the field is preserved as historical reference only. If your firm relies on the portal access flag to trigger follow-up actions (e.g., 'send welcome email if portal_status = pending'), that automation must be rebuilt in Nutshell using Sales Email sequences or a third-party client portal integration. The data migrates correctly; the workflow does not.

Migration approach

Six steps for a successful Case Status to Nutshell data migration

  1. Audit Case Status custom properties and matter structure

    FlitStack AI reads your Case Status export or API data and catalogues every standard and custom contact property, matter field, and engagement log type. We produce a migration plan that lists each Nutshell custom field to pre-create, each pick-list value to set, and each matter-to-Person relationship to establish. Your Nutshell admin creates the custom fields before the migration run so schema validation passes on the first attempt.

  2. Resolve Case Status users and attorneys to Nutshell owners

    We match Case Status staff and attorney records to Nutshell users by email address. Any attorney without a corresponding Nutshell user is flagged in the pre-flight report — your team creates the Nutshell account or assigns those records to a fallback owner before migration. No record lands in Nutshell without a resolved owner, preventing orphaned matter assignments. We also preserve role type (attorney, paralegal, case manager) as a custom field for future routing.

  3. Migrate companies and people before matters and activities

    Nutshell requires companies to exist before people can reference them (via the company field on Person), and people to exist before activities can link to them. We sequence the migration: Companies → People → Leads, then matter custom fields on Person records, then Deal creation for matters with financial values, then Activities tagged with matter IDs. This ordering ensures foreign-key integrity across the Nutshell schema.

  4. Run a sample migration with field-level diff

    A representative slice of 100–500 records migrates first, covering at least one Person with a full matter record, an activity log, a lead record, and a company. We generate a field-level diff report showing every source value, mapped destination field, and any transformation applied. You verify case_stage mapping, portal_access_status preservation, and activity-matter tagging before the full run commits. This sample run also validates that pick-list values for case_type and case_stage translate correctly into Nutshell's custom field options, reducing the risk of data loss on the full dataset.

  5. Cut over with delta-pickup for in-flight matter updates

    The full migration runs against Nutshell's JSON-RPC API. Your team continues using Case Status during the run — FlitStack uses scoped read access only. A delta-pickup window (24–48 hours) captures any matter updates, new client records, or case-stage changes made during cutover. Audit log records every operation. One-click rollback reverts all migrated records if reconciliation fails. The delta window also captures any new engagement activities logged by attorneys after the initial load, ensuring that notes, calls, and meeting records added during the transition appear in Nutshell without manual re-entry.

Platform deep dives

Context on both ends of the pair

Case Status logo

Case Status

Source

Strengths

  • Highly-rated mobile app and client portal that requires no custom development to deploy
  • Built-in AI for message triage and client intelligence that surfaces urgent communications proactively
  • Seamless integration ecosystem with Clio, PracticePanther, MyCase, and other leading legal case management platforms
  • Client satisfaction tracking via NPS with automated review request workflows that drive referral growth
  • G2-recognized ease of use for admins and AI assistant categories, indicating low learning curve for firm staff

Weaknesses

  • Platform is a client-facing layer rather than a full practice management system, requiring firms to maintain a separate case management license
  • No publicly documented API — full API access requires a paid tier, limiting programmatic data extraction options
  • Automation builder lacks the depth of enterprise CRM workflow engines, limiting complex client communication sequences
  • Pricing lacks public transparency, with many features billed as add-ons rather than included in published tiers
  • Small company footprint (~$4.5M revenue, ~77 employees) raises long-term viability and support capacity questions for large firm deployments
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. 1 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 Case Status and Nutshell.

  • Object compatibility

    B

    1 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

    Case Status: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Case Status to Nutshell migrations complete in 24–72 hours of clock time for firms with under 10,000 contacts and fewer than 50 custom properties. Firms with 50,000+ records or complex matter-to-deal relationships extend to 5–10 days. The longest phase is usually the pre-flight: auditing Case Status custom properties and pre-creating Nutshell custom fields for legal-matter fields like case_type and case_stage.

Adjacent paths

Related migrations to explore

Ready when you are

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