Journal/News

Mailchimp has a new owner. Export your list this quarter

Bending Spoons has agreed to buy Mailchimp from Intuit for $3.68 billion. Nothing changes this week, but your list and automations are now part of someone else's plan. Here is what to do about it.

Risograph illustration of an open birdcage holding an envelope, resting on stacked ledger slabs

On 19 November, Bending Spoons announced a definitive agreement to buy Mailchimp from Intuit for an enterprise value of $3.68 billion in cash, with the deal expected to close in early 2027 once regulators sign off. You can read the full statement in the Bending Spoons press release announcing the Mailchimp acquisition.

If you run a business in Melbourne that sends newsletters, abandoned cart emails, booking reminders or post-purchase follow-ups through Mailchimp, nothing changes this week. Nothing changes next month either. The deal has not closed. But your customer list, your consent records and your automation logic are now line items in a transition plan written by people you have never met, and the sensible time to prepare for that is while everything still works.

What was actually announced, and what was not

The facts are narrow. Bending Spoons is buying 100% of The Rocket Science Group, the entity behind Mailchimp, plus related assets and liabilities. Intuit is putting $368 million of the proceeds back into newly issued Bending Spoons equity. Closing is expected early 2027. Bending Spoons CEO Luca Ferrari said the company will "invest substantially in the business, building on the powerful, easy-to-use tools customers already value and rely on."

There is no announcement of price changes, plan restructuring or feature removal. Anyone telling you otherwise is guessing.

What is worth reading closely is how Bending Spoons describes itself in its own release. It acquires digital businesses, "implements deep transformations and ongoing optimizations to sustainably expand earnings", and reinvests the proceeds into more acquisitions. The transformation, in its words, "entails reorganizing teams, overhauling technology, redesigning user interfaces, accelerating product development, and enhancing marketing and monetization." That is the company stating its model plainly. Expanding earnings from an existing customer base generally means some combination of charging more, spending less on service, or both.

Its current portfolio includes Evernote, WeTransfer, Vimeo, Eventbrite, Airtable, Brightcove, Tractive, Miro and AOL.

The reaction tells you what users expect

The response from the developer community was uniformly sour. In the Hacker News thread on the Mailchimp acquisition, one commenter called Bending Spoons "somehow a worse owner than Intuit", another described the company as "like the grim reaper, killing and harvesting anything that was once good", and a third compiled a year-by-year list of acquisitions going back to 2018. One commenter noted that Intuit paid around $12 billion for Mailchimp in 2021 and is now selling for roughly a third of that.

Treat all of that as opinion, because it is. But it is informed opinion from people who have lived through the previous transitions, and it is consistent enough to be a signal rather than noise. When the people who have used a buyer's other products all say the same thing, that is worth a quarter of your attention and none of your panic.

Your list is an asset. It is currently sitting on someone else's balance sheet

Here is the part that matters for an owner, and it has very little to do with Bending Spoons.

If a vendor decision could materially damage your ability to reach your customers, you do not own that channel. You rent it. The email addresses are yours. The thing built on top of them, the segments, the sequences, the timing rules, the templates, the signup forms embedded on your website, the integrations wired into your store or booking system, often is not portable in any practical sense.

Exporting contacts is easy. Every platform does it. What does not come out cleanly:

  • Automation logic. The multi-step sequences with branching, delays and conditions have to be rebuilt by hand in whatever you move to. For a business with half a dozen mature flows, that is real work.
  • Engagement history. Opens, clicks and purchase behaviour that your segments depend on. You can often export the raw data, but the new platform will not interpret it the same way.
  • Consent and unsubscribe records. Under Australian spam law you need to be able to show how and when someone opted in, and honour unsubscribes. Those records need to survive the move intact.
  • Deliverability reputation. If you have been sending on shared infrastructure, your inbox placement partly belongs to the platform, not to you. Moving means a warm-up period where open rates dip.
  • Everything pointing at the tool. Signup forms on your site, checkout integrations, webhooks, Zapier connections, the link in your email signature.

None of that is an argument against Mailchimp. It is an argument for knowing the number.

What we would do this quarter

Our position is not "migrate now". Migrating off a working platform because of a press release is an expensive reaction to something that has not happened. Our position is: stop being unable to leave.

Three things, and they are small.

First, take a full export and keep it somewhere you control. Contacts with their tags and merge fields, consent and signup source data, and a copy of your template HTML. Put it in your own storage, not in another SaaS tool. Diarise it to repeat quarterly. If you have never done this, it will take an afternoon.

Second, write down your automations in plain English. Not screenshots. A short document per flow: what triggers it, what it sends, what the delays and conditions are, what happens on each branch. This is the asset most businesses lose when they switch tools, because it only exists inside a drag-and-drop interface and inside one staff member's head. It is also the document you hand a developer when you do decide to move, and it turns a vague project into a quotable one.

Third, price an exit without taking it. Ask your developer or marketing person for a one-page estimate: which platform you would move to, how many hours to rebuild the flows, what breaks on the website, how long the deliverability warm-up takes. You are not committing to anything. You are replacing "we'd have to move, I suppose" with a number. A number lets you make a decision in a week when the renewal notice arrives instead of accepting a price rise because the alternative is unknown.

The broader rule for software you do not own

When we build for clients, the line we draw is this: the data and the business logic that define how your company actually operates should live somewhere you control, and vendor tools should be the delivery mechanism, not the system of record. A platform that sends email is a replaceable supplier. A platform that holds the only copy of your customer relationships and the only definition of your sales process is a dependency, and dependencies get repriced.

That applies to far more than email. It applies to booking systems, point of sale, your CRM, your inventory tool, anything where the switching cost is high enough that you would absorb a price rise rather than deal with it.

So: pull an export this week, document your flows, and get a rough migration estimate on a single page. Then forget about it until something actually changes. That is the whole job.

Filed under: News. Last edited 21 November 2026. Send corrections.
§ Read next
/ News
Who patches your web app? Answer that one today
/ News
OpenAI's legal product tells you what not to build

§ Start a project

Got something
to build?

Websites, stores, apps and custom software, from $500. Send a brief and a senior developer replies within one business day.