Migrate from Marketing Optimizer to Odoo CRM

Marketing Optimizer Contact records map directly to Odoo Partner (res.partner) records. Standard fields (name, email, phone, company) map 1:1. The is_company flag on Partner determines whether the record represents an organization or an individual contact. Company linkage from Marketing Optimizer maps to a parent Partner relationship via the parent_id field on res.partner. We resolve parent Partner records before Contact import so that the relationship is satisfied at the time of insert.

Marketing Optimizer Lead records map to Odoo CRM Lead (crm.lead). The lead-selling lifecycle stage (e.g., New Lead, Assigned, Sold, Buyer Confirmed) does not map to any Odoo standard field. We preserve the original lifecycle stage value in a custom Char field (x_mktopt_lifecycle_stage) on the Odoo Lead for audit and reporting. Lead assignment to buyers or internal users maps to the Odoo Lead's user_id field by resolving the email address match against Odoo Users.

Marketing Optimizer Lead Assignments map a lead to a specific buyer or internal user. We migrate these as the Odoo Lead's user_id (owner) field and add a custom Many2one field (x_mktopt_assigned_buyer_id) pointing to the assigned Partner record for buyer linkage. If the assignment has a status or timestamp, we preserve these in additional custom fields.

Marketing Optimizer Company records map to Odoo Partner with is_company=True. The company domain or website from Marketing Optimizer maps to the Partner's website field. Company records must be imported before any Contact or Lead that references them so that the parent Partner record exists when the child records are inserted.

Marketing Optimizer Campaign records (name, type, associated contacts) map to Odoo's UTM Campaign (utm.campaign). Associated contacts are re-linked via the Odoo utm.source and utm.medium tracking fields on the Lead or Partner record. We document the original campaign-contact associations during scoping and apply them as link_ids during Odoo import. Campaign logic (automation triggers and conditions) does not migrate; it is included in the workflow rebuild inventory.

Marketing Optimizer web tracking data (pages visited, time on site) per contact migrates as a custom Char or Text field (x_mktopt_web_tracking) on the Partner record. Because Odoo CRM does not have a native web activity model equivalent to HubSpot's engagement timeline, we store the raw tracking summary as a structured text field or JSON field depending on the Odoo version. The customer decides whether to surface this data in a custom dashboard widget.

Any Marketing Optimizer custom fields on Contacts, Leads, or Companies require custom field creation in Odoo via Studio before migration. We document all custom field names, types, and values during scoping, create matching Odoo fields (with x_ prefix for custom fields in Community edition), and map the values during import. Custom fields on Leads that store lead-selling-specific values (e.g., buyer tier, lead grade) map to custom fields with Char or Selection type in Odoo.

Attachments associated with Marketing Optimizer Contacts, Leads, or Companies are not accessible via the documented API. We flag all attachments during discovery, list them by record ID, and recommend the customer exports them manually to a shared drive or cloud storage before the migration window opens. Any attachments not manually exported will not appear in Odoo. We do not skip migration of records with attachments; we deliver a complete attachment export checklist alongside the migration inventory.

Marketing Optimizer automated workflows (lead routing, scoring, action triggers) do not migrate as executable code. We extract and document every active workflow with its trigger conditions, conditional branches, delay rules, and action sequences as a written rebuild guide. The customer's Odoo admin or an Odoo implementation partner uses this document to recreate equivalent automations using Odoo Studio or the Marketing Automation app. We do not copy workflow logic into Odoo.

Marketing Optimizer Owners map to Odoo User records. We resolve by email match. Any Marketing Optimizer Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Leads and Contacts migrates by resolving the email address to the Odoo User record's id.

The lead-selling lifecycle stage is Marketing Optimizer's most platform-specific field with no native Odoo equivalent. We preserve it as a custom Char field on crm.lead rather than attempting to force it into the standard lead stage field, which is reserved for Odoo's own pipeline stage progression. The customer uses this preserved value to build reports, segment leads, or normalize stages in a future configuration pass.

Marketing Optimizer notes attached to Leads or Contacts migrate as Odoo Chatter messages (mail.message) on the Partner or Lead record, linked via mail.thread. The note body migrates as plain text. If the Odoo destination does not include the Discuss app, we fall back to a custom Text field on the Partner record.