How to migrate from Mailchimp without losing unsubscribe state

A perfect row count can hide a dangerous migration. Every email address may arrive while the facts that decide whether it may be emailed disappear.

Mailchimp currently distinguishes subscribed, unsubscribed, non-subscribed, cleaned, pending, archived, and deleted contacts. Its audience export can contain separate files for the first four states. Treat those files as separate instructions, not one pile to concatenate. The new platform should never become more permissive merely because its data model uses different names.

In email operations, the durable do-not-send record is often called a suppression. The label matters less than the behavior: a future upload, form, integration, or AI agent must not quietly turn that person back into an eligible recipient.

Start with a manifest of the real account. Record each object, its owner, last use, dependencies, export method, destination, and whether it should move, be rebuilt, or retire. This exposes hidden work before the cutover date does.

Mailchimp's full account backup can include audiences, campaign content, reports, templates, and other account data. Its audience export includes fields, marketing permissions, and opt-in information where available. Download both when the account and your retention policy make that appropriate. A contact export alone does not capture every dependency.

Write the destination rule in plain language before running an import. If a source fact is ambiguous, quarantine it for review. Do not resolve uncertainty by declaring the person subscribed.

1. 01Load global exclusions, opt-outs, complaints, and known bad addresses before any active audience can send.
2. 02Retain the source audience, contact ID, state, state timestamp, collection method, and scope where those facts exist.
3. 03Keep email and SMS permission separate. Permission for one channel is not permission for the other.
4. 04Reject any transformation that makes a record more emailable without new evidence or a documented business rule.
5. 05Count every skipped, quarantined, merged, and rejected record. An invisible exception cannot be reviewed.

A deletion request is not simply another marketing status. Follow the privacy and retention rules that apply to your organization. The practical systems requirement is to avoid deleting a record in one place while leaving a different system free to add the person back without the required controls.

Mailchimp treats audiences independently. Someone can opt out of one audience and remain subscribed to another. A destination with one customer profile must decide whether those boundaries represent different brands, purposes, regions, or merely old duplication.

Create a precedence table before merging. A global complaint or known bad address should normally stop email everywhere. A preference for one publication may stay scoped to that publication. When the evidence cannot establish the scope, hold the address out of marketing until a person or a new consent event resolves it.

A tag named VIP might be a lasting customer tier, a temporary workflow marker, or residue from an automation that no longer exists. A saved segment is a live rule, not the list of people who happened to match it during export.

For every segment, write the rule in plain language, identify its fields and events, rebuild it, evaluate both systems at the same time, and inspect the differences. Mailchimp groups deserve special care because its documentation describes them as contact-facing preferences. Do not flatten a stated preference into an invisible internal tag.

For every automation, classify people as not entered, waiting, between steps, at a branch, completed, exited, or unclear. Some journeys should finish in Mailchimp while only new entrants use the destination. Others can switch at a dated checkpoint. If the destination cannot represent the current position safely, stop or finish the old journey instead of guessing.

Moosewave's automation system and audience model keep live eligibility and workflow state inspectable. An optional AI agent can help compare rules, but a person can run the self-serve migration directly and approves consequential changes.

A successful rehearsal creates a report you can review later. It should not be a green message that vanishes when the import window closes.

Run the rehearsal in a workspace that cannot email real recipients. Imported forms and automations can be active even when a team informally calls the workspace a test account.

1. 01

   Freeze

   Pause nonessential edits to fields, tags, forms, segments, campaigns, and journeys. Record the final export time and owner.

2. 02

   Authenticate

   Verify sending domains, DKIM, SPF relationships, DMARC alignment, tracking, replies, and webhook endpoints before moving traffic.

3. 03

   Import safety first

   Load opt-outs, complaints, bad addresses, and manual exclusions before eligible contacts or schedules.

4. 04

   Move a small cohort

   Start with internal and low-risk recipients. Compare the exact audience, exclusions, content, headers, links, and provider events.

5. 05

   Reconcile

   Record intended, excluded, accepted, delivered, failed, and unresolved recipients for every cohort.

6. 06

   Expand or stop

   Increase volume only after the previous cohort matches the plan. Pause when a difference cannot be explained.

A rollback is not a second send from Mailchimp. It is the ability to stop new work, restore one authoritative source for forms and integrations, reconcile what already happened, and resume without repeating a message.

Keep the old account read-only while support, finance, marketing, and privacy teams may still need campaign reports, templates, permission evidence, invoices, or delivery history. Export what your organization is allowed and required to retain before plan or account changes remove access.

Before closure, verify that no form, store, CRM, application, webhook, scheduled export, campaign, or journey still writes to or sends from Mailchimp. Revoke users, keys, and connected apps in a controlled order. Remove DNS records only after legitimate traffic from the old system has ended.

Moosewave's migration workspace organizes the same sequence around inventory, mapping, dry runs, exceptions, controlled cutover, verification, and rollback evidence. Review the integration directory for the systems that must keep writing after the move, then use the product walkthrough to see the connected customer record in context.

The completion test is simple: nobody became more emailable by accident, and the team can show why every migrated person is or is not eligible for the next message.

• Mailchimp: About Your Contacts. Current definitions for subscribed, unsubscribed, non-subscribed, cleaned, pending, archived, and deleted contacts.
• Mailchimp: View or Export Your Contacts. Audience, segment, tag, and group export steps, plus the fields and separate contact-state files in an export.
• Mailchimp: Export and Back Up Account Data. The wider account export for audience data, campaign content, reports, templates, and other account records.
• Mailchimp: About Unsubscribes. How opt-outs work and the fact that Mailchimp treats audiences independently.
• Mailchimp: Getting Started with Groups. Mailchimp's description of groups as contact-facing categories and preferences.

Sources checked 28 August 2026. Product behavior and documentation can change, so the linked primary source takes precedence if it differs from this article.