The Definitive Guide to Migrating to Mailchimp

Mailchimp was founded in 2001 by Ben Chestnut and Mark Armstrong in Atlanta, Georgia, with Dan Kurzius later joining; it was acquired by Intuit in 2021 and now operates as Intuit Mailchimp under the Rocket Science Group subsidiary ¹. The product began as a side feature of a web-design agency and grew into one of the largest email-and-marketing-automation platforms in the small-to-mid-business segment.

The typical Mailchimp customer is a marketing team — solo founder up to 50 marketers — that wants email campaigns, signup forms, basic automation and e-commerce-aware segmentation without standing up a Marketo-style admin function. Compared with Klaviyo, Mailchimp positions itself on broader template tooling and a flatter pricing entry point; compared with HubSpot Marketing Hub, it positions on faster time-to-value and a marketing-first feature set rather than a full CRM overlay.

The shapes of migration that actually land on Mailchimp tend to fall into four patterns. First, Constant Contact and AWeber exits — long-time small-business senders moving for better automation and a stronger free tier. Second, e-commerce consolidations, where a store running Shopify or WooCommerce wants its abandoned-cart and post-purchase flows on one platform ³⁰.

Third, homegrown-list rescues, where a newsletter or membership site has accumulated subscribers in a database, MySQL table or a previous SaaS that is shutting down. Fourth, multi-audience consolidations, where a team that created several audiences for different products now wants one primary audience with tags and groups.

Each shape has a different difficulty profile: a Constant Contact move usually has clean field parity but messy tag-versus-segment intent, while a homegrown migration has rich behavioural data that needs to be re-shaped into Mailchimp's event model.

What makes migrating *to* Mailchimp easier than the category average is the import tool itself — it accepts CSV, TXT, XLS and XLSX files and supports paste-from-spreadsheet for ad-hoc loads ²⁹.

What makes it harder than the average is the audience-based pricing model, which can punish teams that import a duplicate contact across multiple audiences and have them billed twice, and the merge-field-per-audience schema, where each audience has its own set of custom fields and there is no global property catalogue to share across audiences.

Customer Journeys, segments and campaign history do not import — they are rebuilt from documentation. Teams that scope for that work up front finish on time; teams that assume parity do not.

Teams that scope for the rebuild work up front finish on time; teams that assume parity do not.

Mailchimp's data model is built around the audience — historically called a list — and everything else hangs off it. A contact lives inside exactly one audience; merge fields are defined per audience; tags, groups and segments all operate within an audience boundary. This is the single most consequential design decision you inherit on day one.

Before you can map a field on the source side, you need to know which audience the row belongs in, what merge fields it requires, and which value will serve as its upsert key. The table below summarises the objects you will touch in a Mailchimp migration.

Contacts use email address as the default unique identifier — two rows with the same email in the same audience collapse into one record on import, and Mailchimp documents that duplicates across multiple audiences increase costs because each audience-membership counts separately.

Audiences themselves have no natural key beyond an internal ID, so re-importing a contact into the wrong audience does not merge across audiences — it creates a second contact-membership and a second line on the bill. Plan the audience consolidation decision before the first row is loaded.

Merge fields are the closest thing Mailchimp has to typed custom properties, and they are scoped to a single audience ⁶. The catalogue below covers what you can model and the limits you need to plan around.

Mailchimp does not have a multi-select picklist merge-field type. Practitioners migrating Salesforce multi-select picklists into Mailchimp map them into a single text merge field with values separated by commas or semicolons, then build segment rules using *Contains* operators against that text.

Relationships in Mailchimp are flat by design. There is no native parent-child object model — no Companies linked to Contacts, no Deals linked to anything. The closest you get is the e-commerce schema, where a Store has Customers, Orders and Products, but these are managed through the platform-integration layer rather than the contact import flow ³³. Tags, groups and segments substitute for relationships in marketing-only scenarios; if you need true relational modelling, Mailchimp is the wrong tool.

The single best predictor of a clean Mailchimp migration is how much work you do on the source side before the first import button is pressed. Mailchimp itself publishes a seven-step checklist that emphasises permission, cleansing and authentication ahead of the load, not after ⁸².

The single best predictor of a clean migration is how much work you do before the first import button is pressed.

Treat the source export as raw material that needs to be shaped to Mailchimp's expected formats — email lowercased, phone normalised to E.164, tags pre-split into the columns Mailchimp expects, dates rewritten to YYYY-MM-DD, and merge-field tags pre-named to fit the ten-character limit.

Source-side prep

• Audit and dedup the source database before export — third-party tools like Insycle are built specifically for Mailchimp-bound dedup and can find email-case-only duplicates and cross-audience duplicates that Mailchimp's importer will not catch on its own.
• Normalise emails to lowercase, trim whitespace, and strip role-based addresses (info@, sales@) that you do not want flooding marketing audiences. Mailchimp lowercases on import but matches before you can intervene.
• UTF-8 encode every file — Mailchimp's importer routinely rejects files saved with Windows-1252 or Latin-1 encoding, and the error message gives no hint about which row ⁶⁹. Save CSVs as UTF-8 from Excel, Google Sheets or whatever generated them.
• Pre-split tags into a single comma-separated column and quote any tag value that itself contains a comma — for example, the tag Monday, Wednesday must be written as "Monday, Wednesday" to survive CSV parsing ¹⁸.
• Decide which audiences you actually need before importing — most teams should consolidate to a single primary audience with tags and groups, because duplicates across audiences inflate the contact total and the bill.

Destination-side prep

• Create the destination audience(s) first and configure default from-name, default from-email, default subject line, permission reminder, contact address and physical mailing address — Mailchimp will not let you send a campaign without these and the audience-creation step is faster done in advance than mid-migration.
• Pre-create every merge field on the right audience with the right type — Text vs Number vs Date matters because Mailchimp will store the value as the type you defined and a mismatched import row will be silently coerced or rejected.
• Provision users and seats before importing — Free includes 1 seat, Essentials 3 seats, Standard 5 seats, Premium unlimited ²⁹. Owners, admins, authors and viewers each have different field-edit and audience-edit permissions.
• Authenticate your sending domain (SPF, DKIM, DMARC) before the first campaign — Mailchimp's own migration checklist flags this as the prerequisite for protecting deliverability through the platform switch ⁸².
• Approve your SMS audience application if SMS contacts are in scope. SMS contact import is gated behind a separate approval workflow inside Mailchimp before the SMS Phone Number field will accept rows ⁷⁹.

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every team that touches the email program. Train campaign creators on Mailchimp's Customer Journeys builder, template editor and segment builder before go-live, not after. A typical small-list migration of under 5,000 contacts runs one to two business days; a multi-audience consolidation with deep automations runs two to four weeks of elapsed time ⁷⁸.

Mailchimp exposes multiple load paths and the right one depends on dataset size, audience mix, and whether you need to re-run idempotently. The UI Import Tool covers most one-shot migrations under a few hundred thousand contacts. Third-party tools sit on top and add staging, transformation and dedup layers.

UI Import Tool

The native import lives inside the Audience → Contacts → Add contacts → Import contacts flow ⁶⁶. There are several modes: Upload a file (CSV, TXT, XLS, XLSX), Copy and paste from a spreadsheet, Enter info directly into the import table, or Import from a connected app such as Shopify, WooCommerce, Eventbrite or Salesforce. Each import step requires confirming the target audience, optional group memberships, optional tags to apply to every row, and a column-to-field mapping screen.

Mailchimp accepts CSV, TXT, XLS and XLSX. The only fields it strictly requires are email address for email contacts and SMS phone number for SMS contacts; everything else is optional ⁴⁴. Some European spreadsheet exports separate fields with semicolons rather than commas — Mailchimp will reject these as malformed unless you re-save with commas.

The right call: UI for one-shot loads under 100k contacts on a single audience, or any time you want a visual mapping review and a 24-hour Import History page to confirm the result ⁷².

Third-party staging tools

Tools like Fivetran, Airbyte, Stitch, Skyvia and Matillion sit between the source and Mailchimp. They are commonly used in two ways: (a) reverse-ETL where the source database is loaded into a warehouse, transformed in SQL, then synced into Mailchimp; and (b) staging-and-validate, where the tool handles file generation, encoding fixes, type coercion and dedup before the result is fed to the import flow.

For one-time migrations the value is in repeatability under failure; for ongoing syncs (the post-migration phase), they become the system of integration.

Mapping is where every migration earns its scars. The decisions you make in your mapping spreadsheet determine whether segments work on day two, whether Customer Journeys fire correctly on day five, and whether your marketing team trusts the data on day thirty.

Work audience by audience, with merge fields and groups created first, then contacts, then tags, then activity. If you are consolidating multiple source audiences into one Mailchimp audience, plan the master-audience design before any rows go in.

Contacts and merge fields

Each merge field has a short tag (the merge token, like FNAME or BIRTHDAY) capped at ten characters and a longer display name. Name the tags before the import — renaming later does not retroactively update content that already referenced the old tag.

Tags vs Groups vs Segments — the three classification systems

Mailchimp gives you three different mechanisms for organising contacts and each behaves differently. Tags are free-text labels applied by you, the operator, and are invisible to subscribers. Groups are subscriber-managed preferences, exposed on signup forms and the update-profile page, and live inside named categories. Segments are saved filters over the union of merge fields, tags, groups and activity, and they can be static (a frozen list) or dynamic (re-evaluated when the campaign sends) ³⁶.

The mapping decision is rule-based: if the source data was an operator label (vip, 2024-customer, webinar-attendee-2025), it maps to a tag. If it was a subscriber choice (Newsletter Preferences: Weekly), it maps to a group. If it was a derived filter (opened any of the last 5 campaigns), it is a segment that does not import — it is rebuilt in Mailchimp's segment builder.

Audience consolidation strategy

Most teams arriving at Mailchimp with multiple existing audiences benefit from consolidating to one primary audience plus tags or groups ¹¹⁴. The audience-based pricing model bills a contact in two different audiences as two contacts, so a 20,000-contact list duplicated across three product audiences shows up as 60,000 on the bill. Mailchimp's *Combine Audiences* tool exists for exactly this scenario but only after you have backed up every source audience first.

If you genuinely need multiple audiences — for example a B2B prospect list and a B2C customer list with completely different merge fields and compliance posture — keep them separate, but accept that segments cannot span audiences and reports are scoped per audience.

Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one into merge fields. Mailchimp's per-audience merge-field count caps at roughly 80 in practice, and every extra field is one more thing to maintain across signup forms, segments and Customer Journeys. Migrate only the merge fields used by an active segment or campaign in the last 12 months.

For picklist source fields whose values do not match a destination dropdown, either: (1) collapse adjacent values during transform, (2) map to a text merge field and accept that segment filters use string equality, or (3) build the values as a Mailchimp Dropdown merge field if the set is small and stable.

Calculated source fields (formulas, scores) do not import — Mailchimp does not have a formula-field type, so values are rewritten on each export from the source or recomputed by a downstream tool.

Campaigns, Customer Journeys and segments

Campaign sends do not migrate as historical objects — there is no way to backfill a campaign record into Mailchimp's reporting. What you can preserve, when migrating from a connected source such as another email provider, is per-contact engagement metadata: import a last_open_date, last_click_date, open_count_legacy and click_count_legacy into custom merge fields so segments built off historical engagement still work on day one ¹¹⁶.

Customer Journeys — Mailchimp's automation builder, which replaced the legacy Automations product — do not import either. Recreate the journey structure manually using Mailchimp's starting points (signup, tag-added, e-commerce events, date-based) and rewire the steps from documentation. Single-email automations are available on Essentials and up; deeper multi-step flows require Standard or Premium ²⁹.

Segments are filters, not data — they regenerate themselves when the underlying contact data is present. Document each source segment as a filter expression in your mapping spreadsheet, then recreate them in Mailchimp's segment builder after contacts and tags have loaded.

E-commerce store, orders and products

Mailchimp's e-commerce data model covers Stores, Customers, Orders and Products. There is no CSV import for orders — they go through the platform integrations. The pre-built Shopify, WooCommerce, BigCommerce, Square and Magento connectors populate these objects automatically once connected.

For manual e-commerce migration — a custom store or a deprecated platform — build a load that creates the store first, then customers, then orders. Order status, currency, total, line items and timestamps round-trip cleanly, but discount codes and gift card balances do not have first-class fields and need to be modelled as custom data.

Files, attachments and content assets

Mailchimp's File Manager hosts images, audio, video and documents that you reference inside campaigns ¹⁰⁴. There is no bulk-attachment-to-record concept — files do not attach to contacts. Migrate inline assets used by templates by re-uploading them to File Manager, then rewrite template HTML to point at the new URLs.

Email templates themselves do not transfer cleanly from another platform. Mailchimp warns about formatting issues from rich-text paste — the *Paste from Rich Text* editor and the *Clear Styles* button exist specifically because copying from Word, Outlook or another email tool brings in formatting that breaks rendering ¹⁴¹¹⁴². The cleaner path is to rebuild templates from scratch in Mailchimp's drag-and-drop or Classic Builder, then validate in a litmus-style preview before sending.

Audit trail, ownership and original timestamps

Standard subscriber system fields — timestamp_signup, timestamp_opt, last_changed, member_rating — are Mailchimp-managed and cannot be overwritten on import. If you need to preserve original signup or consent timestamps for GDPR audit purposes, the pattern is to create custom date merge fields *LEGACY_SIGNUP* and *LEGACY_CONSENT* and populate them from the source export.

Mailchimp does not expose per-field change history at the contact level — there is no equivalent to Salesforce Field History Tracking. Account-level activity is visible via the Account Activity feed and the Audience Activity report, but practitioners building compliance trails for regulated industries typically export to a warehouse on a daily schedule and treat the warehouse as the immutable record.

Compliance — GDPR, CASL and marketing permissions

Mailchimp ships GDPR-compliant signup forms with per-channel marketing-permission checkboxes — email, customised email, direct mail, online advertising, and so on — and surfaces these on the contact profile ¹²²¹²⁹. Migrating consent state requires importing each permission as a column with a boolean value plus a gdpr_marketing_permissions_*_timestamp companion column where possible. Without those, Mailchimp imports the contact as marketing-eligible by default, which is the wrong outcome under GDPR.

Mailchimp is SOC 2 and GDPR compliant; it is not HIPAA-compliant for the Marketing product¹²⁶. If you are migrating healthcare or PHI-adjacent data, Mailchimp is the wrong destination — neither the Marketing product nor the Transactional product offers a Business Associate Agreement on the standard plans.

Validation is the bridge between the import finishing and the first campaign going out. Mailchimp's own migration checklist recommends a phased approach — protect deliverability with domain authentication, send a low-volume warm-up campaign, then ramp to full audience sends only after engagement signals are healthy ⁷⁸⁸². The most reliable single signal is having a marketing operator verify a sample of records they personally know better than any reconciliation script.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before the first campaign send.

• Total contacts imported per audience vs source — minus deliberately excluded rows (role-based emails, bounced lists, opt-outs, GDPR-non-consenting contacts).
• Cross-audience duplicate count — count distinct emails across all audiences and compare to the sum-of-audience-counts; the delta is the cross-audience duplicate inflation that drives billing.
• Tags applied per contact — for each tag in the source, count contacts in Mailchimp that carry it and compare to source row counts to catch comma-parsing failures from the tag column.
• Group memberships — sample 50 contacts who should belong to specific groups and verify in the contact profile that group categories and selected groups round-tripped.
• Merge-field non-null density — for every merge field, calculate the percentage of contacts with a non-empty value in source and in Mailchimp; large drops point to type mismatches or truncation at the 255-byte limit.
• Marketing-permission state — count contacts with each GDPR marketing permission enabled vs the source consent table; any drift means the migration trip-defaulted some contacts to non-consenting and they will not receive sends.
• Customer Journey enrolment — for any journey that auto-enrols on tag-added, count contacts currently enrolled and compare to the expected initial population.

On top of reconciliation, run a manual spot-check protocol: pick 30 random contacts across audiences and verify each merge field, tag and group against the source UI. Send a single-recipient test campaign to a verified internal email and confirm merge tags render correctly — *|FNAME|* resolving to a blank string is the most common sign of a mis-mapped column.

Mailchimp ships an Undo a contact import action from the Import History page — clicking the rollback option removes the affected contacts from the audience ⁹⁴. This works within 24 hours and only for the standard UI import flow.

The real rollback strategy remains: export every audience to S3 before the import starts, stamp every imported contact with an *IMPORT_BATCH* custom merge field, and if catastrophe strikes, archive by batch ID via POST /lists/{list_id}/members/{subscriber_hash}/actions/archive and re-import from the cleaned source.

Cutover sequencing: (1) source goes read-only and the team is notified; (2) final delta export captures everything that changed during the test-import window; (3) delta is imported with the same merge-field mapping; (4) reconciliation runs; (5) a low-volume warm-up campaign goes to the most-engaged 10 percent of contacts; (6) deliverability metrics (open rate, bounce rate, complaint rate) are reviewed; (7) full audience sends resume; (8) source decommission is scheduled for 30 to 90 days out, never the same day.

Mailchimp's Pro Partner program lists certified experts who specialise in setup, migration, template design, automation and integration work — there is a global directory at mailchimp.com/experts with filters for region, certification level and specialisation ¹³⁷. Top-ranked Pro Partners (Chimpology and similar) carry deep experience with multi-audience consolidation, Klaviyo-to-Mailchimp, Constant Contact-to-Mailchimp and homegrown-list migrations.

For migrations specifically, partners with explicit Salesforce-to-Mailchimp, Constant Contact-to-Mailchimp, or e-commerce-platform-to-Mailchimp practices tend to ship cleaner than generalist marketing agencies. Mailchimp also runs Personalized Onboarding as a paid service for new customers above a certain plan tier — included on Premium and available for purchase on Standard.

On the ETL and iPaaS side, Fivetran, Airbyte, Stitch, Skyvia and Matillion all have Mailchimp connectors. Their role in a migration is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that converts picklist values, normalises emails and resolves consent state, and the ongoing-sync layer that takes over once the one-time migration is complete.

Airbyte and Fivetran are common picks for warehouse-first teams; Skyvia is common for direct CSV-from-FTP loads and lighter-weight syncs without standing up a warehouse.

Managed-migration cost ranges vary widely. A clean Constant Contact-to-Mailchimp move of under 25,000 contacts with no historical engagement preservation and a single audience often lands in the £400–£2,000 / $500–$2,500 range with a setup fee plus per-contact pricing.

A multi-audience consolidation from a legacy CRM with deep tag taxonomy, Customer Journey rebuilds, GDPR consent reconstruction and e-commerce store sync typically runs $5,000–$25,000, with the upper end driven by audience count, merge-field complexity and the number of integrations that need rebuilding rather than re-pointed.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Mailchimp migrations and handles the audience consolidation, merge-field design, tag-versus-group classification, GDPR consent reconstruction and validation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on contact count and source platform, with separate line items for cross-audience consolidation and e-commerce store sync so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Mailchimp Pro Partner, paid onboarding, an iPaaS-first approach, or a specialist migration vendor. Explore FlitStack →