Migrate from FactBox to Odoo CRM

Each FactBox case maps to a single Odoo crm.lead record. The case name becomes the lead name, case status maps to lead stage via value mapping, and legal metadata (court, judge, opposing counsel, case type) migrate as Odoo Enterprise custom fields on the lead. Parent-child case hierarchy maps to the crm.lead parent_id self-referential field.

Each FactBox fact becomes either a scheduled Odoo mail.activity (with a due date) or a mail.message note on the parent crm.lead. The fact content maps to the activity's note field. Original create and update timestamps are preserved as custom datetime fields on the activity record for factual chronology continuity.

FactBox documents and exhibits download from FactBox's storage and re-upload into Odoo's ir.attachment table. Each attachment sets res_model='crm.lead' and res_id pointing to the mapped case's lead ID. Exhibit numbers and document-type metadata map to ir.attachment custom fields (x_exhibit_number, x_document_type) on the attachment record.

Each FactBox witness record creates a res.partner in Odoo with type='contact' and a custom field x_contact_role='Witness'. The witness name maps to partner name, contact details map to standard address and phone fields. Testimony text maps to a custom long-text field on the partner for reference — linked to the parent case via a many2one on the crm.lead.

Evidence items with text content merge into a custom Evidence_Summary__c long-text field on the parent crm.lead. Evidence items with file attachments map to ir.attachment records linked to the parent crm.lead. Exhibit tag and evidence type values map via value_mapping to a custom pick-list on the lead.

FactBox issues and legal claims map to Odoo CRM tags (crm.tag) created dynamically from source issue names, linked to the crm.lead via crm.lead.resolver.tag_ids. Longer issue narratives migrate as mail.message notes on the lead for auditability. We also map each issue's status to the tag's active flag, preserving its open or closed state in Odoo.

FactBox timeline entries — hearing dates, filing dates, deposition dates — map directly to Odoo's mail.message records on the crm.lead. Each message preserves the original event date as message_date and adds a custom field x_event_type to distinguish hearing, filing, and deposition events.

FactBox owner resolved by email match against Odoo's res.users table. Unmatched owners flagged before migration; records assigned to a fallback Odoo user or held for admin assignment. FactBox does not have a separate user-object table — owner ID maps via the user's email in the export.

FactBox custom properties at the case level (e.g., x_case_number, x_case_type, x_judge, x_opposing_counsel, x_court) require Odoo Enterprise custom fields on crm.lead. Odoo Community does not support Studio-based field creation — Enterprise plan or direct PostgreSQL field addition is required for these mappings.

Witness-specific and fact-specific custom properties migrate as custom fields on the respective target objects. These require Odoo Enterprise custom field support on res.partner and mail.activity models. We surface all required custom fields in the pre-migration schema plan before data moves.

All FactBox file attachments — correspondence, court filings, discovery documents — download and re-upload to Odoo's ir.attachment table. Each record stores the original filename, file size, and MIME type. The migration tool sets res_model='crm.lead' and res_id to the mapped case lead ID, preserving the link to the originating case.