Migrate from Odoo Marketing Automation to Mailchimp

Odoo CRM Contacts map to Mailchimp subscribers within a target Audience. We map name (split into FNAME and LNAME merge fields), email, phone, company (mapped to COMPANY merge field), and tags (flattened to Mailchimp tags). The primary email address is the dedupe key during import. Contacts with no email address are excluded and documented in a reconciliation report because Mailchimp requires a valid email for subscriber records.

Odoo CRM Leads map to the same Mailchimp Audience as Contacts. Leads and Contacts share Odoo's unified partner model, so we pull both from res.partner with a filter on lead-specific fields (lead_id, stage_id) to identify which records originated as Leads versus Contacts. We preserve the Odoo Lead stage in a custom merge field odoo_lead_stage__c for reference.

Odoo Marketing Automation Campaigns map to Mailchimp Campaigns. We migrate campaign name, target model filter (Contact, Lead), and audience domain filter as a Mailchimp segment definition. Campaign state (active, draft, archived) maps to Mailchimp campaign status. The activity trace logs (which contacts entered the campaign) are documented as a written record rather than migrated as a data entity because Mailchimp does not store enrollment history in the same structure.

Odoo Email Marketing templates migrate to Mailchimp Templates. We preserve template name, subject line, and HTML body. Inline images and variable placeholders are preserved where they use standard Odoo Jinja2 syntax; custom variable tokens may require reformatting in Mailchimp's template editor. The template type (standard versus automation-triggered) is noted in the migration inventory.

Odoo Mass Mailings map to Mailchimp Regular Campaigns with send history preserved in a migration log. Subject, body HTML, scheduled date, and recipient count transfer to Mailchimp campaign records. Recipient lists are resolved via the Contact and Lead dedupe mapping before send. Any Odoo mass mailing marked as a test send is flagged and excluded from the campaign migration inventory.

Odoo Automation Rules with time-based triggers or email-event triggers (opened, clicked, replied) are documented in a written inventory for rebuild in Mailchimp Automation Builder. Each rule entry includes trigger type, filter domain, activity chain (send email, update record), and timing configuration. This inventory serves as the handoff document for the customer's marketing team to reconstruct in Mailchimp's visual builder. Rules with Python Code activities are excluded from the inventory and flagged separately as manual-rebuild items requiring developer involvement.

Individual Odoo workflow activities (Send Email, Update Record, Create Task, SMS) map to Mailchimp Automation steps. We document each step's activity type, timing (delay in days or hours), template reference (resolved via the template mapping), and child activity link (for multi-step sequences). The customer uses this step inventory to rebuild the sequence in Mailchimp's Automation Builder because workflow metadata does not transfer as executable code across platforms.

Odoo tags on Contacts and Leads migrate as Mailchimp tags. Tags are stored as string arrays on the subscriber record. We preserve all tag names exactly and map them to Mailchimp tags using the Tags API endpoint after subscriber import completes. Tags used for segmentation in Odoo campaigns map directly to Mailchimp segment filters.

Odoo custom fields (added via Odoo Studio or ir.model.fields) migrate as Mailchimp merge fields. We map the field label to the merge field name, the Odoo field type to the nearest Mailchimp merge field type (TEXT, NUMBER, DATE, ADDRESS, PHONE), and the field value to the subscriber's merge field value. Any many2one or relational field in Odoo is flattened to the target record's display name. Merge fields must be created in Mailchimp before subscriber import so that values can be written during the upsert step.