Migrate from Odoo Marketing Automation to Odoo CRM

Odoo Marketing Automation reads from the same res.partner model that Odoo CRM uses for Contacts. We migrate name, email, phone, company (partner_id), tags, and custom fields from the source partner records. The internal id from the source database is preserved in a custom migration_ref field so that Campaign traces can be reconciled against the original contact records after migration.

Leads in Odoo Marketing Automation and Odoo CRM share the crm.lead model. We migrate lead name, email, phone, company name, stage_id, priority, source, expected closing date, and tags. Stage names vary by database and require a mapping table built during scoping. Owner (user_id) migrates by email match against the Odoo destination User table.

Opportunities can be enrollment targets in Marketing Automation via domain filters. We migrate opportunity name, partner_id, stage_id, expected revenue, probability, lost reason, and close date. Opportunities referenced in Automation Rule domain filters are preserved as CRM Opportunities after migration, and the domain filter logic is included in the automation inventory document for manual rebuild.

Marketing Automation Campaigns have no direct CRM equivalent. CRM does not have a campaign object for marketing orchestration. We migrate Campaign name, target model (Contact, Lead, or Sales Order), audience domain filter, and campaign state as a reference record stored in a custom CRM_Campaign migration table. The customer's Odoo admin uses this as the lookup reference when rebuilding automation inside CRM Automated Actions.

Automation Rules are the workflow definitions in Marketing Automation (trigger, filter domain, action chain). These do not have a direct CRM equivalent and cannot be replayed on the destination because CRM Automated Actions have a different trigger model and action set. We extract every Automation Rule with its name, trigger_type (time-based, email event, server action, record creation), filter_domain, and action chain, and present it as a written inventory document with recommended CRM Automated Action equivalents. Python Code activities are flagged separately as manual-rebuild items.

Workflow Activities are the individual steps within an Automation Rule (Send Email, Update Record, Create Task, Server Action). We extract activity type, timing (wait_days, interval_type), template reference, and child activity links as part of the Automation Rule inventory. Send Email activities map to CRM Email Templates and can be reused; Update Record activities map to CRM Automated Action field updates; Create Task activities map to CRM Project tasks or CRM activities.

Mass Mailings tracked in the Email Marketing app (mailing.mailing records) are migrated as reference objects in a custom CRM_MassMailing migration table with subject, body (HTML), scheduled_date, recipient count, and mailing statistics (sent, delivered, opened, clicked). The email body HTML is preserved for re-use inside CRM Email Templates if the customer rebuilds a campaign send in CRM.

Email Templates from the Email Marketing app (mail.template records) migrate to CRM Email Templates. We migrate template name, subject, body HTML, and inline image references. Variable placeholders (mail_merge_model fields) are preserved with a note that they require reconfiguration inside CRM because CRM uses a different merge model than Marketing Automation.

Tags on Contacts, Leads, and Opportunities in Marketing Automation are stored in the ir.model.data pattern shared with CRM. We migrate tag names as string arrays and reassign by name on the destination. Duplicate tag names across source objects are merged into a single tag list per CRM convention.

Custom fields added via Odoo Studio or ir.model.fields on Contact, Lead, and Opportunity are migrated as key-value pairs on the parent record. We inspect the ir.model.fields metadata to determine field type (char, integer, many2one, date, etc.) and create equivalent custom fields in the destination CRM database before importing data. Many2one fields require lookup resolution against the referenced model.

Odoo user accounts are referenced as create_uid, write_uid, and assignees on CRM and marketing records. We map user login, name, and active status by email match against the destination Odoo User table. Any source user without a matching destination user is flagged for the customer admin to provision before record migration begins.

Campaign Trace records (marketing_trace records linked to contacts and leads) capture enrollment events in Marketing Automation. CRM has no trace log equivalent. We migrate trace data as reference records in a custom CRM_CampaignTrace migration table keyed to the original contact and campaign IDs, allowing the customer admin to reconstruct trace history inside CRM Activities or a custom model post-migration.