Migrate your Odoo Marketing Automation data

Contacts are the core audience unit for Marketing Automation campaigns. We migrate name, email, phone, company, tags, and custom fields. The CRM contact model is stable and well-documented across Odoo versions 14–19.

Leads are the primary enrollment target for automation workflows. We map Lead name, email, stage, priority, expected closing date, and source. Leads and Contacts share a unified partner model in Odoo but are tracked separately in campaign targeting.

Opportunities can be used as workflow targets via the domain widget. We migrate opportunity name, stage, expected revenue, partner, and lost reason. Stage names vary by database and require a mapping table during migration.

Campaigns are the top-level container for automation rules. We migrate campaign name, target model (Contact, Lead, Sales Order), audience domain filter, and campaign state. Traces and activity logs are migrated as read-only history records.

Automation Rules are the workflow definitions that trigger actions. We migrate rule name, trigger type (time-based, email event, server action), filter domain, and action chain. Rules containing Python server-action code cannot be replayed on non-Odoo destinations and are flagged for manual rebuild.

Workflow Activities are the individual steps within an Automation Rule (e.g., Send Email, Update Record, Create Task). We migrate the activity type, timing, template reference, and child activity links. Email templates are migrated separately as HTML blobs.

Mass Mailings are the email-sending records tracked in the Email Marketing app. We migrate subject, body (HTML), scheduled date, and recipient count. Recipient lists are resolved via Contact or Lead domain filters at migration time.

Email Templates store reusable HTML email bodies used by both Email Marketing and Marketing Automation. We migrate template name, subject, body HTML, and attachment references. Inline images and variable fields require field-level mapping against destination placeholders.

Custom fields added via Odoo Studio or ir.model.fields are migrated as key-value pairs on the parent record. The field type (char, integer, many2one, etc.) is preserved from the ir.model.fields metadata and mapped to the destination schema.

Odoo user accounts are referenced as create_uid, write_uid, and assignees on CRM records and automation rules. We map user login, name, and active status. On destination platforms without an equivalent user model, owner assignment defaults to the migration admin account.

Tags on Contacts, Leads, and Opportunities are migrated as string arrays and reassigned by name on the destination. Odoo stores tags in a separate ir.attachment model; we flatten them to a simple list during export.

Attachments (documents, images, inline email assets) are stored in Odoo's ir.attachment table as binary blobs with complex path dependencies. We do not migrate attachments; we flag their existence in trace logs and provide a separate file listing for manual download.