Mailchimp to Odoo CRM migration
We migrate Contacts, Audiences, Tags, and campaign metadata from Mailchimp into Odoo CRM with unsubscribed records flagged as opted-out, subscription status preserved as GDPR-ready fields, and every active Mailchimp automation documented for rebuild in Odoo Marketing Automation.
FlitStack AI migrates contact list / tag memberships, partners, custom partner fields, tags and tag / filters from Mailchimp to Odoo CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 2-4 weeks.

What moves from Mailchimp to Odoo CRM?
Moving from Mailchimp to Odoo CRM is a platform-category shift from an email-first marketing tool to an all-in-one ERP with a built-in CRM module.
Read the full summary
Mailchimp organizes contacts inside Audiences with Tags, Segments, and a merge-field system; Odoo CRM uses a single Partner model with Tags, a type field (individual versus company), and custom fields. The structural difference is that Odoo CRM has no native equivalent to Mailchimp's Audience container, so we flatten multiple Audiences into a single partner database and preserve Audience membership as a tag so it can be filtered in Odoo. Subscription status migrates as boolean fields (opt_in, unsubscribed, bounced) with GDPR-ready labeling. Mailchimp Automations cannot be exported and are delivered as a written inventory with Odoo Marketing Automation rebuild recommendations. E-commerce data from a connected Shopify store migrates if the connection remains live during the export window. We do not migrate workflows, customer journeys, forms, landing pages, or reports as code.
Audience → Contact list / Tag membership
Mailchimp Audiences have no direct Odoo equivalent.
How it maps
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.
Contact → Partner
Mailchimp contacts map to Odoo Partner records.
How it maps
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.
Merge Field → Custom Partner Field
All Mailchimp merge fields (FNAME, LNAME, PHONE, COMPANY, and any custom merge fields) migrate to Odoo custom partner fields.
How it maps
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.
Tag → Tag
Mailchimp tags migrate directly to Odoo Partner tags.
How it maps
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.
Segment → Tag / Filter
Mailchimp dynamic Segments cannot be replicated as dynamic filters in Odoo without custom development.
How it maps
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.
Group and Category → Tag Category and Tag
Mailchimp Groups require their parent Category to exist first, and both export as a name string with no structured ID.
How it maps
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.
- AudienceContact listsplit
- ContactPartner1:1
- Merge FieldCustom Partner Field1:1
- TagTag1:1
- SegmentTagtransformed
- Group and CategoryTag Category and Tag1:1
+ 6 more in the mapping below
How Mailchimp and Odoo CRM differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Mailchimp | Odoo CRM |
|---|---|---|
| Contact model | Audiences as separate containers; contacts scoped to an Audience | Single Partner model; no audience concept; all contacts in one database |
| Segmentation | Dynamic Segments and static Groups with filter-based conditions | Tags and Filters applied to Partner records; no dynamic segment equivalent natively |
| Subscription state | Subscribed, unsubscribed, non-subscribed, cleaned, transactional per contact | Opt-out checkbox on Partner; no native multi-state subscription model |
| Automation | Visual Customer Journeys with triggers, delays, conditions, and AB splits | Marketing Automation module; different trigger model; requires rebuild |
| Pricing model | Contact-count billing across all Audiences including unsubscribed | Per-user app subscription; no contact-count billing; e-commerce adds cost |
| CRM deal tracking | No deal or opportunity object; email-centric engagement tracking | Native pipeline, stages, and revenue tracking on Opportunity object |
| Integration scope | Email marketing with 300+ native integrations including Shopify | ERP ecosystem; CRM is one module among 70+; built-in Odoo Shopify connector |
What to watch for in a Mailchimp to Odoo CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Mailchimp counts unsubscribed and non-subscribed records toward contact billing
Mailchimp charges based on total contacts across all Audiences, including unsubscribed and non-subscribed records.
How we handle it
Only archived, cleaned, and deleted contacts are excluded from billing. When migrating into Odoo CRM, contacts land as Partner records with opt-out set to true for unsubscribed records and bounced set to true for cleaned records. We explicitly flag which records should have opt-out enabled at import time to prevent a billing cliff in Mailchimp if the customer keeps the account partially active during the migration window. GDPR consent fields are preserved as a custom date field consent_date on the Partner record.
Mailchimp Automations cannot be exported and require full rebuild in Odoo
Mailchimp's automation engine stores workflow logic (triggers, delays, conditions, AB splits, goals) in a proprietary format.
How we handle it
There is no export endpoint. We inventory all active automations with their trigger type, step count, and enrollment size, then provide a structured checklist with Odoo Marketing Automation rebuild recommendations. The customer or an Odoo partner rebuilds each automation post-migration. This limitation applies to Welcome emails, Abandoned Cart, Birthday, Post-purchase, and all custom Customer Journeys.
Odoo email marketing allows only one email per campaign
Odoo email marketing has a structural limitation compared to Mailchimp: the built-in Email Marketing app supports one email send per campaign and does not natively support multi-step drip sequences as a campaign construct.
How we handle it
Reddit discussions in the r/Odoo community document that Odoo Marketing Automation handles triggered multi-email sequences but requires separate configuration from the Email Marketing campaign module. We document this limitation during discovery and flag whether the customer's automations can be mapped to Odoo Marketing Automation or whether an external email platform integration is needed.
Template HTML uses Mailchimp-specific syntax that may not render in Odoo
Mailchimp email templates use Mailchimp-specific content block syntax (mailchimp_merge_vars, mc:edit attributes, conditional content tags) that does not render natively in Odoo's template engine.
How we handle it
We export templates as raw HTML files and import them as Odoo email template records, but Mailchimp-specific blocks require manual adjustment in Odoo's template builder. We flag visually complex templates and plain-text templates separately during the template audit so the customer knows which templates need rebuild versus which import cleanly.
Bidirectional Mailchimp-Odoo sync creates master record conflicts without a clear ownership model
If the customer has been running a bidirectional Mailchimp-Odoo sync before migration, contact records may have been updated on both sides during the sync window.
How we handle it
The Ecosire integration guide documents a common failure mode: a contact updated in Odoo overwrites a customer-side update from the Mailchimp email footer unsubscribe link, leaving Odoo showing the contact as subscribed while Mailchimp refuses to email them. We establish Mailchimp as the master for subscription state during migration and flag the need for a master-record ownership model if the customer plans to run Odoo and Mailchimp in parallel post-migration.
How the migration runs
Discovery and Mailchimp audit
We audit the source Mailchimp account across all Audiences, contact volumes per audience (with status breakdown: subscribed, unsubscribed, non-subscribed, cleaned), active Automations with step counts, Segments, Groups, Tags, merge fields, e-commerce store connections, and API key access.
What this step covers
We produce a written migration scope document that identifies the total contact count, any records with malformed email addresses, the number of active automations to inventory, and whether e-commerce data is accessible. This document is the basis for the migration plan and timeline.
Data profiling and quality cleansing
We profile the exported contact data and identify duplicates (contacts appearing in multiple Audiences), contacts with invalid email formats, and unsubscribed or cleaned records that must land with opt-out flags set to true in Odoo.
What this step covers
We deduplicate by email address across all Audiences and flag the resolution method (keep the most recent record, merge field values, or retain both with a duplicate indicator tag) with the customer before import. Malformed email addresses are exported to a separate review list for the customer to validate or suppress.
Odoo schema configuration
We configure the destination Odoo instance before any data import.
What this step covers
This includes activating the CRM, Email Marketing, and Contacts apps. We create custom Partner fields for each Mailchimp merge field using the appropriate Odoo field type, set up Tag categories matching Mailchimp Group Categories, configure unsubscribed and bounced as boolean fields on Partner, and create an opt-in consent date field for GDPR compliance. Audience membership tags are pre-created so that contacts can be tagged at import time without creating duplicate tags.
Phase migration in dependency order
We run migration in phases: Contacts first (with Audience membership as tags and opt-out flags set per status), then Segments and Groups as tags, then campaign metadata and email templates (HTML exported separately for manual template rebuild where needed), then Email Activity history (last 90 days default), then E-commerce data if the Shopify connection remains live.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Odoo XML-RPC batch inserts use configurable chunk sizes to stay within Odoo's API rate limits.
Automation inventory and rebuild handoff
We deliver the written automation inventory covering every active Mailchimp Automation: trigger type, step count, enrollment size, and a written recommendation for rebuilding in Odoo Marketing Automation including trigger equivalent, action mapping, and delay configuration.
What this step covers
We do not rebuild automations in Odoo as this is outside standard migration scope. The inventory document is formatted as a checklist that the customer's admin or an Odoo partner uses to configure Marketing Automation post-migration.
Cutover, validation, and post-migration handoff
We freeze Mailchimp writes during cutover, run a delta migration of any records modified during the migration window, then validate total contact counts in Odoo against Mailchimp export totals.
What this step covers
We spot-check 25 to 50 records for field-level accuracy. We deliver the final reconciliation report, the automation inventory, and a post-migration operations guide covering opt-out handling, template management, and email deliverability monitoring. We do not provide post-migration admin support or training as standard scope.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with total contact count, number of Audiences, and whether e-commerce order and product data are in scope. Odoo subscription cost (app-based; CRM is one module of many) sits outside the migration fee and depends on which Odoo apps the customer activates. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Mailchimp to Odoo CRM →Why teams move from Mailchimp to Odoo CRM
- Contact-count pricing becomes punitive as Mailchimp lists grow. Reviews on G2 and Capterra document sticker shock when total contacts including unsubscribed and non-subscribed records push accounts from $13/month to $75/month or beyond. Odoo CRM charges per user regardless of contact volume, making it more predictable for businesses that maintain large prospect databases and do not need email-first marketing features at scale.
- Teams that need pipeline management and deal tracking outgrow Mailchimp's contact-centric model. Odoo CRM provides a visual pipeline kanban, Opportunity stages with revenue amounts, and quote generation that Mailchimp does not offer. Businesses migrating from Mailchimp to Odoo typically want to consolidate CRM and ERP operations onto one platform after recognizing that email marketing alone does not manage the full customer lifecycle.
- Post-Intuit acquisition uncertainty has prompted businesses to evaluate alternatives. Reddit threads and G2 reviews from 2024-2026 describe user frustration with platform direction, with reviewers describing Mailchimp as limited and expressing concern about long-term roadmap. Odoo, as an open-source platform with an active developer community, appeals to teams that want platform independence and self-hosting options via Odoo Community.
- Odoo's modular all-in-one architecture reduces tool sprawl. Teams using Mailchimp alongside separate CRM, accounting, or inventory tools migrate to Odoo to consolidate operations. Odoo CRM integrates natively with Odoo Sales, Accounting, Inventory, and Project modules, eliminating the data synchronization overhead that a Mailchimp-plus-standalone-CRM stack requires.
- Odoo CRM is enterprise-level at a fraction of the cost of traditional CRM platforms. Odoo Community is open-source and free; Odoo Enterprise starts at a fraction of Salesforce or HubSpot Enterprise pricing. Businesses migrating from Mailchimp to Odoo often cite total cost of ownership as a factor, particularly when they have outgrown Mailchimp's feature ceiling but do not want to pay Salesforce-level licensing.
Questions, answered
Mailchimp to Odoo CRM migration questions
How long does a Mailchimp to Odoo CRM migration take?
Most migrations land between two and four weeks for straightforward contact and campaign data without e-commerce. E-commerce migrations with Shopify order history, or migrations with more than 20 active Mailchimp Automations to inventory, move to four to six weeks. Contact volume is a secondary factor compared to data quality; a clean contact list of 50,000 records migrates faster than a list of 5,000 records with heavy deduplication requirements.
Do Mailchimp Automations and Customer Journeys migrate to Odoo?
No. Mailchimp Automations store workflow logic in a proprietary format that cannot be exported. We do not migrate them as code. We deliver a written inventory of every active Mailchimp Automation with its trigger type, step count, enrollment count, and a written recommendation for rebuilding in Odoo Marketing Automation. The customer or an Odoo partner rebuilds each workflow post-migration. This limitation applies to Welcome emails, Abandoned Cart, Birthday, Post-purchase, and all custom Customer Journeys.
What happens to unsubscribed and cleaned Mailchimp contacts during migration?
Unsubscribed Mailchimp contacts migrate as Odoo Partner records with the opt_out boolean set to true and a custom unsubscribed_date timestamp field preserved. Cleaned contacts (hard bounces) also land with opt_out set to true and a bounced boolean set to true to prevent them from being re-activated in Odoo. GDPR consent dates migrate to a custom consent_date field on the Partner record. This ensures compliance records travel with the contact even though Odoo does not have a native multi-state subscription model equivalent to Mailchimp's.
Can we keep Mailchimp running for email marketing and use Odoo for CRM?
Yes. A hybrid stack is common for businesses that want Odoo's pipeline management and ERP capabilities but prefer Mailchimp's email deliverability and template builder for campaigns. We configure a unidirectional sync from Odoo to Mailchimp so that new Odoo Partner records flow into the appropriate Mailchimp Audience. Mailchimp remains the email-sending platform and the master for subscription state. The customer pays for both Odoo CRM and Mailchimp subscriptions concurrently during the transition.
Will our email deliverability be affected by switching from Mailchimp to Odoo?
Odoo uses its own sending infrastructure or the customer's configured SMTP server, which is different from Mailchimp's established email deliverability reputation. A brief deliverability dip is expected during the IP warming period after cutover, typically one to two weeks. We recommend configuring proper SPF, DKIM, and DMARC records in Odoo before the first large send, and monitoring bounce rates closely during the first 30 days. For businesses with high deliverability requirements, we recommend integrating Odoo with a dedicated email service provider (SendGrid, Amazon SES, or Mailgun) rather than relying on Odoo's default sending.
How do you handle Mailchimp Segments during migration?
Mailchimp dynamic Segments cannot be replicated as live dynamic filters in Odoo without custom module development. We export the full segment rules as structured JSON including field names, operators, values, and combinator logic. We then tag every contact that matches the segment with a tag named after the segment in Odoo. This preserves the segment membership so it can be filtered using Odoo's saved filters or ir.filters. For true dynamic behavior in Odoo, the customer would need a custom Odoo module or an external segmentation tool.
What email templates can be migrated from Mailchimp to Odoo?
Mailchimp templates export as raw HTML files. Plain-text and basic HTML templates without Mailchimp-specific content blocks (merge tags, conditional content, mc:edit attributes) import into Odoo email templates without manual adjustment. Templates with Mailchimp-specific syntax require manual rebuild in Odoo's template builder. We flag each template during the template audit with an importability assessment (clean, manual adjustment required, or full rebuild required) so the customer knows what to expect before migration begins.
Related migrations
Odoo implementation
Set up Odoo CRM and migrate into it as one engagement.
See the service → SuiteCRM to Odoo CRMMapping · history · rollbackZendesk Sell to Odoo CRMMapping · history · rollbackAct! to Odoo CRMMapping · history · rollbackJonas Enterprise Service & Construction Software to Odoo CRMMapping · history · rollbackHubSpot to Odoo CRMMapping · history · rollbackPipedrive to Odoo CRMMapping · history · rollback Mailchimp to SalesforceMapping · history · rollbackMailchimp to HubSpotMapping · history · rollbackMailchimp to Zoho CRMMapping · history · rollbackSources: official documentation
- Export and import data — Odoo 19.0 documentation
- Import products — Odoo 19.0 documentation
- Odoo Online programmatic throughput limits — Odoo Forum
- Data Cleaning — Odoo 19.0 documentation
- Merge Fields Documentation — Mailchimp Developer
- Format Guidelines for Your Import File — Mailchimp
- Manage Audience and Signup Form Fields — Mailchimp
Get a quote
Moving from Mailchimp to Odoo CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Odoo CRM setup with you, then send a quote.
Get a quote