Migrate from The Attorney Case File to Odoo CRM

Each The Attorney Case File matter becomes a crm.lead record with type='opportunity'. The crm.lead.name field holds the matter title, and stage is set based on the case-status mapping defined during discovery. Original case creation date is preserved as a custom datetime field since Odoo sets crm.lead.create_date at migration time.

Client records from The Attorney Case File map directly to res.partner. Individual attorneys and opposing counsel each become separate res.partner records. The client-type flag (e.g., plaintiff, defendant, opposing counsel) is stored as a custom selection field since Odoo's native partner category model is used for tagging rather than party role classification.

When The Attorney Case File stores a firm or organization name as a separate entity from individual contacts, it maps to res.partner with company_type='company'. Individual contacts at the firm become child res.partner records with parent_id pointing to the firm, mirroring Odoo's standard company-contact structure.

Every document linked to a case in The Attorney Case File re-uploads as an ir.attachment record with res_model='crm.lead' and res_id set to the migrated crm.lead ID. The original file name and MIME type are preserved; Odoo's ir_attachment.store_file field routes storage to PostgreSQL or the filestore directory per your Odoo configuration.

Time entries linked to matters map to account.analytic.line records with product_id set to the migrated billing-rate product. Odoo requires the Timesheet app or a timesheet-enabled project to be active; if neither exists, time entries migrate as notes on the crm.lead with a custom description field carrying the original hours and narrative.

Fixed billing rates and fee schedules stored in The Attorney Case File become product.template records in Odoo's Product app. Each rate becomes a product with a list_price set to the billing amount, and the rate name maps to product.name. Hourly rates use uom_id='Hour'; flat fees use uom_id='Unit'.

Each distinct case-status value in The Attorney Case File is mapped to a corresponding crm.stage record in Odoo. Stage names (e.g., 'Active Litigation', 'Discovery', 'Settlement Negotiations') are created as new stages in the default Odoo pipeline or a dedicated legal pipeline. Probability values are assigned per stage to support Odoo's forecast reporting.

Scheduled court dates and attorney calendar events from The Attorney Case File map to calendar.event records in Odoo, with the crm.lead linked via the res_id field. Start and stop datetime values are preserved; reminder settings are mapped to calendar.alarm records. If no calendar module is active in Odoo, events are stored as notes on the crm.lead.

Any custom properties defined on The Attorney Case File matters — such as statute of limitations dates, venue court names, insurance carrier references, or judicial assignment data — require new ir.model.fields entries on the crm.lead model before migration. FlitStack generates the field definition SQL and applies it during the schema-setup phase.

Client-specific custom fields from The Attorney Case File (e.g., bar number, referral source, conflict-check status) are added to res.partner via ir.model.fields. Odoo restricts field name length to 50 characters and requires snake_case naming; source field names are normalized during the field creation phase.

The Attorney Case File may store opposing counsel as a separate contact record. In Odoo, these contacts are merged into res.partner with the party role recorded in a custom selection field (Case_Party_Role__c) rather than as separate object types. This preserves the relationship without inflating contact counts.

The Attorney Case File owner or responsible attorney on a matter is resolved by email match against res.users in Odoo. If no matching Odoo user exists, the crm.lead.owner_id is set to a fallback attorney designated by the firm, and the original owner name is preserved in a custom field for reconciliation.