Migrate from MerusCase to Odoo CRM

MerusCase cases map to Odoo CRM opportunities. The case number becomes opportunity name with the case type appended. Original create date and last-modified date preserve as custom datetime fields since Odoo sets CreateDate at migration time. Case status maps to Odoo CRM stage_id via value_mapping per case type.

MerusCase party contacts map to Odoo res.partner records. The party's role in the case (plaintiff, defendant, opposing counsel) migrates as partner tags and a custom selection field on the partner record. Primary contact email, phone, and address fields map directly to Odoo partner fields.

Insurance carriers and employer entities from MerusCase map to res.partner records with company_type set to 'company'. The carrier's claims address and contact name become Odoo partner address and contact fields. Carrier-specific claim limits or policy references store as custom fields on the partner.

MerusCase activities attached to a case migrate as Odoo CRM activities linked to the crm.lead. Call activities create crm.activity records with activity_type_id set to Phone Call. Emails create mail.message records threaded to the opportunity. Original timestamps and staff owner IDs preserve via custom datetime fields and user email matching.

MerusCase custom fields create equivalent custom fields in Odoo CRM via ir.model.fields. Date types use ttype=date, Currency uses ttype=monetary (linked to res.currency), Text uses ttype=text, Numeric uses ttype=float or integer, Yes/No uses ttype=boolean. The custom field is created on crm.lead before migration; field labels preserve the MerusCase field name.

MerusCase ledger entries with task_code, activity_code, and expense_code map to a combination of Odoo CRM custom fields on the opportunity and optionally account.move.line records if Odoo Accounting is active. Damages and settlement amounts store as monetary custom fields on the crm.lead for reporting continuity.

MerusCase case types (Workers' Comp, Personal Injury, Criminal, Employment) map to Odoo CRM pipeline stages or custom tags on the opportunity. A firm running Workers' Comp cases and Personal Injury cases in separate pipelines gets separate Odoo CRM sales teams and stage sets per case type.

MerusCase documents attached to cases (PDFs, scanned filings, medical records) are re‑uploaded to Odoo CRM as ir.attachment records linked to the corresponding crm.lead using the original case number as the matching key. File size limits apply per Odoo configuration; for archives exceeding typical thresholds, FlitStack can leverage Odoo’s external storage options or split uploads into manageable chunks. Original document names and upload timestamps are preserved in the attachment metadata for auditability.

MerusCase staff members (attorneys, paralegals, admins) resolve to Odoo res.users by matching the email address stored in MerusCase against existing Odoo user accounts. Any staff member without a matching email is flagged in a pre‑migration report, allowing your admin to either create the Odoo user, assign a designated fallback user, or place the staff records in a queue for later mapping. This ensures every case and activity in Odoo has a valid owner from the start.

MerusCase Workflows triggered by activity tags or description text do not transfer to Odoo. They must be rebuilt using Odoo CRM's Automate menu or Odoo Studio. FlitStack exports the workflow definitions as a JSON reference file for your Odoo admin to use during rebuild.

MerusCase special handling flags and settlement details map to custom fields on the Odoo opportunity. Settlement status (open, settled, closed) becomes a selection field; settlement amount and payment date store as monetary and date custom fields for reporting against the opportunity.

MerusCase UTBMS L-Codes (task), A-Codes (activity), and E-Codes (expense) require mapping to Odoo products or accounts. If Odoo Timesheet or Expense module is active, we map task codes to analytic accounts; otherwise they store as custom selection fields on the opportunity for billing reference.