CRM migration
Field-level mapping, validation, and rollback between Case Status and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Case Status
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between Case Status and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Case 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
Nutshell
Company
1:1Case 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
Nutshell
Custom Fields on Person / Deal
1:1Nutshell 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)
Nutshell
Activity
1:1Case 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
Nutshell
Lead
1:1Prospective 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)
Nutshell
Custom Field (on Person)
1:1Case 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)
Nutshell
Custom Field (on Person / Deal)
1:1Legal-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
Nutshell
Custom Field (on Person)
1:1Case 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
Nutshell
Custom Field (on Person)
1:1Case 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)
Nutshell
Owner (Nutshell user)
1:1Case 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.
| Case Status | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Matter | Custom Fields on Person / Deal1:1 | Fully supported | |
| Engagement Activity (attorney notes, client interactions) | Activity1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Custom Property (contact-level) | Custom Field (on Person)1:1 | Fully supported | |
| Custom Property (matter-level) | Custom Field (on Person / Deal)1:1 | Fully supported | |
| Portal Access Status | Custom Field (on Person)1:1 | Fully supported | |
| NPS / Satisfaction Score | Custom Field (on Person)1:1 | Fully supported | |
| Staff / Attorney (Case Status user) | Owner (Nutshell user)1: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.
Case Status gotchas
No publicly documented public API for self-service exports
Portal data is partially decoupled from source case management
Add-on pricing model obscures true cost for migration assistance
Custom properties are stored as JSON key-value pairs with limited schema visibility
Client app notifications and push token state does not transfer
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 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.
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.
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.
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.
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
Case Status
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Case Status and Nutshell.
Object compatibility
1 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
Case Status: Not publicly documented.
Data volume sensitivity
Case Status 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 Case Status to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Case Status
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.