Migrate from Leadfox to Odoo CRM

Leadfox Contacts with Lifecycle Stage of opportunity, customer, evangelist, or other (indicating a qualified buyer) map to Odoo res.partner records attached to an Account (res.partner with is_company=True or parent_id set). Contacts with Lifecycle Stage of subscriber, lead, or marketing qualified lead map to crm.lead. We compute the split using the Leadfox lifecyclestage property at migration time and preserve the original stage in a custom Char field lf_original_lifecycle__c on both crm.lead and res.partner for audit and reporting continuity.

Leadfox companies stored as contact properties (website, industry, employee count) map to Odoo res.partner records with is_company=True. The company domain stored in Leadfox's Contact becomes the res.partner website field and serves as a deduplication key during import. The res.partner Account record must be created before any dependent Contact or res.partner contact import so that the parent_id lookup is satisfied.

Leadfox Deals map to Odoo crm.lead records with type='opportunity'. The Leadfox dealstage property maps to Odoo's stage_id on crm.lead, and the Leadfox pipeline assignment maps to an Odoo crm.team via crm.team member assignment. Closed-Won and Closed-Lost reason custom fields in Leadfox become Odoo Char fields capturing the original reason text.

Leadfox custom fields (text, number, date, dropdown, checkbox) map to Odoo custom ir.model.fields created on the target model (crm.lead, res.partner, or crm.lead.custom) before migration. We validate field type compatibility: Leadfox date fields become Odoo Date fields, numeric fields become Float or Integer, and dropdowns become Odoo Selection fields with the same option keys. Field help text and required flags are replicated from Leadfox field definitions.

Leadfox Tags applied at the Contact level map to Odoo res.partner category records (res.partner.category) with many2many relationship via res_partner_res_partner_categ_rel. For Deal-level tags, we use crm.tag and crm_lead_tag_rel. Tags are exported as static values at migration time; dynamic behavioral segments in Leadfox (which recalculate based on filter criteria) cannot be replicated as live Odoo dynamic filters and are documented for the customer to rebuild as Odoo Actions or domain-based filters.

Leadfox unsubscribe status and suppression list entries map to Odoo res.partner.opt_out = True to ensure CAN-SPAM compliance continuity. We export the suppress file from Leadfox and apply opt_out=True to matching res.partner records during import. Any hard-bounce history stored in Leadfox is noted in a custom Char field for the customer's admin to review.

Leadfox numeric lead scores calculated from behavioral rules (page visits, email opens, form submissions) are exported as a static custom field on each crm.lead record. The original behavioral scoring rule logic is not exported—Odoo CRM's crm.lead.scoring.frequency or a custom scoring model must be rebuilt by the customer's admin using the exported historical scores as a baseline reference.

Leadfox Email Templates from Content Studio export as raw HTML with dynamic personalization tokens (e.g., {{contact.first_name}}). We export the template HTML and the token-to-field map so that tokens can be reconnected manually in Odoo's mail.template editor under Email > Templates. Visual templates that rely on Leadfox's drag-and-drop builder are exported as HTML snapshots only; Odoo requires email templates to be rebuilt or adapted for Odoo's qweb-based template engine.

Leadfox landing pages are built with the platform's proprietary page builder and cannot be exported as live editable pages. We produce HTML snapshots and form field definitions for each page. Form submissions export as crm.lead records with the utm_source, utm_medium, and utm_campaign from the originating Leadfox page. We flag the top-converting pages by submission volume so the customer can prioritize rebuilding those in Odoo or a third-party landing page tool first.

Leadfox automation sequences (triggers, time delays, conditional branches, goal steps) are stored in a proprietary format that cannot be interpreted by external systems. We document every active automation as a step-by-step action map listing trigger conditions, time delays, branching logic, and CRM actions. The customer rebuilds these in Odoo Studio, Server Actions, or Automated Actions under Settings > Technical. We explicitly do not migrate automation logic as executable code.

Leadfox engagement history (calls, emails, meetings, tasks, notes) migrates to Odoo using the destination platform's API where available: calls to crm.phonecall or mail.message with message_type='notification', emails to mail.message, meetings to calendar.event, and tasks to mail.activity or project.task depending on Odoo apps installed. We set create_date on each activity record to the original Leadfox timestamp to preserve the chronological timeline. Note body migrates as mail.message with subtype='comment' linked to the parent record.

Leadfox campaign names, UTM parameters, and search tracking data map to Odoo's utm.mixin fields on crm.lead and res.partner: utm_source_id, utm_medium_id, and utm_campaign_id via Odoo's UTM module. If the UTM module is not installed in the destination Odoo instance, we store UTM values as Char fields on crm.lead and res.partner. Actual analytics and conversion data (impressions, CTR, ROAS) do not transfer as these live in Leadfox's reporting dashboard and not in the contact record.

Leadfox user accounts, roles, and permissions are not accessible via the standard export tools. We extract every distinct Hubspot Owner (or Leadfox user) email referenced on Contact, Company, Deal, and Engagement records and produce a User Mapping Table listing source user name and email. The customer provisions matching res.users records in Odoo before migration begins. Any Owner without a matching Odoo User is placed in a reconciliation queue; migration cannot complete past this step because OwnerId references are required on crm.lead and crm.lead.team_id.

Leadfox suppression lists (hard bounces, explicit unsubscribes, spam complaints) export as a contact reference list and apply as res.partner.opt_out=True on matching Odoo records. We deliver the suppress file as a CSV alongside the migration so the customer's admin can reapply it if needed for compliance audits or cross-platform list hygiene.

Leadfox direct integrations with HubSpot, Zoho, Pipedrive, and Zapier do not have Odoo equivalents out of the box. We document each active integration with its trigger, destination system, and data flow. The customer selects one of three paths: reconnect to the original system via Odoo's generic integration tools, replace with a native Odoo app from the Odoo Apps store, or rebuild via a custom Odoo module using the XML-RPC API. We do not configure these integrations as part of the migration scope.