Migrate from NextChapter to Nutshell

Bankruptcy cases do not map to Nutshell deals — they require a structural rearchitecture

NextChapter organizes data around Cases (Chapter 7, 11, 13 filings) with clients, trustees, creditors, and activities all scoped to a case. Nutshell's Deal object is a sales opportunity with a pipeline stage. When migrating a bankruptcy case to Nutshell, the case becomes a Deal record, but the case lifecycle — filing, 341 meeting, discharge, closing — does not map to a standard sales pipeline. We create a custom 'Case Status' pick-list field on the Deal to preserve filing-state metadata, and we map case stages to pipeline stages where a semantic fit exists. The gap between a legal case lifecycle and a sales pipeline lifecycle must be acknowledged: Nutshell will show the case as a Deal with stage milestones, but the legal process logic that drives NextChapter's workflow automation has no native Nutshell equivalent and must be rebuilt or eliminated.

Document files cannot migrate — only metadata travels to Nutshell

NextChapter stores legal documents (petitions, schedules, court orders, creditor correspondence) with version history, access controls, and PACER-linked status. Nutshell is not a document management system — it stores notes and supports file attachments, but it has no equivalent to NextChapter's document container model, PACER integration, or versioned filing history. We migrate document metadata (filename, document type, upload date, associated case and client) as Nutshell Notes with custom fields. The actual files are exported as a separate package for re-hosting in your document storage system (Google Drive, SharePoint, or a dedicated legal DMS). Your team must re-link documents in their new storage after migration.

SALI field mapping requires pre-migration custom field creation in Nutshell

NextChapter's Pro+ plan exposes the SALI (Legal Industry) field standard — a set of standardized legal data fields for bankruptcy intake and case metadata. Nutshell has no native SALI field equivalent; every SALI field must be mapped to a Nutshell custom field on the appropriate entity (Person, Company, or Deal). We create the Nutshell custom fields before migration runs, which means your Nutshell account must have the field creation capacity for your plan tier. Some SALI fields have no reasonable Nutshell equivalent (e.g., 'means test result', 'exempt property schedule') — those are flagged in the migration plan as candidates for a separate reference document rather than a live CRM field.

NextChapter's JSON-RPC API rate limits on find operations require migration pacing

Nutshell's JSON-RPC API applies rate limits to find operations that return non-stub responses (full record data). Large migrations pulling thousands of case records, client records, and activity histories will hit these limits if run without pacing. We implement exponential backoff and request batching when Nutshell's rate limit responses (429 status) are detected, and we run the migration during off-peak hours where possible to minimize impact on your team's Nutshell usage during the migration window.

Workflow automations, filing deadline alerts, and trustee notifications do not transfer

NextChapter's automation engine drives legal-case-specific triggers: filing deadline reminders, trustee assignment notifications, court hearing alerts, and PACER status updates. Nutshell's automation tools (workflow rules, goal tracking) handle general sales triggers — lead assignment, deal stage change notifications, email sequence starts. There is no migration path for legal automation logic because the trigger conditions (filing deadlines, trustee assignment events, court calendar events) have no equivalent in Nutshell's event model. We export your NextChapter automation definitions as a reference document your team can use to rebuild the automations that still make sense in a Nutshell context (e.g., follow-up reminders after a client meeting).