Migrate from Leaf360 to Odoo CRM

Leaf360 contacts map directly to Odoo res.partner records. The crm.lead record will reference the same partner ID once the opportunity is created. Email, phone, and address fields map 1:1. Leaf360 contacts without a company association land as individual partners with company_type = 'person'.

Leaf360 company records map to res.partner with company_type = 'company'. The partner_id of the associated Leaf360 contact is set to the newly created company partner record. Parent-company hierarchies in Leaf360 map to the child_ids relationship on the parent res.partner record in Odoo.

Leaf360 deals map to Odoo crm.lead records. The is_opportunity boolean is set to True for deals that represent active mortgage applications. Pipeline name in Leaf360 becomes the name field on the crm.lead, and pipeline stage names map to existing or newly created crm.stage records within the assigned crm.team.

Each Leaf360 pipeline stage (Pre-Qualified, Submitted, Underwriting, Rate Locked, Closed) maps to a named crm.stage record within the appropriate crm.team. Stage sequence and probability values are set per stage in Odoo. If the target Odoo installation already has stages, we apply a value-mapping table; new stages are created during schema setup.

Leaf360's referral-source field has no native Odoo CRM equivalent. We create a custom Char field (x_referral_source) on crm.lead. If the referral is a named partner in Leaf360, we attempt to match it to an existing res.partner record in Odoo; unmatched referral names are stored as plain text in x_referral_source.

Named referral partners from Leaf360 are created as res.partner records with a custom tag or category (x_partner_type = 'referral'). The crm.lead's x_referral_source field references the partner by name. This allows Odoo users to click through from the opportunity to the referral partner's full record.

Leaf360 logged calls, emails, and notes are migrated as mail.message records attached to the corresponding crm.lead using res_model='crm.lead' and res_id set to the lead's ID. The subtype_id field records the interaction type (call, email, or note). Both the original created_at timestamp and the owner_id (author) from Leaf360 are retained in the message record.

Leaf360 file attachments are fetched via the platform's file API, then stored as ir.attachment records in Odoo, with res_model set to 'crm.lead' and res_id referencing the destination lead ID. The original filename and content type are preserved. Odoo's filestore enforces a default 25 MB per‑file limit; any attachment exceeding this threshold is flagged for manual handling and its source URL is recorded in a custom Char field (x_source_file_url) for later retrieval.

Leaf360 owner_id values are resolved by email match against res.users in the destination Odoo tenant. Unmatched owners are flagged before migration; your Odoo admin either creates matching user accounts or assigns those records to a fallback owner (typically the admin user). No record lands without a valid Odoo user_id.

Leaf360 custom fields returned by /api/v2/custom-fields are enumerated and mapped to Odoo ir.model.field records. Each field is created on crm.lead (or res.partner for contact-level properties) with the matching field type — Char, Selection, Float, Date, Datetime, Many2one, etc. Fields are exposed in the Odoo Studio UI after migration so your admin can arrange them on the form view.

Leaf360 lifecycle-stage values beyond simple Open/Closed are mapped to corresponding crm.stage names in Odoo, using a value‑mapping table that respects the order and probability defined for each stage. To preserve the moment of a stage change, a custom Datetime field called x_lifecycle_changed_date is added to crm.lead, storing the timestamp of the most recent transition captured from Leaf360. This enables audit trails and historical reporting without relying on Odoo's default create_date.