Migrate from Legal Case Tracker to Odoo CRM

Legal Case Tracker matters map to crm.lead for new-intake cases and crm.opportunity for active matters in the pipeline. Odoo requires a crm.lead to be converted to crm.opportunity via the Convert to Opportunity wizard, which creates the opportunity and links it to a res.partner contact. The mapping plan defines which Legal Case Tracker status values route to lead versus opportunity.

Client records in Legal Case Tracker map directly to res.partner in Odoo. Odoo res.partner serves both the CRM and the accounting modules, so contacts created here are immediately available for invoicing and purchase workflows. Legal Case Tracker contact roles (Attorney, Client, Opposing Counsel) map to res.partner categories or custom tags in Odoo.

Document files attached to Legal Case Tracker matters are downloaded and re-uploaded as ir.attachment records in Odoo. The res_model field is set to crm.lead or crm.opportunity depending on the target object, and res_id references the migrated record's integer ID. Files are stored in Odoo's filestore directory; large documents (over 25MB) may require Odoo Document module or external storage configuration.

Billable hours logged against Legal Case Tracker matters map to account.analytic.line records when Odoo Timesheet module is active. Each time entry becomes a timesheet line linked to the migrated crm.opportunity via the project_id and task_id context. Non-billable entries map to internal notes or tasks. Original date, duration, description, and user reference are preserved.

Expenses incurred against Legal Case Tracker matters map to hr.expense records linked to the corresponding opportunity. Vendor name, amount, date, and description transfer directly. Odoo Expense approval workflow must be configured separately to route expenses through your firm's approval chain.

Legal Case Tracker status labels (Open, Pending Review, Closed Won, Closed Lost) map value-by-value to crm.stage records. Each stage in Odoo has a sequence integer and a probability percentage that applies to the opportunity's forecast. Stage-entered timestamps from Legal Case Tracker are preserved as custom datetime fields on the opportunity.

Legal Case Tracker custom fields on matters map to Odoo custom fields created via Settings > Technical > Custom Fields. Field type determines the Odoo field_type: short text maps to Char, long text to Text, numbers to Integer or Float, dates to Date. A migration-time script creates each custom field on the crm.lead or crm.opportunity model before data loads.

Legal Case Tracker picklist custom fields with defined value options map to Odoo Selection fields. The selection options are encoded as a Python list of tuples in the field definition: [('value1','Label 1'),('value2','Label 2')]. If a picklist value has no Odoo counterpart, it is preserved as-is and a note is added to the migration plan for manual review.

Legal Case Tracker lookup fields referencing contacts map to Odoo Many2one fields pointing to res.partner. The field definition requires the comodel_name set to 'res.partner'. During migration, the contact ID from Legal Case Tracker is translated to the corresponding res.partner ID generated in Odoo.

Legal Case Tracker practice-area tags and matter categories merge into Odoo's tag system (crm.tag) and sales team assignments (crm.team). Multiple Legal Case Tracker categories on one matter become multiple crm.tag records on the opportunity. Team assignment maps based on attorney owner in Legal Case Tracker—each unique owner becomes a crm.team or is assigned as the opportunity's user_id.

Legal Case Tracker invoice line items tied to matters have no Odoo CRM equivalent. These records must be rebuilt using Odoo Accounting (account.move) once the CRM migration is complete. FlitStack preserves the invoice data as reference records in a holding table so your accounting team can reconstruct invoices in Odoo.

Legal Case Tracker users (attorneys, paralegals, staff) map to res.users records in Odoo. User matching is done by email address. If a Legal Case Tracker user has no corresponding Odoo user, they are flagged in the migration plan—their cases are assigned to a fallback user (typically the admin) and their name is stored in a custom x_original_owner field for reference.