Migrate from NextChapter to Salesforce Sales Cloud

No native 'case file' object means all filing data must live inside Salesforce Account custom fields

Salesforce has no standard object representing a bankruptcy case file. All NextChapter case-level data — chapter type, filing date, trustee, schedules A–J status, POC filed flag, and discharge date — must be stored as custom fields on the Account record. This means your Salesforce page layout for the Account object needs to be rebuilt to display bankruptcy-specific fields in a logical group, separate from standard Account fields. We deliver a page layout design plan before migration so your admin can pre-build the layout and assign it to profiles. Until the layout is configured, the case data is visible in record detail but not organized the way attorneys expect to see it.

Document re-upload is required — NextChapter file format does not map directly to Salesforce Files

NextChapter stores petition PDFs, court orders, and schedule attachments in a cloud document repository tied to each case. Salesforce Files (ContentVersion/ContentDocument) have a different storage architecture: each file must be re-uploaded as a binary blob with metadata. We download the NextChapter file set, convert the file references to Salesforce ContentVersion records, and attach each to the Account via ContentDocumentLink. Files are linked correctly, but the Salesforce 25MB per-file limit applies — unusually large petition exhibits may need to be split or stored in a linked SharePoint library rather than as Salesforce Files.

Case number may not exist at extraction time for in-progress intake cases

NextChapter generates the official case number through the court e-filing integration during the intake wizard — often after the initial case record is created in NextChapter. Cases that are in intake but not yet officially filed will not have a case number in NextChapter at the time of migration extraction. We flag these records with a Case_Number_Status__c field set to 'Pending — Intake In Progress' and re-query the case number after the filing is complete. For firms with a large intake pipeline, this may require a second delta run to backfill case numbers post-filing.

NextChapter workflows and document templates cannot be migrated to Salesforce Flow or Salesforce Docs

NextChapter automations — intake questionnaire logic, document generation triggers, hearing reminder schedules, and task auto-creation rules — are built inside the NextChapter platform and have no Salesforce equivalent. Salesforce Flow, Process Builder, and Salesforce Docs handle similar use cases but require rebuilding from scratch. FlitStack AI exports your NextChapter workflow definitions as a structured JSON reference document that your Salesforce admin can use to configure equivalent Flows. We flag which automations exist in NextChapter before migration so no automation is accidentally left unaddressed.

SALI field standards map to pick-lists that require post-migration admin configuration

NextChapter encourages use of SALI (Standardized Legal Industry) field codes for bankruptcy data. The SALI taxonomy includes debtor type, case stage, asset status, and jurisdiction codes stored as pick-lists in NextChapter. These map to custom pick-list fields on the Account object in Salesforce, but Salesforce requires each pick-list value to be manually entered in Setup unless you use a metadata deployment tool. We generate the pick-list values as a data load script your admin runs after the migration, or we handle the metadata deployment directly as part of the migration package.