Migrate from NextChapter to HighLevel

NextChapter Case has no direct HighLevel equivalent. Case number maps to Opportunity name, chapter type (Chapter 7/11/13) becomes a custom pick-list field, filing date becomes a custom date field, and trustee name becomes a custom text field. The case status (active, discharged, dismissed) maps to a pipeline stage via value mapping. FlitStack sequences Cases after Contacts so the Opportunity-Contact relationship resolves correctly via the HighLevel Contact Opportunity association.

Debtor records in NextChapter map directly to HighLevel Contacts. Debtor name splits to first_name and last_name, SSN last four digits store as a custom encrypted field, and phone, email, and address fields map 1:1. The attorney_id on the debtor resolves by email match to an existing HighLevel user or Contact record. Multi-debtor cases (joint filings) create multiple Contact records linked to the same Opportunity.

NextChapter attorney records contain name, bar number, email, and phone. These map to HighLevel Users if the attorney needs CRM access, or to Contacts if they are a referral partner tracked in the CRM but not a system user. FlitStack flags attorney records for client decision on user vs. contact classification before migration runs.

NextChapter calendar entries (court dates, 341 meeting dates, filing deadlines) map to HighLevel Calendar appointments. Event title maps to appointment subject, start time maps to start_date, end time maps to end_date, and the linked case_id links to the corresponding Opportunity. Recurring events are preserved as a series. Reminder settings are carried as HighLevel appointment reminders.

NextChapter task lists attached to cases migrate as HighLevel Tasks. Task name maps to subject, due date maps to due_date, assigned user maps by email match, and the linked case maps to the Opportunity via the Opportunity-Contact relationship. Checklist items within a task are flattened into individual Task records in HighLevel.

NextChapter case notes and general notes map to HighLevel Notes. Note body maps to the Note content field, create date maps to created_at, and the note is linked to the appropriate Contact or Opportunity record. Notes with attachments require a separate handling step since HighLevel Notes don't natively support file uploads.

Custom fields defined on NextChapter Cases (beyond the standard case_number, chapter_type, filing_date, trustee_name, case_status) map to HighLevel custom fields on the Opportunity object. Field type mapping: text fields to Short Text, pick-lists to Drop-down (multiple), dates to Date fields. FlitStack creates the custom fields in HighLevel before migration and maps values during the load phase.

Custom fields defined on NextChapter Debtor records map to HighLevel custom fields on the Contact object. SALI field taxonomy from NextChapter (if used) maps to equivalent HighLevel field types. Fields requiring address parsing or phone formatting get transformation during migration. FlitStack validates field type compatibility before creating the custom fields.

NextChapter document attachments (PDF court forms, signed documents, correspondence PDFs) have no native equivalent in HighLevel's note model. FlitStack exports all attachments to a ZIP archive organized by case number. A Note is created in HighLevel referencing the exported file path. The firm re-uploads files to HighLevel's document storage or a linked external system post-migration.

NextChapter payment records (filing fees, attorney fees, trustee payments) can map to a HighLevel Custom Object for fee tracking, or to custom fields on the Opportunity if all fees are case-level. FlitStack maps these based on the firm's chosen structure — the default is a Custom Object with fields for payment_date, amount, payment_type, and status. Financial records stay in NextChapter for audit; only summary amounts migrate to HighLevel.