Migrate from NextChapter to Odoo CRM

NextChapter cases map to Odoo crm.lead (opportunity/lead). The case name becomes the lead name, case status maps to a custom stage field, and all financial fields (fees, PACER costs) migrate as custom fields on the lead. The original case ID is preserved in source_id for delta-run de-duplication.

NextChapter clients nested inside cases resolve to res.partner records in Odoo. The client name maps to partner name, email to email, and address fields to street/city/state/zip. Partner records are de-duplicated by email before lead creation so one partner can have multiple linked leads (one per bankruptcy case).

NextChapter's one-case-to-one-client nesting requires the client to be migrated first so the res.partner record exists before the crm.lead is created. The partner_id on the Odoo lead is set by email match against the migrated partner record. FlitStack sequences the migration: partners first, then leads with partner_id resolved.

NextChapter case documents (PDFs, filed forms, PACER downloads) are exported and re-uploaded to ir_attachment linked to the corresponding Odoo crm.lead using the external ID stored in source_id. Document name, file type, and original upload date are preserved. Binary files are re-hosted in Odoo's filestore.

NextChapter custom fields (defined under My Account Settings > Firm Details > Custom Fields) require manual pre-creation in Odoo Studio with the x_ prefix before migration. FlitStack generates a custom-field manifest listing each NextChapter field name, type, and suggested Odoo field type so Odoo admins can pre-create them. Field values migrate as x_ field values on the lead record.

NextChapter activity history — emails, logged calls, and meeting records — migrates as mail.message entries on the crm.lead's chatter thread, preserving the original timestamp and a note indicating the activity originated in NextChapter. Call type is set in the activity type field so Odoo filters work correctly on migrated data.

NextChapter client-level custom fields (if defined at the firm level for client records) migrate as x_ fields on the res.partner record. These must be pre-created in Odoo Studio alongside the case-level field manifest. Client custom fields typically include SALI-standard fields used for debtor intake data.

NextChapter PACER fee amounts and court case numbers are bankruptcy-specific with no Odoo CRM native equivalent. FlitStack maps these to x_pacer_fee and x_court_case_number custom fields on the lead for reporting continuity. The PACER fee amount is stored as a monetary field; court case number as a char field.

NextChapter tracks the bankruptcy trustee name and payment date on the case. These migrate as x_trustee_name (char) and x_trustee_payment_date (date) custom fields on the Odoo lead. Trustee assignment workflow must be rebuilt in Odoo using server actions or a custom module.

NextChapter case_type stores the bankruptcy chapter designation (chapter_7, chapter_11, chapter_13). This has no native Odoo CRM equivalent. FlitStack maps it to x_chapter_type as a selection field so Odoo stage rules can be configured per bankruptcy type after migration for reporting.

NextChapter case notes migrate as mail.message records on the Odoo lead with create_date matching the original note timestamp and create_uid set to the matched Odoo user. Author information is preserved in the message body. This maintains the case's chronological narrative in Odoo's chatter.

NextChapter tracks flat fees, court costs, and payment status on the case. Odoo CRM has no billing module in its base CRM app. FlitStack preserves all financial fields as x_ custom fields on the lead for reference. Firms needing full accounting must activate Odoo Accounting separately post-migration.