Migrate from LeadSimple to Odoo CRM

LeadSimple's lead record maps directly to Odoo's crm.lead model. The lead's core properties—name, contact details, address, and property information—translate to corresponding fields on the Odoo record. Odoo crm.lead can represent both a Lead (unqualified) and an Opportunity (qualified). The migration sets type='lead' initially; conversion to opportunity is handled separately in Odoo post-migration. The original LeadSimple record ID is preserved in a custom x_source_system_id field for traceability and delta-run matching.

LeadSimple stores a contact name, email, phone, and address directly on the lead. These fields translate to Odoo's res.partner record — created as a standalone partner record first, then linked to crm.lead via partner_id. The lead-contact relationship is N:1 in Odoo (one partner can have many leads).

LeadSimple's Pipeline name maps to an Odoo crm.team (sales team). Each crm.team in Odoo holds its own set of crm.stage records. If your LeadSimple setup has multiple pipelines with the same stage names, we create one crm.team per pipeline and scoped stage sets to avoid mixing deal records across teams.

LeadSimple Stage Name maps to Odoo crm.stage records within the corresponding crm.team. Stage sequence (order) is preserved via the sequence field. Odoo's stage records include probability and legend attributes that we set based on your LeadSimple stage-status values (Active / Won / Lost).

LeadSimple property type (Single Family, Multi-Family, Commercial, etc.) has no native Odoo equivalent in the CRM module. We create a custom selection field on res.partner named property_type before migration. Value-mapping is required: each LeadSimple property type becomes a matching selection option in the Odoo custom field.

LeadSimple tracks whether a property is Occupied or Vacant at the lead level. We create a custom selection field occupancy_status on res.partner in Odoo to hold this value. The field is optional — records without occupancy data leave the field blank.

LeadSimple Number of Units is an integer stored against the lead's property record. Odoo CRM has no native units field — the concept of multi-unit properties doesn't exist in the standard CRM model. We create a custom integer field number_of_units on res.partner so the property portfolio context stays attached to the contact record. This preserves the property-specific unit count alongside the partner's address and contact information during the migration.

LeadSimple carries both ACV (Annual Contract Value) and Cost as numeric fields. These map to Odoo crm.lead custom fields — annual_contract_value__c and property_cost__c — using the __c suffix convention for custom fields. Odoo's standard Amount field is reserved for opportunity amounts tied to sale orders, so these property-finance fields are kept separate.

LeadSimple tracks where the lead originated (Source) and which referrer sent it. Both map to custom text fields on crm.lead in Odoo. If your LeadSimple uses a fixed list of sources, we can convert these to selection fields for cleaner reporting in Odoo's crm.lead views.

LeadSimple Tag List maps to Odoo's crm.tag model, which links to crm.lead via a many2many tag_ids field. We create any missing tags in Odoo before migration and apply them to the corresponding leads. Tags without a matching Odoo tag are created on the fly during the migration run.

LeadSimple comments on a lead become Odoo mail.message records attached to the crm.lead. Original timestamps and the commenting user are preserved in the message body using Odoo's mail.thread tracking. This keeps the conversation history visible directly in the lead form view.

LeadSimple Process records — conditional task checklists with stages — have no Odoo CRM equivalent. We export the full process definition as a structured JSON file listing each process, its conditional rules, assigned stages, and task instructions. Your Odoo admin uses this as a rebuild reference in Odoo Studio.

LeadSimple Assigned To (owner) is resolved by email match against Odoo res.users. Unmatched owners are flagged before migration — your team either pre-creates the user in Odoo or assigns those records to a fallback sales team. No crm.lead lands without an assigned user or team in Odoo.

LeadSimple Created At maps to crm.lead create_date. Odoo's write_date is updated at migration time, so the original creation timestamp is preserved explicitly via a custom field Original_Create_Date__c if audit continuity is required. Closed At maps to Odoo's date_closed field for leads that reached a Won or Lost stage.