How to export your data from Mailchimp

How to export your data from Mailchimp and what stays behind

A renewal, a pricing change or a data residency requirement is usually what forces the move, so the first job is to find out what Mailchimp will actually hand over. Audience exports generally include contact fields, consent and opt-in information, ratings, tags and SMS contacts, which is enough to rebuild a list elsewhere if the consent trail comes with it. Signup source, historical opens and clicks, and purchase history generally do not come out in the audience file, so plan to record what you cannot export before you leave. Confirm the exact export options, file formats and field names in Mailchimp's current help documentation, because these change and the wording here should not be treated as a specification.

Start by listing who in your organization can run an audience export in your account. Mailchimp's permissions are set by user role, and an export is often restricted to account owners or admins, so confirm this with the person who manages the account before the migration window opens. Also check whether the export is available for each audience separately, and whether suppressed or unsubscribed contacts are included, since you will need that status to avoid mailing people who opted out. Export the consent fields alongside the email addresses, because a contact without a recorded opt-in source is much harder to justify importing into a new system.

Mailchimp also limits how long a generated export stays available for download, so treat the download as a time-boxed task rather than a file you can retrieve later. Save each export in its original form, record the date and the audience it came from, and keep a copy in your own controlled storage. Verify row counts against the audience total shown in Mailchimp, and spot-check a sample of records for consent status and tags before you move on. The export is the only copy of that data for many teams, so retain it under the same retention and access rules you apply to other personal data.

Which Mailchimp data you can export and in what format

This table lists the Mailchimp data types you will need to move, how each is typically exported, and what to verify before you start. Use the last column as a checklist for the Mailchimp help pages, since file formats, row limits and download windows can change. Note the rows marked as not included in the audience export, because you will need to rebuild or source that data separately.

Data type	Export method	File format and limits	What to confirm
Audience contacts and fields	Audience export from the audience dashboard	Confirm the file format and any row limit in Mailchimp help	Field names and merge tags that map to listmonk or Mautic fields
Consent and opt-in status	Included in the audience export	Confirm how subscription status values are labeled	Whether opt-in timestamps and proof of consent are present
Ratings	Included in the audience export	Confirm the column format and value scale	What each rating means before you map it to a segment
Tags	Included in the audience export	Confirm how multiple tags are written in one field	The delimiter used, so tags split correctly on import
SMS contacts	Confirm whether they export with the audience or separately	Confirm the format and any separate file limits	SMS consent records and the messenger you will use instead
Campaign reports	Export from the campaign reports section	Confirm formats and whether exports are capped	Whether opens and clicks are summaries or per-contact activity
Signup source, opens, clicks and purchase history	Not included in the audience export	Not applicable to the audience file	Whether a report or connected integration can supply it

What Mailchimp does not export and how to rebuild it

A Mailchimp audience export carries contact fields and consent, but several items that matter for a migration stay behind. Signup source, contact-level engagement and purchase history live in reports, in the connected store, or in the account itself. Agree a workaround for each gap before you close the account.

Signup source

The audience export does not show the form, landing page or integration that added each contact. Record the source before you leave Mailchimp. Check whether signup source is visible in contact profiles or reports, and write what you find into a source field on the new list. If the history cannot be recovered, mark those contacts as legacy so later segments do not treat them as recent sign-ups. Confirm the current contact view in Mailchimp's help documentation before you rely on it.

Opens and clicks

Engagement at the contact level drives suppression and re-engagement rules, so its absence affects deliverability on day one. Campaign reports are separate from the audience file and can be downloaded per campaign. Save the report for every campaign you still need and store it with your campaign archive. Keep the account active until those files are saved, then decide whether your new system can import engagement history at all before you design suppression logic.

Purchase history

Purchase data belongs to the store that took the order, not to the email tool. If a connected store sent purchase events into Mailchimp, the audience export will not give you order history. Pull orders from the store's system of record through its order export or API, and match them to contacts by email address. Keep only the fields your new system needs for segmentation, and ask your privacy lead whether past purchase data can move under your current privacy notice.

Automations and store connections

Automation workflows and the rules that link Mailchimp to a store or other tool sit in the account, not in the contact file. Document each automation by hand, including its trigger, its conditions, its emails and the external system each step depended on. Rebuild only after the audience is imported and tested in the new platform. Confirm with Mailchimp's documentation which automation settings, if any, can be exported as files.

Steps to export your data from Mailchimp in the right order

This sequence produces a complete, checked copy of your Mailchimp audiences, tags, SMS contacts, campaign reports and templates before you change any sending tool. Each step ends with a check so that gaps are found while the source account is still available.

Confirm account ownership and admin roles
Confirm which Mailchimp account holds the audiences and who holds an owner or admin role that can run exports. The person doing the export should be the account owner or an admin with access to every audience in scope, so no list is skipped. Ask the account owner to confirm this in writing and note any sub-accounts or agencies with access. Check current export permissions in Mailchimp's help documentation before you begin. Check: the person running the export can open each audience and see its contact count on the dashboard.
Export each audience with all fields and consent data
Open each audience and start an export of all contacts with every field, including the consent and opt-in information the export offers. Export options can change, so confirm which consent fields appear in the file before you run it. Save each file with the audience name and export date in the file name. Check: open the file, confirm the header row lists the expected fields, and compare a sample of records with the consent values shown on individual contact profiles.
Export tags and SMS contacts separately
Confirm whether your standard audience export includes tags and SMS contacts, then export them as separate files if it does not. Use the tag or segment view to export the contacts for each tag, and export SMS contacts from their own list if your account has SMS enabled. Record which tags were exported and which were skipped. Check: compare the tagged and SMS counts with the figures shown in the dashboard, and match a few tagged contacts back to their profiles.
Download campaign reports and templates
Export the reports for each sent campaign and save the source of each template. These files cannot be imported into listmonk or Mautic directly, but they record the send history, subject lines and layouts you will need when you rebuild campaigns. Note which reports include opens and clicks, because engagement data may be available only in campaign reports and not in the contact export. Check: confirm every campaign you need to keep has a report file and a template file, and that the file names match the campaign names.
Store the files in a controlled location
Move all export files to an encrypted storage location that only the migration team can access, with access logging where your platform supports it. Keep the original exports unchanged and work only on copies. Record the storage location, file owner and retention period in your migration log. Check: restore one file from the storage location to a second machine, confirm it opens, and compare its checksum with the value recorded when it was first saved.
Record row counts for each list
Create a manifest that lists each audience, tag and SMS file with its row count, export date and the person who ran it. Exclude the header row from each count, and record separately any unsubscribed, cleaned or archived contacts, confirming whether your export includes them. Check: the manifest totals should match the dashboard counts for each audience. Keep this manifest as the baseline you compare against after import.

How exported fields map to listmonk or Mautic

listmonk is organized around subscribers and lists, so a Mailchimp export maps to two structures: subscriber records and list membership. Every subscriber needs an email address, and the remaining columns are stored on the record or as attributes that you can query later with SQL expressions.

Subscribers: Each row becomes one subscriber keyed by email address. Keep the name and custom field headers consistent so you can read them back without guessing.
List membership: Map each Mailchimp audience or segment to a listmonk list. Lists are the unit you send campaigns to, so decide in advance whether a contact should belong to several lists.
Opt-in status: Choose single or double opt-in for each destination list. Imported contacts should keep the status they had in Mailchimp, and any move to unconfirmed status should be a deliberate decision with a communication plan.
Attributes: Store fields with no built-in home as attributes, so later segments and queries can use them without a schema change.

Before a full import, load a small sample of rows and check the subscriber count, list membership and status on each list. Confirm the current import options in the listmonk documentation, since they determine how headers and attributes are read.

Mautic imports contacts from CSV through its user interface and matches columns to contact fields automatically. For large files, the project recommends running the import in the background with the mautic:import console command, which Mautic processes in batches of 100 rows by default.

Automatic column mapping: Mautic suggests a field for each header. Review every suggestion before importing, because a header that matches the wrong field will write data to the wrong place.
Fields first: Create any custom contact fields you need before the import, so headers from the export have a target to map to.
Interface import: Suitable for smaller files. You upload the CSV, check the mapping and run the import from the browser.
Background import: For large files, run mautic:import from the server. The import depends on cron, so confirm that your scheduled jobs are configured as described in the Mautic cron jobs documentation.
Tags and segments: Tag the imported group at import time so you can identify it afterward and build segments from it.

Run a test file through the same mapping first and compare the contact count and a sample of field values. Confirm the batch size and command options against the version you install, because defaults can change between releases.

Who can run the export and what access it requires

The export needs a Mailchimp account role that is allowed to access audience data, and that permission decides who can produce the file in the first place. Before anyone clicks export, confirm in your own account which roles Mailchimp grants for audience exports, since role names and permission sets can change. Check also whether the role can export the full contact record, including consent and tag fields, or only a reduced view. A user who can see the audience but cannot export the consent fields will produce a file that is missing the evidence you need for an opt-in migration.

Agency staff, freelancers and shared logins complicate the audit trail. If the export is run under a shared login or by an agency account, you may not be able to show later which person produced the file, when, and for what purpose. Ask the agency to export under a named account with its own credentials, and record the date, the audience name, the export type and the requester in your migration log. Confirm with Mailchimp whether its account activity records show audience exports by user, and keep a copy of those records with the migration evidence.

Treat the exported file as personal data from the moment it is downloaded. Store it in an encrypted location with access limited to the few people who run the import, and avoid email attachments and unmanaged laptop folders. Set a retention rule for the file, then delete every local, shared drive and ticketing attachment copy once the import into listmonk or Mautic has been verified against record counts and consent status. Deleting copies on your side does not remove data from Mailchimp, so decide separately whether the source audience will be kept, archived or closed, and document that decision.

What to plan before the Mailchimp contract ends

Several dates and ownership questions decide how much of your audience and automation history you keep. Settle them with Mailchimp and inside your organization before the contract ends, because a missed export window or a stopped sending account can leave you with a list you cannot send to.

Export window and file availability

Confirm with Mailchimp how long exported files stay available for download after you request them, and whether the account keeps access to the export tools after billing stops. Ask whether the window depends on plan or account status. Your team should decide who owns the download, where the files are stored, and who checks that each audience export opens and contains the expected row count before the window closes. Keep a dated record of every export you run.

Date the account stops sending

Ask Mailchimp the exact date sending from the account ends, both for campaigns and for automated emails such as welcome series and abandoned-cart messages. Your team needs to decide the last campaign to send from Mailchimp and the first send from your new platform, so subscribers are not emailed twice or left without messages for a gap. Plan the cutover around the time zone your sending schedule uses, not only the date on the invoice.

Freeze on list edits during export

Ask Mailchimp whether unsubscribes, bounces and new signups keep updating audience records while you export, and how those changes appear in files you download earlier. Decide internally whether to pause imports, tag changes and manual list cleanup for the export period. A frozen snapshot makes the consent and status fields in your exports consistent with each other, which matters when you rebuild opt-in records on the new platform.

Sender domain and DNS ownership

Confirm which domain and sending subdomains are registered to the Mailchimp account and who holds the DNS records for SPF, DKIM and DMARC. Your team should decide whether the domain stays with your organization or is delegated to a new sending service, and who approves DNS changes. Removing Mailchimp's records too early can break authentication for mail still in flight, so plan the DNS changes as their own step with a rollback path.

Automations, templates and forms inventory

Before the account closes, list every automation, journey, template, landing page and signup form in the account, along with the audience each one reads from. Mailchimp exports cover contacts, but they may not carry the logic or design of these assets, so ask Mailchimp which of them can be downloaded and in what format. Your team should decide which ones to rebuild on the new platform and which to retire, since rebuilt automations need the same trigger and timing logic.

Stop date for paid features

Ask Mailchimp which features stop working at the end of the paid term, such as advanced segmentation, send-time optimization, custom domains or extra contact tiers, and whether any feature stops earlier than the account closure date. Your team should decide which paid features your migration still depends on and sign off on the last day you need them. Plan to finish reports and analytics exports before those features switch off, because historical reporting may not be available afterward.

Keeping consent records when you move contacts

Consent status and consent evidence are two different records, and a Mailchimp audience export only gives you the first. The export can show a value for each contact, such as whether they are subscribed or unsubscribed, along with fields and tags you have set up. It does not, by itself, show how or when that person agreed to receive email, which form or page they used, or the wording they saw. Treat the export as a snapshot of status, and decide before you export where the supporting evidence lives, whether that is in Mailchimp's own signup records, your web forms, your CRM or your consent management tool.

Before you move any contact into listmonk or Mautic, confirm with your legal or compliance team which consent records you are required to keep, how long they must be retained, and who may access them. This is a question for them, not for the migration team, and this guide does not give legal advice or describe any regulatory outcome. Ask them specifically whether the status values in the export are sufficient for your obligations or whether you must also retain signup source data, timestamps and form versions from your original systems before the Mailchimp account is closed.

Store the export as a dated, read-only record together with its metadata: the export date, the Mailchimp account and audience name, the person who ran the export, the file version, and a note of which fields were included. Keep a copy of the file in your own controlled storage so it remains available after you cancel Mailchimp. Use **consent evidence** labels in your inventory so auditors can see which records came from which system. When you later import into listmonk or Mautic, record the import settings used, such as the list or segment each contact was placed in, so the destination's opt-in state can be traced back to the source file.

Questions about exporting your data from Mailchimp

How much effort does a single Mailchimp audience export take?

A single audience export is a short download, but the effort around it depends on how much review the audience needs first. The time goes into checking what came out and deciding what moves to the new platform. Plan time for three tasks: reviewing field names and tags, confirming that consent records are complete, and deciding which contacts are safe to import. Inventory your lists and segments before you export, because each list adds a review step. An audience with a long history of imports and manual edits usually takes longer to review than a clean, recently built list.

What drives the cost of a Mailchimp export project up?

The download itself is rarely the expensive part. Cost depends on the work around it, and the main drivers are the number of lists and segments, the number of custom fields and merge tags, how much consent cleanup is needed, and how far verification goes. Verification might mean checking that imported records keep their original opt-in status and that row counts match. Each driver adds review time. Export and cleanup are one-time costs, while hosting, sending infrastructure and support recur after cutover. Ask any provider to price each driver separately in the written scope so you can see which choices move the total.

Can our own team run the Mailchimp export without outside help?

Yes, a competent administrator can export a small audience alone. The export is available inside the Mailchimp account, and the destination platform has its own import path. Mautic's documentation describes CSV import through the user interface with automatic column to field mapping, and a background import through the mautic:import console command for large files. Outside help usually adds the most value in consent review, field mapping decisions and import validation, where mistakes are expensive to fix later. Decide early which parts your team will handle and which you will hand over, and confirm that the person doing the export has the permissions they need.

What does the work need from the Mailchimp account owner?

The account owner, or an administrator with the right role, needs to authorize the export, confirm which audiences and fields are in scope and approve any changes to consent records. Expect to share access to the account, a list of sending domains and any integrations connected to it, so the team can see what data flows where. Confirm who holds the contract, because export rights and data handling terms sit with the account. Name who signs off on the scope and who answers questions about legacy lists. Agree these roles in writing before the export so nobody discovers a missing permission during cutover.

How long do we have to download a Mailchimp export, and how do we confirm it?

Mailchimp's export window is documented as 30 days, but confirm the current period in your own account before you start. Treat that window as the deadline for keeping a complete copy, not as the deadline for finishing the migration. Download the file as soon as it is ready and store it in an encrypted location you control. Record the file name, row count and export date, then compare the row count with the audience size shown in the account. If the file is incomplete or the window has closed, request a new export. Check Mailchimp's own help documentation for current terms, since windows and file formats can change.

Can signup source and engagement history be recovered after a Mailchimp export?

Generally not from the audience export alone. An audience export is designed to carry contact fields, consent status and tags. Signup source, opens and clicks, and purchase history usually live in reports or in connected systems, so check what your account offers before assuming it is lost. Some of this history may be available through campaign reports or a separate export. Do not assume the new platform will carry historical engagement over. Confirm this for your own data during planning, decide whether historical activity matters for segmentation, and keep the Mailchimp reports and any connected store data as archives.

What should a quote for a Mailchimp export include?

A quote should follow from a written scope that names the lists and segments in scope, the fields to be mapped, the consent records to be reviewed, the verification method and the acceptance criteria. It should separate one-time work, such as export, cleanup, mapping, import testing and cutover, from recurring items such as hosting, sending infrastructure, monitoring and support. Ask for the assumptions behind each line, including what the provider will not do, such as legal review of consent wording. Ask how files are stored and deleted and what happens if an export is incomplete. DeployOpen does not publish a price list, and its fixed-scope quotes follow from deliverables agreed before work starts.

How DeployOpen scopes and delivers a Mailchimp data exit

DeployOpen plans and delivers a Mailchimp data exit as a fixed-scope engagement inside your own infrastructure. We agree in writing which audiences, consent fields and tags are in scope, then document what the export does and does not contain before anyone moves a subscriber record.

How we scope

Inventory every audience, tag, segment and SMS contact list that must leave Mailchimp
Confirm which consent and opt-in fields your legal and compliance owners require in the export
Record the gaps in advance, such as signup source, opens, clicks and purchase history, and agree how they are handled

How we build

Run the export from an account owner or admin role and validate row counts against each Mailchimp audience
Load the extracted files into your target platform in a test environment and check field mapping and consent flags
Test suppression and unsubscribe handling so previously opted-out contacts stay excluded after import

How we hand over

Deliver a written record of each export file, its source audience, its date and the fields it contains
Document the exclusions and the data that stayed in Mailchimp so your team knows what was not moved
Set the retention and deletion steps for the exported files in your own storage, as agreed in the scope

How we support

Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts
Ongoing support, upgrades and continuous testing are available as a retainer after handover
Quotes follow from the written scope, so ask for line items covering export, validation, documentation and handover

How to export your data from Mailchimp