Migrate from Leadforce CRM to Odoo CRM

Leadforce Lead records migrate to Odoo crm.lead. We apply a split rule based on Leadforce lead status: unqualified leads (new, contacted) map to Odoo Lead with type='lead'; qualified leads with monetary deal values map to Odoo Opportunity with type='opportunity'. Embedded company fields from Leadforce (company_name, industry, website) extract into a separate res.partner record flagged as is_company=True and linked via partner_id on the Odoo Lead.

Leadforce Deals map directly to Odoo crm.lead with type='opportunity'. The Leadforce dealstage maps to Odoo stage_id within the assigned crm.team. Deal monetary value maps to Odoo planned_revenue. The Leadforce deal owner resolves to an Odoo res.users record by email match and becomes user_id on the Opportunity.

Leadforce Activity records (calls, emails, meetings) migrate to Odoo mail.message with msg_type='email', 'comment', or 'notification' based on activity type. Chronological ordering preserves through create_date set to the original Leadforce activity timestamp. Author attribution resolves via email match to res.users. The related crm.lead id populates res_id for timeline display.

Leadforce Notes migrate to Odoo mail.message with message_type='notification' and subtype='note' for internal annotation display. Body content migrates as HTML with attachments preserved via ir.attachment records linked via res_model='crm.lead' and res_id pointing to the target opportunity.

Leadforce file attachments extract from exports as binary or URL references and re-attach to the corresponding Odoo crm.lead via ir.attachment records. We map the Leadforce attachment context (attached to Lead or Deal) to the correct res_model ('crm.lead') and res_id before upload via Odoo's /web/binary/attachment API.

Leadforce Proposals migrate to Odoo sale.order as draft Quotation records. Line items (product, quantity, price) map to sale.order.line with product_id resolved via sku or product name matching against Odoo product.product. The linked Deal reference becomes the sale.order's origin field pointing back to the Opportunity.

Leadforce Invoice records migrate to Odoo account.move with move_type='out_invoice' for customer invoices. Payment status from Leadforce maps to Odoo payment_state field. Line items map to account.move.line with account_id resolved from the customer's Odoo partner properties.

Leadforce does not use a separate Companies object; company data lives in Lead records. We extract unique company_name values during the transform phase, deduplicate by domain, and create res.partner records with is_company=True. The resulting partner_id links back to the originating Lead or Deal records in Odoo, establishing the Account-Contact hierarchy that Odoo's CRM expects.

Leadforce pipeline stage names and order migrate as Odoo crm.stage records within the target crm.team. Stage probability percentages map to Odoo stage probability field. We create stages before Opportunity import so stage_id references resolve at insert time.

Leadforce Owner assignments resolve by email match against Odoo res.users. Any Owner without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision before Opportunity import continues. Inactive Leadforce users map to Odoo users with active=False.

Leadforce custom fields on Leads and Deals require manual discovery via screen-share walkthrough since no API schema documentation exists. We document each custom field's name, data type, and options, then create corresponding Odoo custom fields via the Settings > Technical > Custom Fields interface before data import. Selection and multiselect fields map to Odoo selection and many2one fields respectively.

Leadforce auto-triggers and workflow rules do not migrate as executable code. We audit every active trigger (object, event, condition, action) during the discovery phase and document it in a Server Action specification sheet with the equivalent Odoo ir.actions.server model, trigger domain, and action steps. The customer's admin rebuilds these in Odoo Studio or via Python module development post-migration.