Migrate from Mailchimp to Odoo CRM

Mailchimp Audiences have no direct Odoo equivalent. We flatten each Audience into the Odoo Partner database and tag every contact with the originating Audience name as an Odoo tag. This preserves Audience membership so it can be filtered in Odoo without maintaining separate audience containers. Audience-level settings including opt-in workflow and campaign defaults are documented separately for Odoo configuration.

Mailchimp contacts map to Odoo Partner records. The standard fields (email, first name, last name, phone, address) map directly to Odoo res.partner fields. Subscription status maps to opt_out (boolean) plus a custom field unsubscribed_date to preserve the unsubscribe timestamp. Non-subscribed and cleaned records land with opt_out set to true and a bounced flag set to true respectively. We run email validation during the transform phase and flag malformed addresses for review before import.

All Mailchimp merge fields (FNAME, LNAME, PHONE, COMPANY, and any custom merge fields) migrate to Odoo custom partner fields. We create each field in Odoo during the schema configuration phase using the appropriate Odoo field type (char, text, date, selection). Field labels and help text are preserved from Mailchimp. Merge field ordering and display position in the Mailchimp form are noted for Odoo form view configuration.

Mailchimp tags migrate directly to Odoo Partner tags. Tags are simple string labels in both systems and map 1:1 without transformation. If a contact has multiple tags, each tag is created once in Odoo and associated via Odoo's ir.model.data many2many relation. Tag counts per contact are preserved in a tag summary field for reporting.

Mailchimp dynamic Segments cannot be replicated as dynamic filters in Odoo without custom development. We export the full segment rules as structured JSON (field, operator, value, combinator logic) and tag every contact that matches the segment with a tag named after the segment. In Odoo, the customer can use saved filters or custom ir.filters to approximate segment behavior, or commission a custom module if dynamic behavior is required.

Mailchimp Groups require their parent Category to exist first, and both export as a name string with no structured ID. We create the parent Category as an Odoo tag category, then create each Group as an Odoo tag within that category. This preserves the group hierarchy from Mailchimp in Odoo. Interests (checkboxes that contacts select within a group) migrate as tags with a prefix matching the group name.

Mailchimp campaigns (sent emails, automated sends,plain text emails) migrate as Odoo Marketing Campaign records with campaign name, subject line, send date, and recipient count preserved. The campaign HTML content is stored as an Odoo Document linked to the campaign. Open and click statistics from Mailchimp Reports migrate as Odoo activity records for reference. Note that automated workflow campaigns require manual rebuild in Odoo.

Mailchimp Automations including Welcome emails, Abandoned cart, Birthday, Post-purchase, and custom Customer Journeys store workflow logic in a proprietary format with no export mechanism. We do not migrate them. We deliver a written inventory of every active automation including trigger type, number of steps, enrollment size, and a written recommendation for rebuilding in Odoo Marketing Automation. The customer or an Odoo partner rebuilds each workflow post-migration.

Mailchimp email templates export as raw HTML files. Odoo accepts HTML content for email templates, but Mailchimp-specific content block syntax may not render correctly in Odoo's template renderer. We import templates as Email Template records in Odoo and flag any that contain Mailchimp-specific shortcodes or dynamic content blocks. Visually complex templates require manual rebuild in Odoo's template builder; plain-text and basic HTML templates typically import without issue.

Mailchimp open, click, bounce, and unsubscribe events for each contact export as a structured record set per contact. We import the last 90 days of activity by default as Odoo mail.message records linked to the Partner, with the event type (open, click, bounce) stored in a custom field and a link to the original campaign. Full campaign activity history (all events since account creation) may require pagination across multiple API pages and is available on request.

Orders, products, and customers synced from Shopify via Mailchimp's e-commerce integration migrate to Odoo Sale Order and Product records if the connected store remains linked during migration. E-commerce data is only accessible while the Mailchimp store connection is live. We coordinate timing with the store connection and export e-commerce data first. Without an active store connection, order history is not accessible through the Mailchimp API and does not migrate.

We authenticate Mailchimp exports using the customer's account-level or user-specific Marketing API key generated from the Mailchimp Extras menu. The key must remain active throughout the migration window. For Odoo ingestion, we use the customer's Odoo XML-RPC or JSON-RPC endpoint with valid database, user, and password credentials. Both credentials are stored securely during migration and destroyed after cutover.