Migrate from OneAdvanced Legal to Odoo CRM

Custom matter properties require pre-creation in Odoo before migration data can land

OneAdvanced Legal stores legal-specific metadata (matter_type, court_jurisdiction, legal_aid_reference, case_reference_number, opposing_counsel, SLA_deadline) as matter-level custom properties. Odoo CRM has no native fields for these values — crm.lead supports only stage_id, priority, tag_ids, and out-of-the-box fields. FlitStack AI delivers a field-creation specification as part of the migration plan listing each custom field, its Odoo field type (Char, Selection, Date, etc.), and the options list for Selection fields. Your Odoo admin (or our team) must create these fields in Settings > Technical > Models before the migration run commits records. If fields are missing at run time, migration pauses and requests creation — this is the most common cause of a blocked migration on the OneAdvanced-to-Odoo path.

Time entries carry relational context that cannot map directly to any Odoo CRM field

OneAdvanced Legal time entries form a three-way relational chain: they belong to a matter, carry an hourly rate or fixed fee, and are consumed by a billing run. Odoo CRM (crm.lead) has no billable-time model — the Odoo Timesheet app handles time tracking but that is a separate installation concern. FlitStack AI resolves this by appending each time entry as a formatted mail.message on the linked opportunity, containing date, duration, narrative, and rate as text. The full billing context is preserved for your team to action in Odoo Sales or to import into Odoo Timesheet post-migration. If your migration requires a direct timesheet table, a custom Odoo module is needed — FlitStack AI surfaces this as a post-migration step.

Matter-routing workflows and SLA timers do not migrate — legal automation must be rebuilt

OneAdvanced Legal configures matter-routing rules (which fee-earner receives a new matter based on practice area or client), automated billing posting rules, and SLA deadline tracking as platform-level workflow settings. Odoo CRM uses studio-based automation rules and server actions on crm.lead to achieve similar routing and escalation behaviour, but there is no automated translation between the two rule formats. FlitStack AI exports the OneAdvanced workflow definitions as a structured JSON document so your Odoo administrator can rebuild the logic as Odoo automation rules. The legal team should audit which workflows are business-critical and treat them as a post-migration configuration project with a separate scope.

MatterContact parties per matter need Many2many linking that Odoo does not provide natively

OneAdvanced Legal stores multiple parties per matter — opposing counsel, expert witnesses, opposing parties — as sub-records. Odoo CRM links contacts to opportunities only through the standard Opportunity Contact Role mechanism, which is designed for sales contact roles (Champion, Economic Buyer), not legal party types. FlitStack AI creates a custom Many2many field (Matter_Parties__ids) on crm.lead pointing to res.partner, enabling the migration to carry all party records and associate them with the opportunity. This custom field must be pre-created in Odoo alongside the other legal metadata fields before the migration run.

OneAdvanced Legal has no documented bulk-export API — data retrieval relies on CSV export and scoped REST

Unlike Salesforce or HubSpot, OneAdvanced Legal does not publish a public bulk API endpoint for exporting all objects in a single authenticated call. The primary extraction path is a CSV export from the OneAdvanced interface and a scoped REST endpoint for supplemental record types. FlitStack AI parses the CSV export, normalises field names, and resolves relational links (matter-to-client, time-entry-to-matter) during a pre-migration staging phase. The scoped REST endpoint is used to backfill any fields not present in the CSV export. If the CSV export is incomplete or missing required columns, FlitStack AI flags the gap and requests a revised export before proceeding.