Migrate from InfoTrack to Odoo CRM

InfoTrack parties are named individuals or entities attached to a matter. Each party migrates as a res.partner record. If the party is a company, Odoo stores it as a commercial partner with individual contacts as children. Email, phone, and address fields map directly.

InfoTrack matters are the central case record. They map to Odoo crm.lead as the lead/opportunity record. We preserve the original matter number as a custom field (InfoTrack_Matter_Number__c) and store the Odoo lead as the canonical case record with stage, priority, and responsible user mapped.

A single InfoTrack matter has multiple parties (plaintiff, defendant, attorney contacts). We create one crm.lead per matter and link multiple res.partner records through Odoo's crm.lead.partner_ids many2many field. Each linked partner's role (e.g., opposing counsel) is stored as a custom selection field on the rel table.

InfoTrack stores court-stamped documents and eFiled packets. These migrate as ir_attachment records in Odoo, linked to the corresponding crm.lead via res_id/res_model. Large PDFs are stored in Odoo's filestore directory and remain accessible from the lead's Documents tab. All file metadata such as original filing dates and court codes are preserved as custom Char fields on the ir_attachment record to aid future searches.

InfoTrack logs each court filing event with a date, court, and description. These map to mail.message records on the crm.lead with message_type='notification' so they appear in the lead's chatter but are clearly distinguished from sales activity logs. The notification includes the original event type and court identifier, enabling users to filter court-specific updates separately from general communications.

InfoTrack tracks when documents were served, on whom, and by which process server. We migrate these as mail.message records with a custom field (Service_Date__c, Process_Server__c) so the service history is visible on the crm.lead without cluttering the standard activity timeline.

InfoTrack docket entries (hearing dates, filing deadlines) migrate as Odoo calendar.event records linked to the crm.lead. Original event timestamps and reminders are preserved so Odoo's calendar view reflects the full court schedule. Each calendar.event record also stores the associated court location and case identifier as custom Char fields, ensuring that all scheduling details are immediately visible to attorneys when they open the event.

InfoTrack stores the attorney or staff member assigned to a matter. We resolve by email match against Odoo res.users records. Unmatched users are flagged for your Odoo admin to invite before the migration finalizes. If a match cannot be found, the system records the original InfoTrack user identifier in a custom field on the crm.lead so that manual assignment can occur post-migration without losing the historical attribution.

InfoTrack generates invoices per transaction for client billing. Odoo Accounting (a separate Odoo app) handles invoicing. We preserve InfoTrack invoice metadata as a custom JSON field on the crm.lead for reference; rebuilding invoicing logic in Odoo requires your accountant to configure Odoo Accounting separately.

InfoTrack allows custom fields per matter (e.g., Case Type, Insurance Carrier, Statute of Limitations). We evaluate each custom field and create matching Odoo custom fields on the crm.lead model using Odoo's ir.model.fields API before migration loads data. The field type (Char, Selection, Date, Integer) is inferred from the source data, and any validation rules in InfoTrack are documented for manual recreation in Odoo Studio.

InfoTrack integrations with Clio, LEAP, and Time Matters are connection-level settings with no data stored in InfoTrack itself. These integrations cannot migrate — your Odoo administrator must reconfigure API credentials and webhooks for any third-party systems you continue to use.

InfoTrack does not expose a workflow builder — automations are embedded in its integration layer (e.g., auto-file on court ruling). There are no migration-eligible workflow definitions to export. Odoo automations must be built from scratch using Odoo Studio or server actions after migration.