Migrate from Legl to Odoo CRM

Odoo API throughput is constrained by per-user concurrent call limits

Odoo's XML-RPC interface does not publish a public rate ceiling, but in practice the server enforces per-user concurrent call limits that throttle migration throughput. Legl's API allows 3,600 requests/hour (sustained) with a burst of 120 requests/minute. Extracting data from Legl is fast; loading into Odoo is the bottleneck. We batch Odoo writes into chunks of 50 records per XML-RPC call and pace uploads to avoid Odoo worker queue saturation. Large migrations (50,000+ records) may require multiple Odoo user sessions or a direct PostgreSQL insertion strategy for the initial load, followed by XML-RPC validation passes.

Legl engage requests and risk assessments require custom field creation in Odoo before data lands

Odoo CRM has no native objects for AML compliance tracking or KYC risk assessment — these are Legl-specific concepts with no crm.lead or res.partner field equivalent. Before migration runs, your Odoo admin (or our team via Odoo Studio) must create x_engage_status, x_risk_type, x_risk_status, and their companion datetime and reference fields on res.partner. If your firm tracks multiple engage requests or risk assessments per business entity, a separate LeglEngageRequest model in Odoo (via Odoo Studio or custom module) is needed — one-to-many relation not handled by simple custom fields. We provide the exact field definitions and Odoo Studio export file as part of the pre-migration schema setup plan.

Lead-to-partner conversion in Odoo drops unmapped custom fields unless inheritance is adjusted

When an Odoo crm.lead is converted to an Opportunity, Odoo calls _convert_opportunity which creates a res.partner (if the lead has no partner_id) and optionally links the lead to that partner. Custom fields on the crm.lead record — including our x_engage_status and x_risk_type fields — do not automatically propagate to the newly created partner unless _convert_opportunity is extended in a custom module. Since Legl compliance data lives on res.partner (not on crm.lead), any leads converted post-migration will lose their Legl compliance context. We mitigate this by migrating Legl businesses and contacts directly to res.partner as company/individual partners, bypassing crm.lead for compliance-heavy records. Only Legl records that represent active sales opportunities are created as crm.lead.

Legl's N:1 contact-to-business model requires primary-company designation in Odoo

Legl allows a contact to be associated with multiple businesses (primary_business_id plus secondary associations). Odoo's res.partner model uses a single parent_id to designate the company for an individual contact. Secondary business associations collapse into child_ids on the secondary company partner, which can cause confusion in Odoo's contact tree view. We migrate the Legl primary_business_id as the Odoo parent_id, flag secondary associations in x_secondary_business_ids as a custom char field storing a semicolon-separated list of Legl business IDs, and recommend that your Odoo admin rebuilds multi-company contact associations using Odoo's Contacts menu and the partner's Contact Information tab post-migration.

Legl workflow definitions cannot migrate — Odoo automation rules run at object level

Legl workflows are organization-level constructs with configurable steps, assignee rules, stage transitions, and conditional branching that span multiple entity types (business, contact, engage request). Odoo automation rules (Automated Actions, Server Actions, CRM Sales Team automations) operate on individual Odoo models — there is no Odoo-native equivalent for cross-object, multi-step workflow orchestration at the Legl level. We export your Legl workflow definitions as structured JSON including step sequence, assignee logic, and conditional rules, then deliver an Odoo Studio rebuild guide mapping each Legl step to the corresponding Odoo automated action trigger on crm.lead, res.partner, or a custom engage-request model. Rebuild effort depends on Legl workflow complexity — single-step workflows take under an hour; complex multi-step onboarding flows may require two to three days of Odoo Studio configuration.