Migrate from LegalE to Odoo CRM

Legale contacts map to Odoo res.partner records with type='contact'. The partner_id on Odoo opportunities references these records. Legale contacts without a company association get a standalone partner record; those linked to a Legale company use the mapped company partner as parent_id.

Legale companies map to Odoo res.partner records with type='company'. The parent_id relationship is set for child companies. Odoo distinguishes companies from contacts via the type field alone — Legale's separate Company object collapses into the same partner table with a different type value.

Legale deals map to Odoo crm.lead records where type='opportunity'. The name field maps to opportunity name, amount to expected_revenue, and close_date to date_deadline. The Legale stage value maps to a specific Odoo crm.stage via the stage_id lookup scoped to the target sales team.

Each Legale deal stage is mapped value-by-value to an Odoo crm.stage record within the target crm.team. Odoo stages carry a sequence integer and probability percentage that are applied from the Legale stage definition. Teams with multiple Legale pipelines map to multiple Odoo crm.team records, each with its own stage sequence.

Legale owner IDs are resolved by email match against Odoo res.users records. The crm.lead owner_id field references the matched res.users id. Legale owners without a corresponding Odoo user are flagged before migration — your admin either creates the Odoo user first or assigns those records to a fallback owner.

Legale logged calls and emails map to Odoo mail.message records with model='crm.lead' and res_id pointing to the opportunity. Meetings map to calendar.event records with linked crm.lead. Notes map to mail.message with subtype='comment'. All records preserve the original Legale timestamp, body content, and author user.

Legale custom properties are exported as field definitions and recreated as custom fields on the target Odoo model (res.partner for contact properties, crm.lead for deal properties). Pick-list properties in Legale require matching selection fields in Odoo with value-by-value mapping. The field definitions are loaded via Odoo's CSV import or XML data file.

Legale file attachments are re-uploaded as Odoo ir.attachment records with name, db_datas (base64 binary), res_model set to the parent model (res.partner or crm.lead), and res_id pointing to the migrated record ID. Odoo's filestore path is reconstructed on write. Files over 115MB require chunked handling.

Legale deal tags and contact labels map to Odoo crm.tag records via a direct transformation. Tags are created first as crm.tag records in Odoo, then linked to crm.lead records via the tag_ids many2many relationship field. Legale tags with no existing Odoo equivalent are created on the fly during migration using the tag name and stored in the crm.tag model. The migration preserves tag color metadata when available.

Legale workflows, sequences, and email templates have no Odoo equivalent in the migration data — they must be rebuilt manually in Odoo Studio or via the automation framework. FlitStack AI exports Legale workflow definitions as JSON for reference so your Odoo admin can reconstruct them in the correct sequence.