Migrate from CosmoLex to Odoo CRM

CosmoLex matter hierarchy has no native Odoo CRM equivalent

CosmoLex structures its entire data model around the Client–Matter relationship: matters are first-class records with their own billing ledgers, notes, tasks, calendar events, and custom fields. Odoo CRM natively models leads and opportunities as crm.lead records attached to res.partner partner records, but the matter concept — a client sub-record with its own lifecycle and billing context — requires deliberate design. We map matters to crm.lead but cannot preserve the full matter-billing relationship without creating custom fields (x_billing_method, x_case_number, x_court) on the lead. Firms with complex matter hierarchies may need to map to project.project for deeper matter-level tracking, which requires Odoo Project to be installed and configured.

Trust accounting and IOLTA ledger data cannot migrate to standard Odoo

CosmoLex includes built-in trust accounting with per-matter IOLTA ledger entries, operating account balances, and trust activity history. Odoo ERP has no native trust accounting or IOLTA construct — it handles client funds via the accounting module's journal entries and reconciliation, but not on a per-matter basis. FlitStack cannot create Odoo trust accounts that mirror CosmoLex's IOLTA behavior because that model does not exist in Odoo's standard schema. We export trust account balances as reference data for your Odoo accounting team to set up manually, and we flag every trust transaction in the migration plan. If your firm requires strict IOLTA compliance, budget additional accounting setup time in Odoo or consider a legal-specific Odoo community module for trust management.

CosmoLex billing methods require Odoo custom field setup before migration

CosmoLex records billing method (Hourly, Flat Fee, Contingency) as a property on each matter. Odoo CRM has no native field for legal billing method on crm.lead. Before any matter data is imported, we create a custom selection field (x_billing_method) on crm.lead via Odoo Settings > Custom Fields. This field must exist in Odoo before the migration run because Odoo enforces field-type constraints during import. If your firm uses multiple billing methods per matter or nested fee arrangements, each arrangement may require separate Odoo product configurations (timesheet products for hourly, sale order lines with fixed price for flat fee), which adds to the planning scope.

Odoo API access requires Custom Plan for external integrations

Odoo's external XML-RPC API is free to use for all customers on the Custom Plan ($37.40 per user per month annually). Customers on the Standard Plan ($24.90 per user per month) do not have API access — the API page in Odoo returns an error for Standard Plan users. If your CosmoLex migration uses Odoo's API for data import (rather than CSV import), your Odoo instance must be on the Custom Plan or higher. FlitStack validates API connectivity during scoping and will use CSV import as a fallback if API access is unavailable, which may affect the speed and reliability of the migration run.

Matter-level document attachments require separate handling

CosmoLex stores documents and files linked to matters — client agreements, court filings, correspondence — in its own document management system. Odoo CRM's document attachment model (ir.attachment records linked to crm.lead via res_model/res_id) accepts file uploads, but the migration pipeline does not automatically re-upload CosmoLex's document library. Files must be exported from CosmoLex separately and uploaded to Odoo manually or via a document migration step scoped as an add-on. If your firm has a large document archive, document migration adds scope and cost that is scoped separately from the data migration.