Mailchimp has a new owner. Five inventories come before any migration decision
The Mailchimp sale is expected to close in early 2027. Before you renew or migrate, inventory five things no export carries.
Nobody has to change email platforms because Mailchimp changed owners. But the clock started on November 19. Intuit's agreement to sell Mailchimp to Bending Spoons is expected to close in early 2027, so most accounts will hit a renewal, and probably a price conversation, before the ownership actually changes. The companies that get through this cheaply do the same thing first: inventory what they have, in five categories, before anyone books a demo.
What the filing actually says
On November 19, 2026, Intuit announced a definitive agreement to sell Mailchimp to Bending Spoons for approximately $3.68 billion, made up of $3.31 billion in cash and $368 million in Bending Spoons stock, per Intuit's investor release. Bending Spoons' own newsroom describes it as an all-cash transaction in which Intuit invests $368 million of its proceeds into newly issued Bending Spoons equity, and states the deal is subject to regulatory approvals and expected to close in early calendar 2027.
Two more numbers from the same release are worth keeping next to the headline. Intuit bought Mailchimp in 2021 for roughly $12 billion. And Mailchimp's revenue in the quarter ending October 31, 2026 was $313 million, down 1 percent year over year.
That gap between $12 billion and $3.68 billion is the most-quoted number of the week, and it is also the least useful one for your planning. It tells you what one buyer thinks the asset's future cash flows are worth. It tells you nothing about what your account will cost in April.
What it does suggest is a management posture: a platform whose disclosed revenue is flat to slightly down while it changes hands tends to be run for retention and margin rather than for land-grab growth. Treat that as a hypothesis to test against the quote you actually receive, not a conclusion to act on.
An export is a copy of the data, not a copy of the system
The single most expensive misunderstanding in any ESP migration is that "we can export everything" means "we can move everything." Mailchimp documents its own export surface precisely enough to settle the question.
Its account export gives you one export per 24-hour period, packaged as a ZIP: campaign emails with an HTML/TXT campaigns_content folder, audience files split by marketing status, report folders including aggregate activity and per-contact granular activity, email templates as HTML, your content-studio gallery, SMS consent data, custom events passed through the API, and appointments. The same page notes you can re-import that data — "with the exception of email and SMS reports."
Now read that list as what it is: an inventory of artifacts. Missing from it is everything that acts on the data. There is no portable definition of a customer journey, no segment logic, no hosted signup form or pop-up, no API keys, no webhooks, no CRM field mapping. And the sending identity is not in the ZIP at all, because it does not live in the account — Mailchimp's authentication documentation puts it in DNS: two CNAME records for DKIM and one TXT record for DMARC, on a domain you own and control, with a note that Gmail and Yahoo require custom authentication and a published DMARC record above 5,000 messages a day.
A new provider issues new record values. Authentication gets rebuilt, not migrated. So does sender reputation.
The contact-level export has its own limits that matter operationally: it splits into separate CSV files by contact type (subscribed, unsubscribed, non-subscribed, cleaned), it explicitly excludes email report data such as open and click rates, the files are only available in the account for 30 days, and only Owners and Admins can run an audience export. If the person who owns the account leaves in the middle of your project, the export stops with them.
The five inventories
Run these in order and write the answers down. Each one has a different owner, which is why "we'll handle the migration" as a single task always slips.
| Artifact | Where it lives | What an export does with it | Who signs off |
|---|---|---|---|
| 1. Live journeys and automations | Automation and Customer Journeys, plus any API-driven sends | Gives you the email HTML, not the trigger logic, delays, or branch conditions | Lifecycle marketing owner |
| 2. Consent and suppression state | Contact marketing status, opt-in records, cleaned addresses, SMS consent | Splits contacts into separate CSVs by type, but not the reason behind each status | Legal or compliance |
| 3. Sending identity | DNS: DKIM CNAMEs, DMARC TXT, plus dedicated-IP sending history | Absent entirely: new provider, new records, reputation starts over | Deliverability owner |
| 4. Integration surface | Hosted forms and pop-ups, ecommerce sync, CRM field mapping, API keys, webhooks | Landing pages and ad content are explicitly not exportable; keys die with the account | RevOps or IT |
| 5. Audience fidelity | Tags, groups, merge fields, custom events, per-contact engagement | Tags and groups survive as columns at best; per-contact opens and clicks only exist in the account export's granular activity folder | Marketing ops |
The trap inside inventory two
Most teams collapse "unsubscribed" and "cleaned" into one bucket called bad contacts. They are different facts with different obligations. An unsubscribe is a consent decision a person made. A cleaned address is a hard bounce the platform recorded. If you rebuild your suppression list from a CSV and lose the distinction, you will either mail people who opted out, which is a compliance problem, or permanently retire addresses that were only temporarily undeliverable. Mailchimp keeps them in separate files for a reason; your target platform's import will happily let you merge them.
This is the same class of problem as automation that sends without checking whether it should, and it is more expensive after a migration because nobody remembers the original reason.
The four numbers that decide staying versus leaving
Skip the license-price spreadsheet until you have these. None of them are vendor quotes; all of them change the answer.
- Live journeys, not contacts. Migration cost tracks how many automations are running and how many people depend on each one being right, not how big the list is. A 40,000-contact list with three automated flows is a two-week project. A 9,000-contact list with nineteen flows, three of them feeding a sales handoff, is a quarter.
- Share of revenue that arrives through automated flows. If most revenue comes from one-off campaigns, migration is mostly a list-and-template job and the risk is low. If automated flows carry the recurring revenue, you are moving a machine that runs while everyone sleeps, and it needs a parallel run.
- Cleaned ratio and engagement recency. A decaying list costs the same at either vendor, and it costs more at a vendor now managed for margin. Cleaning before the move is cheaper than cleaning after, because you are not paying to store dead weight in the meantime. The mechanics of that decay are covered in how dirty CRM data costs revenue.
- Renewal date versus expected close. The close is expected in early 2027. Your renewal probably comes first, which means the lever in your hand is the renewal, and the deal is the context, not the reverse. If your contract has an assignment clause, read it now rather than assuming either outcome.
There is a fifth number people reach for and should not: the acquisition price. It does not appear in your cost model.
The sequence that avoids paying twice
Once the inventory is on paper, the migration order is mechanical. Every stage produces the input for the next one.
- Freeze new automation builds. Two weeks, no exceptions. Every flow you build during the inventory is one more thing to rebuild.
- Export with a receipt. Take the account export, record the date and a checksum, and store the archive outside both vendors. Mailchimp allows one account export per 24 hours, so plan it. You get one clean shot per day, not a do-over whenever someone remembers a missed folder.
- Rebuild one real journey in the target on a small segment. Not a test send. A live journey with a live branch, on 2 percent of the audience, with the same exit rules. If the exit rules cannot be expressed in the new platform, you have learned something worth more than the whole migration budget.
- Cut over by sending domain, not by list. Move the domain and its new DKIM and DMARC records first, verify them, then move the audience behind them. Reversing that order means your first week of mail from the new platform goes out on reputation you have not built.
- Leave the old account read-only for 90 days. Not deleted. Report history is the only way to answer "was it always like this?" in the first quarter, and re-importing historic reports back into the new platform is exactly what the export documentation says you cannot do.
In migration work, the cutover that breaks is almost never the import. It is the flow someone rebuilt from memory three weeks earlier and nobody tested against the old behavior. Deliverability is the second failure point, and it usually shows up as a slow decline rather than an error, which is the pattern described in the deliverability layer nobody configures.
What to do this week
- Open the account and count live journeys, then write down the owner of each one. If nobody owns a flow, that is your first decision, not your first rebuild.
- Take the account export today, even if you decide to stay. It is dated evidence of your own data, it costs one click, and the 24-hour limit means starting early is free.
- Pull your order form and read the assignment and renewal clauses. That is a fifteen-minute task that tells you whether the closing date matters to you at all.
If you want the inventory done properly, with journeys mapped to owners, consent state classified and sending identity documented before anything moves, that is what our CRM implementation and migration practice does, and the first step is usually a two-hour scoping call rather than a proposal. If you are still deciding whether two platforms should merge at all, the consolidation framework is the better starting point.
You can book that call here.
Frequently Asked Questions
What does a Mailchimp export leave out?
An export copies artifacts, not behavior. Mailchimp's account export bundles campaign emails, audience files, report folders, templates, content-studio images, SMS data, custom events and appointments — and it can be re-imported, with the exception of email and SMS reports. The journey and automation definitions, segment logic, hosted forms and pop-ups, API keys, webhooks and the sending-domain authentication records are not in that ZIP. Those have to be rebuilt or reissued.
Does the Mailchimp sale change my contract terms?
Nothing in the November 19 announcement changes your terms on its own. The agreement is subject to regulatory approval and is expected to close in early 2027. Assignment language lives in your order form and master agreement, so read those before assuming either that nothing changes or that everything does.
Should I migrate off Mailchimp before the deal closes?
Not because of the announcement. Migrate when your inventory says the cost of staying is higher than the cost of leaving — measured in live journeys, revenue that depends on automated flows, list quality and your renewal date. An ownership change is a reason to run that inventory now, not a reason to sign a new contract this month.



