Migrate from Odoo Marketing Automation to HighLevel

Odoo's Contact and Lead both derive from the ir.partner model with a partner_type field distinguishing customer from lead. We export both record types as a single contact set, inferring contact type from Odoo's partner_type or crm_stage fields. The Odoo contact name, email, phone, company (partner_id), tags, and custom fields migrate to GoHighLevel Contact. The Odoo Lead's stage (new, qualified, lost) is preserved as a custom field on the GoHighLevel Contact for reconciliation purposes.

Odoo Companies map to GoHighLevel Contacts with company association via the company_name field and website field. Odoo's company-specific address data (street, city, country, zip) migrates to GoHighLevel Contact address fields. If the customer uses Odoo's Contacts attached to Companies in a parent-child structure, we flatten the hierarchy into GoHighLevel Contact records with the parent company name preserved as a custom field.

Odoo CRM Opportunities map to GoHighLevel Opportunities. The Odoo opportunity name, stage, expected revenue (planned_revenue), probability, partner (contact/account), and lost reason migrate directly. Odoo stage names vary by database and require a mapping table that we define during scoping. Stage probability percentages migrate as GoHighLevel custom fields since GoHighLevel Opportunities do not have native probability fields at all plan tiers.

Odoo Campaigns are the top-level container for Automation Rules and define the target model (Contact, Lead, Sales Order) and audience domain filter. We migrate the campaign name, state (draft, running, done), and target model. The Odoo domain filter (which contacts are enrolled) is documented as a GoHighLevel Smart List definition or a Workflow filter note rather than executed during migration, since domain-based enrollment rules must be rebuilt in GoHighLevel's Workflow trigger conditions.

Odoo Automation Rules migrate as GoHighLevel Workflow definitions. We extract the rule name, trigger type (time-based, email event, server action, record write), filter domain, and action chain (Send Email, Update Record, Create Task, SMS). Each action type is mapped: Odoo Send Email maps to GoHighLevel Send Email action; Odoo Update Record maps to GoHighLevel Update Contact Field action; Odoo Create Task maps to GoHighLevel Create Task action. Python Code activities and Server Action activities that reference Odoo-specific models are flagged as rebuild items in the handoff document. GoHighLevel Workflow triggers (form submit, tag added, stage change, email opened) are documented as the closest functional equivalent.

Odoo Workflow Activities are the individual steps within an Automation Rule: Send Email, Update Record, Create Task, Server Action, SMS. We migrate the activity name, activity type, timing (immediately, after X days), template reference, and child activity link (for multi-step chains). The Odoo email template reference resolves to the Email Template mapping (see below). Each step is documented as a GoHighLevel Workflow node with the action type, delay settings, and conditional branching preserved in the automation inventory.

Odoo Mass Mailings are the sending records tracked in the Email Marketing app: subject, body HTML, scheduled date, and recipient count. The recipient list is resolved via the Odoo Contact or Lead domain filter that the mass mailing targets. We migrate the mailing subject, body HTML, scheduled date, and recipient count as a GoHighLevel Campaign record with the email body stored as an email template and the recipient list rebuilt as a GoHighLevel Smart List or tag-based filter.

Odoo Email Templates store reusable HTML email bodies used by both Email Marketing and Marketing Automation. We migrate template name, subject line, body HTML (with inline image references), and attachment list. Variable placeholders in Odoo ({{object.name}}, {{object.partner_id.name}}) are preserved as merge fields in the GoHighLevel email template using GoHighLevel's {{contact.field_name}} syntax. The customer reviews template rendering during the sandbox phase to confirm merge field substitution is accurate.

Custom fields added via Odoo Studio or ir.model.fields on Contact, Lead, Opportunity, and Campaign records migrate as key-value pairs on the corresponding GoHighLevel object. We preserve the Odoo field name as a GoHighLevel custom field label and the Odoo field type (char, integer, many2one, selection) is mapped to the closest GoHighLevel field type (text, number, single-select dropdown). Many2one fields referencing other Odoo records (e.g., a custom Industry field referencing a separate Industry model) are stored as text strings in GoHighLevel to avoid lookup dependency issues.

Odoo user accounts referenced as create_uid, write_uid, and assignees on CRM records and automation rules are mapped by email match to GoHighLevel Users. Any Odoo Owner without a matching GoHighLevel User is flagged in the reconciliation report for the customer to provision before record import resumes. Active/inactive status is preserved as a GoHighLevel contact custom field for audit purposes.

Odoo tags on Contacts, Leads, and Opportunities are stored in a separate ir.attachment model and flattened to a simple tag list on the partner record. We migrate all tags as GoHighLevel Contact tags by name. Tags used for segmentation in Odoo Automation Rules are documented as GoHighLevel Smart List filter definitions in the automation inventory.