The Mailchimp Escape Checklist: Migrate Your List Intact

Here's the migration advice nobody gives you: the list is the plan. Not the new platform. Not the pricing comparison. The CSV export.

Every "should I switch from Mailchimp" article compares features and prices. Almost none of them start where the migration actually succeeds or fails: getting your full list — subscribers, unsubscribes, bounces, consent evidence — out of Mailchimp intact before you touch anything else. Do the export first and the rest is logistics. Skip it and you're rebuilding your audience from memory.

This checklist covers the worst documented failure pattern: a newsletter platform suspends an account overnight and 5,000 subscribers vanish with it — because there was no export. Nobody exports until the day they need one. Plan for that day now.

Step 0: Decide the real question — can you ever be taken off?

Before the checklist, one honest question: if Mailchimp decided tomorrow to suspend your account, pause your sends, or hike your plan 40%, what would you still own?

What you own: the email addresses of everyone who gave you permission, in a CSV you exported yourself. What you don't own: your automations, your templates, your segments, your sender reputation — all of that lives inside Mailchimp and rebuilds by hand. Know the difference now, because the checklist protects the part that's irreplaceable and plans around the part that isn't.

If the answer to "could I be taken off?" is "I'd lose everything," the export below isn't a migration step. It's disaster recovery you should have done yesterday.

Step 1: Export every audience, every segment status, separately

Mailchimp doesn't give you one "export my list" button that catches everything. The audience export downloads as a ZIP of separate CSVs: Subscribed, Unsubscribed, Non-Subscribed, and Cleaned. Each one matters:

Subscribed — your actual list. Obvious.
Unsubscribed — your suppression file. If you leave Mailchimp and these people aren't carried over, your new platform will mail people who opted out. That's not a migration problem, that's a legal one.
Non-Subscribed — contacts from transactions, e-commerce, or API syncs who never opted in. They still tell you who's a customer.
Cleaned — hard bounces Mailchimp stopped mailing for you. Mail them on a new platform and you're re-sending to dead addresses that hurt your deliverability on day one.

Repeat for every audience in the account — Mailchimp accounts often have two or three audiences the owner forgot about, and every one of them exports separately.

Step 2: Export what Mailchimp won't let you take

This is the part most migration guides bury. Your consent records — who opted in, when, and what they agreed to — are the legal proof of your list. Note the source, date, and wording of every signup method you used: the embedded form, the checkout checkbox, the API sync from your store. Screenshot the form settings. Mailchimp doesn't hand you a consent ledger, so build one yourself from the export's timestamp columns and your form documentation.

Then: campaign history. Mailchimp lets you export historical campaign reports. You probably can't import them anywhere — but you want them for comparison, auditing, and the inevitable "how did our last launch perform" question six months from now. Download what's available before you close the account. Multiple migration guides agree on this point: don't close the Mailchimp account on launch day, because historical reports become inaccessible.

Step 3: Document the things that don't export

Automations, tags, and segments do not travel. A 2026 comparison of the major platforms puts it plainly: lists export as CSV everywhere, but "what does not move cleanly is everything around it: automations have to be rebuilt by hand, tags and segments map imperfectly, landing pages and forms need new embed codes." (saascompared.com)

So document before you migrate: - Every automation — open each one and copy the trigger, each step, the subject lines, the waits. Budget 30–45 minutes per automation; it always takes longer than you think. - Tag and segment logic — write down the exact filters ("tag = webinar-2025 AND clicked last 3 emails"). Messy tagging is the biggest source of migration pain; clean it up on paper now. - Sending settings — reply-to addresses, daily limits, signatures, branding. The stuff you set up once and forgot. - Paid subscriber / billing data — if anyone pays you through Mailchimp-adjacent tooling, check how payment history transfers. It's the hardest data to recreate.

Rebuild only the automations that still have a purpose. A migration is the best excuse you'll ever get to kill the zombie workflows.

Step 4: Consider a re-opt-in campaign (and the math)

Here's a fork in the road that depends on your list's age. If your list is fresh and engaged, import it directly. If it's old, cold, or you haven't mailed in months — the same situation that kills deliverability through bounce-rate tripwires — consider a re-opt-in campaign: mail the legacy list once, explain the move, and ask people to confirm.

The real-world playbook (used in an open-source project's Mailchimp-to-self-hosted migration) works like this: export the full list with all custom fields and consent records, import it into the new platform as a holding segment (not the active list), send one confirmation email explaining where their data lives now and who has access, then after two to three weeks move only confirmed contacts to the active list and archive the rest. You don't delete the unconfirmed — you keep them as a record-of-attempt audit trail.

Yes, you'll lose a chunk of the list. The chunk you lose is the chunk that was never going to buy from you — and would have bounced, unsubscribed, or spam-complained your new sender reputation into the ground. A smaller list that actually engages you beats a big list that kills your deliverability. Every deliverability tool says this; almost nobody believes it until they've watched a bounce-rate suspension happen to their own list.

Step 5: Prepare the new sending home before you import

Don't import the list until the new platform is ready to send:

Verify the sending domain first — SPF, DKIM, DMARC on the domain you'll send from. Authentication left until launch day is the classic migration delay.
Import unsubscribed and cleaned contacts FIRST — as suppressed, not as subscribed. The new platform must know who never to mail before the first campaign goes out.
Import subscribed contacts in small test batches — a few hundred at a time. Watch bounces on the first batch before importing the rest.
Warm the reputation — start with your most engaged segment, not the full list. New sending infrastructure mailing 10,000 cold addresses on day one looks exactly like spam to every filter on earth.

Step 6: Keep Mailchimp open for 30 days, then close it

Run the two systems in parallel for one full campaign cycle. Send from the new platform, keep Mailchimp as the safety net and the archive. Once you've sent successfully for 30 days, download the last historical reports and close the account. Only then are you actually off.

The ownership test

After this checklist, apply the question from step 0 to whatever you migrated to: if this new platform suspended you tomorrow, what would you own? If the answer is still "I'd lose everything," you moved the problem, you didn't solve it. The platforms that pass the test are the ones where your list lives in a database you control, exported by default, with no one able to lock you out of your own subscribers.

That's the whole checklist. Export first. Everything else is logistics.

Free self-audit: [grab the ListProof deliverability checklist] — a 15-minute scan that finds the stale addresses, spam-trap risk, and authentication gaps that get lists suspended, before you migrate. No signup.