Migrate from LegalEdge to Odoo CRM

LegalEdge matters map directly to Odoo crm.lead records. The matter name becomes the lead name, status maps to stage values, and billing metadata is stored in custom fields on the lead. Attorney assignments resolve by email match to Odoo user accounts. Court links and case-type labels migrate as custom Char fields.

LegalEdge clients become Odoo res.partner records. The client name maps to the partner name field, email to email, phone to phone, and address components (street, city, state, country) map to Odoo’s address fields using the appropriate relational IDs. Multi‑matter clients retain all linked lead records under the same partner, preserving the relationship across cases.

LegalEdge logged calls migrate as Odoo mail.activity records with activity type set to 'call'. The call subject maps to the activity summary, date maps to the deadline, and duration (in minutes) is stored in a custom Integer field. Call outcome and attorney email are preserved; attorney email resolves to an Odoo user ID for ownership. Each activity is linked to the related res.partner and crm.lead through Odoo's relational fields.

LegalEdge meetings migrate as Odoo mail.activity records with activity type 'meeting'. Meeting title, scheduled date and time, location, and attendees are mapped to Odoo activity fields. The activity is linked to the partner and lead from the originating LegalEdge matter.

LegalEdge case notes migrate as Odoo mail.message records attached to the corresponding crm.lead. The note body text is stored in the message body field using the 'note' subtype. Original creation timestamp and author name are preserved in custom fields (x_note_date and x_note_author) on the message. Any file attachments linked to the note are also migrated and attached to the mail.message record, maintaining context.

Files attached to LegalEdge matters and clients are extracted from LegalEdge storage, renamed with the source matter reference, and uploaded to Odoo's ir.attachment model linked to the corresponding crm.lead or res.partner record. Large files are chunked to stay within Odoo's attachment size limits.

Each LegalEdge custom property on a matter is analyzed by type: text fields become Char, numeric fields become Float or Integer, date fields become Date, and pick-list values become Selection fields on crm.lead. FlitStack creates these fields in Odoo before migration data loads. Property labels are preserved in the field help text.

LegalEdge client-level custom properties migrate to custom fields on res.partner using the same type-mapping logic as matter properties. Custom fields on both partner and lead are created in Odoo Studio or via the data migration script before records are imported.

LegalEdge billable hour entries are aggregated per matter and stored in a custom Float field (Billable_Hours__c) on the crm.lead. Per-entry time logs are preserved as Odoo timesheet records linked to the lead if the Odoo Timesheet app is active; otherwise, summary totals are stored on the lead record.

LegalEdge cost records and invoice numbers are stored in custom Char fields on the Odoo crm.lead: Case_Cost__c and Invoice_Number__c. Full invoice history and line items require the Odoo Accounting app and are handled as a separate accounting migration step after the CRM layer is live.