Migrate from Jubilee to Odoo CRM

Jubilee client records map directly to Odoo res.partner. The partner record holds name, email, phone, address, and company type (individual vs. organization). Client status (active, inactive) becomes a custom selection field on the partner if needed — Odoo partner records do not have a native status field.

Jubilee email maps to partner email. Odoo validates email format on insert and rejects malformed addresses. Duplicate email detection flags existing partners so the migration does not create duplicate contact records when the same attorney appears across multiple cases. Unmatched email formats are logged for pre‑migration correction.

Phone and mobile phone map to the partner phone field. Odoo stores phone as a Char field, accepting free‑form numbers. If Jubilee stores separate mobile and work phone fields, both insert into the same Odoo phone field, with a label annotation indicating type. Phone numbers are normalized to a consistent format before insert to avoid validation errors.

Jubilee street, city, state, zip, country map to Odoo partner address fields (street, city, state_id, zip, country_id). State maps as a many2one to res.country.state — the state ID must resolve to an existing Odoo state record. Country maps as many2one to res.country.

Jubilee client types (individual, corporation, LLC, partnership) have no direct Odoo equivalent. We create x_client_type as a selection field on res.partner and map each Jubilee value to the matching selection option. If Jubilee contains a type not defined in Odoo, we flag it for pre‑migration review and store the raw value in a Char fallback field.

Jubilee's assigned attorney field maps as a many2one custom field (x_attorney_id) on crm.lead pointing to res.partner. The attorney partner record must exist first — we resolve by email match against Odoo users and create a minimal partner record for unmatched attorneys before opportunity insert.

Each Jubilee case record maps to one Odoo crm.lead in opportunity state. The lead stores case name, amount (debt amount or fee), stage, expected close date, and all custom bankruptcy fields. Odoo uses crm.lead for both lead and opportunity — the convert_lead opportunity action handles the split if the firm later distinguishes pre-filing leads from active cases.

Jubilee case number (e.g., 23‑bk‑12345) has no native Odoo equivalent. We create x_case_number as a Char field on crm.lead and index it for fast lookup by case number after migration. Court docket integrations reference this field directly, and we preserve the original case number format to avoid re‑keying errors.

Chapter 7, 11, 13, and 15 values from Jubilee map to selection field x_bankruptcy_chapter on crm.lead. Value mapping ensures case-insensitive match against Odoo selection options. Chapter type drives Odoo stage pipeline creation — each chapter may warrant a separate Odoo sales team and stage set.

Jubilee status values (Pending, Filed, Discharged, Dismissed, Reopened) map to Odoo stage_id records on crm.lead. We create one Odoo stage per Jubilee status value before migration. For reporting continuity we also store the original Jubilee status string in x_case_status__c as a read-only custom field.

Jubilee trustee name maps to a partner record (or x_trustee_name Char field on crm.lead if no Odoo partner exists). Trustee partners are created with type 'company' and stored in x_trustee_id as a many2one on crm.lead. Duplicate trustee names are de-duplicated before insert.

Court jurisdiction string from Jubilee (e.g., 'Northern District of California') becomes a Char field x_court_district on crm.lead. If Jubilee stores court as a structured object with name and division sub-fields, we concatenate into the Char field or create separate x_court_name and x_court_division fields.

Jubilee remaining_balance decimal maps to Odoo x_remaining_balance as a Monetary field on crm.lead, automatically respecting the company's default currency (USD unless overridden). The field stores the outstanding debt figure for case‑disposition reporting, and any null balances are preserved as zero rather than omitted, ensuring consistent reporting across all migrated cases.

Jubilee activity entries (date, type, note body, author) map to Odoo mail.message records linked to crm.lead. Each message stores author as res.partner, body as HTML, and date as mail.message create_date. Odoo's chatter widget on the opportunity form displays the full case activity history in chronological order.

Jubilee file attachments (petitions, schedules, orders) re-upload to Odoo ir.attachment linked to crm.lead via res_model='crm.lead' and res_id=crm.lead_id. Files retain original filenames and (if readable from source) original create dates stored in ir.attachment create_date. Large files follow Odoo's file storage configuration.

Jubilee workflow definitions (deadline triggers, status-change notifications, filing reminders) do not migrate. We export workflow definitions as a structured JSON rebuild reference and provide an Odoo Studio setup guide so your team can recreate triggers using Odoo Automated Actions and Server Actions. Third-party e-filing integrations require separate API configuration.