Migrate from Lexis Affinity to Odoo CRM

Lexis Affinity client records map directly to Odoo res.partner. The partner record carries the original client ID as a custom field for traceability. Multiple contacts per client (attorney, billing contact) create separate res.partner records linked to the primary client partner.

Each Lexis Affinity matter becomes an Odoo crm.lead record. The original matter number is stored in Matter_Number__c (custom Char field) on the lead. Matter status (open, closed, pending) maps to Odoo lead stage values. Multiple matter types (litigation, corporate) may require separate field-mapping profiles per type.

Lexis Affinity matter type codes (e.g., LIT, CORP, REAL) map to Odoo tag records. Tags are applied to the crm.lead for filtering. If Odoo has fewer than 20 tags, the mapping is straightforward; larger type sets require a custom selection field.

Billable time entries migrate as crm.lead activities with type='log_note' when Odoo project module is inactive. When the project module is active, time entries become project.task work records linked to the matter-lead. Each entry preserves the original date, duration, narrative, and attorney attribution.

Lexis Affinity bills map to Odoo account.move records (type='out_invoice') under the accounting module. Bill status (draft, sent, paid) maps to Odoo state values. If the accounting module is not active, bills migrate as custom fields on crm.lead for later conversion. Line items carry description and hours from the originating time entries.

Lexis Affinity trust account balances have no direct Odoo equivalent since legal trust accounting requires a dedicated chart of accounts with trust-specific journal codes. We migrate the last-known balance as Trust_Balance__c (Decimal) on res.partner and flag the record for accounting-side reconciliation before go-live.

Lexis Affinity documents export as file packages (PDF, DOCX, MSG) and re-upload to Odoo as ir.attachment records linked to res.partner or crm.lead via res_model and res_id. Folder hierarchy is lost; we reconstruct folder names as tags on the attachment for navigation. Inline images in notes are downloaded and rehosted as attachment files.

Lexis Affinity calendar entries migrate as Odoo calendar.event records linked to the res.users owner. Start datetime, stop datetime, and description carry over. Attendees (client contacts) are added as calendar.event partners when email addresses resolve to existing res.partner records. When a matching partner record does not exist, the attendee is stored as a display name until the contact is created in Odoo.

Lexis Affinity staff records map to Odoo res.users by email match. Rate-per-hour migrates as Rate_Hourly__c (Decimal) on res.users. Users without matching email are flagged before migration; the firm either creates Odoo accounts first or assigns records to a fallback user.

Lexis Affinity custom matter fields (e.g., Court Name, Opposing Counsel, Case Value) require Odoo custom fields on crm.lead. We create Char, Date, or Selection fields based on the source field type. Multi-value selection fields map to Odoo tags or many2many relation fields depending on the cardinality.

Lexis Affinity workflow rules, matter-stage triggers, and billing automations are not extractable in a form Odoo can import. We export workflow definitions as a JSON spec so your Odoo admin can rebuild them using Odoo Studio or server actions. This export is delivered alongside the migration plan.

Logged client emails and notes in Lexis Affinity migrate as Odoo mail.message records on the crm.lead (internal notes) or as crm.lead activities with type='log_note'. Original timestamps and author user are preserved. Email threading is not reconstructed — each entry lands as a standalone note.