Migrate from Best Case Bankruptcy to Odoo CRM

Best Case client records (debtor name, address, SSN, date of birth) map to Odoo res.partner as the primary contact. FlitStack sets partner_id on each migrated crm.lead. The client's bankruptcy filing date becomes a custom date field on the partner record.

Best Case attorney and staff logins map to Odoo res.users by email address match. Unmatched users are flagged before migration — the firm either creates Odoo accounts first or assigns records to a fallback user. Owner assignment on crm.lead records uses this resolution.

Each Best Case bankruptcy case becomes a single crm.lead record. The case number (e.g., 23-bk-12345) and client name concatenate to form crm.lead.name. The bankruptcy chapter (7, 11, 13, 15) maps to a custom picklist field (Bankruptcy_Chapter__c) on the lead. Case status (pending, filed, discharged, dismissed) becomes the lead stage in Odoo's pipeline.

Each creditor in Best Case splits into two artifacts: a child res.partner record representing the creditor entity, and a structured note block on the crm.lead that preserves debt amount, priority (secured/unsecured/priority), and account number. This preserves creditor data without requiring Odoo to have a native many-to-many creditor relationship.

Best Case debt entries (unsecured, secured, priority) merge into a combination of custom numeric fields on the crm.lead (Total_Unsecured_Debt__c, Total_Secured_Debt__c, Total_Priority_Debt__c) and structured note blocks that list each creditor's individual debt amount and classification. This structure provides attorneys with both aggregate totals for reporting and per-creditor detail for case review in Odoo.

Best Case exemption analyzer results (homestead, wildcard, vehicle, retirement account exemptions) have no Odoo native equivalent. FlitStack creates custom fields on crm.lead for each exemption category the firm uses, preserving the claimed amount and applicable statute reference. This requires the firm to specify which exemption categories are active in their jurisdiction before migration.

Best Case means-test calculator output (median family income comparison, chapter 7 eligibility, plan payment amount) migrates as a group of custom fields on crm.lead. FlitStack preserves the test date, result (pass/fail), and applicable form reference (Form 122A-1 or 122C-1) as datetime and text fields.

Best Case filing events (petition filed, 341 meeting scheduled, discharge entered) migrate as Odoo mail.message records attached to the crm.lead. Each message preserves the event date, court name, and filing status — giving attorneys a complete timeline visible within each lead's chatter thread in Odoo.

Best Case file attachments (petitions, schedules, court orders) are downloaded from Best Case's document library and re-uploaded to Odoo's ir.attachment model, linked to the corresponding crm.lead via res_model and res_id. Large files (>25MB) may need to be split or stored externally with a link preserved on the lead.

Best Case's client portal access log (when the client last logged in, which documents they viewed) has no Odoo CRM equivalent. FlitStack preserves the last-accessed timestamp as a custom datetime field on res.partner for reference, but the portal itself is not rebuilt — Odoo's portal module would need to be configured separately.

If Best Case stores retainer account balances or fee invoices, those records have no direct Odoo CRM equivalent. FlitStack can export them as reference data, but they must be re-created in Odoo Accounting (an Odoo module separate from CRM) if the firm uses Odoo's billing capabilities.