Skip to content
Get a quote

Migrate to Mailchimp

Mailchimp is an email-marketing-native platform whose audience-based pricing, merge-field-per-audience schema and tags-versus-groups-versus-segments architecture punish teams that import before consolidating lists and pre-creating fields.

Short answer

FlitStack AI migrates pipelines, contacts, and deals into Mailchimp from 850+ CRMs. Every field is mapped to Mailchimp's objects, history and associations come across, the Mailchimp setup is configured alongside, and the whole migration stays reversible in one click.

By

From Your system
DestinationMailchimp
850+ sources mapped into Mailchimp

What Mailchimp supports, and where its import tools stop

  • Generous free tier with up to 500 contacts allows small teams to validate email marketing before committing to a paid plan.
  • Intuitive drag-and-drop email builder and 130+ templates let non-technical users produce professional campaigns without HTML or CSS knowledge.
  • 300+ native integrations, especially Canva and Shopify, make it easy to connect existing tools without custom development work.
  • Detailed open-rate, click-through, and campaign analytics give small businesses actionable insights without a dedicated marketing team.
Bulk APIAPI key (account-level or user-specific)
Rate limitsNot publicly documented; varies by plan tier and request type
ObjectSupportNote
AudiencesfullMailchimp's top-level container for contacts. An Audience holds all contacts, segments, tags, and groups. We export each Audience as a separate entity and preserve its settings including opt-in workflow and GDPR compliance fields.
ContactsfullIndividual subscriber records within an Audience. We export all standard fields (email, name, phone, address) plus merge field values. Status (subscribed, unsubscribed, non-subscribed, cleaned) is preserved as a required field.
SegmentsmappedDynamic filters applied to an Audience. Segments depend on Mailchimp's filter syntax which is not portable. We export the segment rules as structured data and apply equivalent filters in the destination where supported.
TagsfullFreeform labels applied to individual contacts. We preserve all tag names and their contact associations. Tags migrate 1:1 to most destination platforms as simple label fields.
GroupsmappedGroupings within a Category that a contact can belong to. Groups require their parent Category to exist first. We export both and maintain the relationship during import.
CampaignsmappedThe sent email, automation, or ad record. We export campaign metadata (name, subject, send date, recipient count) and content as HTML. Automated workflows require manual reconstruction in the destination.
AutomationsnoneMailchimp's triggered workflow engine (Welcome emails, abandoned cart, birthday, etc.) stores logic that cannot be exported. We export a list of active automations with their trigger conditions and enrollment counts so the customer can rebuild them manually.
TemplatesmappedStored email designs used for campaigns. We export templates as HTML files. Destination platform rendering varies; complex Mailchimp-specific blocks may require manual adjustment.
Merge FieldsfullCustom contact properties beyond the standard fields. We preserve all merge field names, types, and values per contact. Field order and display labels are noted for destination mapping.
Email ActivitymappedIndividual open, click, bounce, and unsubscribe events per contact. We export the last 90 days of activity by default. Full history may require pagination across multiple API pages.
ReportsmappedAggregate campaign metrics (open rate, click rate, revenue). We export report summaries as structured data. Visualization preferences do not carry over.
API KeysfullPer-user authentication credentials for the Marketing API. We use the customer's account-level or user-specific API key to authenticate export requests. Keys must remain active during migration.
E-Commerce DatamappedOrders, products, and customers synced from Shopify or other connected stores via Mailchimp's e-commerce integration. Requires the connected store to remain linked during migration; otherwise only product names and order IDs export without reference data.

The Mailchimp migration guide

Why teams migrate to Mailchimp

The four shapes a Mailchimp migration takes, and what makes the platform easier — or harder — than the category average.

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 subsidiary1. 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 platform30.

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 loads29.

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.

The Mailchimp data model you need to map into

Audiences, merge fields, tags, groups and segments — the destination schema decoded for anyone planning a mapping spreadsheet.

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.

ObjectWhat it storesRequiredTier
Audiences (Lists)Top-level container — a self-contained world of contacts, fields, tags, segmentsAudience name, default from-email, default subject lineFree: 1; Essentials: 3; Standard: 5; Premium: unlimited29
Contacts (Members)Individual subscribers — email or SMS contacts inside an audienceEmail address (or SMS phone number for SMS contacts)All tiers; counts against audience-based pricing
Merge FieldsPer-audience custom fields — first name, last name, birthday, custom dataTag (≤10 chars), name, typeAll tiers; per-audience scope (no global properties)
TagsFree-text labels applied to contacts within an audienceTag name (≤100 chars)All tiers; up to ~5,000 tags per audience recommended
Groups (Interests)Subscriber-managed preferences — category + group namesCategory name, group namesAll tiers; up to 60 group categories per audience
SegmentsSaved filters over contacts — dynamic or staticFilter conditions over merge fields, tags, activityAll tiers; saved-segment limits vary by tier
CampaignsRegular, Automation, A/B Test, RSS, Plain text, Reminder sendsAudience, subject, from-name, contentAll tiers; automation flow depth scales with tier29
Customer JourneysAutomation flows replacing the legacy Automations builderStarting point, steps, journey settingsAll tiers (single-email automations on Essentials; deeper flows on Standard+)29
E-commerce Store + Orders + ProductsStore, customer, order, product records synced through Mailchimp's e-commerce integrationStore ID, currency, customer email; per-order: order ID, total, currency, statusAll tiers; integration-only model — no native CSV import for orders

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 audience6. The catalogue below covers what you can model and the limits you need to plan around.

Field typeLimitNotes
Text255 bytes per field valueDefault first-name and last-name fields use this type6
NumberStandard numeric rangeRecommended for age or numeric ID; arithmetic on Zip Code uses Zip Code type
Date / BirthdayYYYY-MM-DD or MM/DD formatBirthday stores month + day only; Date stores year too
AddressComposite field — street, city, state, zip, countryImported as a multi-column block; partial values accepted
Phone / SMS Phone NumberE.164 recommendedSMS audiences require approved application before SMS sends
Dropdown / Radio ButtonsPredefined choice listPicklist-like; choices include gender, days, months, US states, countries
Image / WebsiteURL stringImage stores a URL, not a binary upload
Merge fields per audiencePer-audience scope; no global field catalogueEach audience defines its own set; up to ~80 merge fields typical6

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 flow33. Tags, groups and segments substitute for relationships in marketing-only scenarios; if you need true relational modelling, Mailchimp is the wrong tool.

Pre-migration prep — the work before you touch Mailchimp

What must be true on the source, the destination, and across the team before the first row hits the import 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 after82.

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 row69. 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 parsing18.
  • 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 unlimited29. 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 switch82.
  • 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 rows79.

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 time78.

Import mechanisms: UI wizard, CSV, and staging tools

Multiple paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at scale.

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 flow66. 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 optional44. 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 result72.

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 your data into Mailchimp

The longest section — because field mapping is where almost every migration that fails actually breaks.

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

Common source → Mailchimp Contact mapping
SourceDestinationNote
emailEmail Address (unique identifier)Lowercased on import; primary key inside an audience
first_name / last_nameFNAME / LNAME merge fieldsDefault merge tags; required-field block if column missing on a strict audience
phonePHONE merge field (or SMS Phone Number for SMS audience)Normalise to E.164; SMS audience requires separate approval79
birthday / date_of_birthBIRTHDAY merge fieldMonth + day only — Birthday type strips year
subscribed_at / opted_in_atCapture in a custom date merge fieldMailchimp stamps timestamp_opt; cannot be overridden on standard import
source / utm_sourceSOURCE custom merge fieldNo system source-of-truth field — model in a custom merge field
consent flag / gdpr opt-inMarketing PermissionsEnable per audience; signup forms collect these as separate columns122
language preferenceMMERGE language tag (system) or customMailchimp uses two-letter language codes for content localisation

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)36.

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 groups114. 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.

Multi-source → Mailchimp audience consolidation
SourceDestinationNote
Source audience: "Newsletter"Primary audience + tag: newsletterTag preserves the legacy provenance for filtering and reporting
Source audience: "Customers"Primary audience + tag: customerTag enables campaign exclusion of customers from prospect sends
Source audience: "Webinar attendees Q3"Primary audience + tag: webinar-q3-2025Time-bounded tags are easier to retire than time-bounded audiences
Source audience: "Beta program"Primary audience + group category: "Programs" → group "Beta"Group when subscribers self-select via signup form; tag otherwise

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 one116.

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 Premium29.

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 campaigns104. 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 rendering141142. 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 profile122129. 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 product126. 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.

The pitfalls that derail Mailchimp migrations

Nine specific failure modes — ranked by impact, each tied to the exact Mailchimp mechanism that breaks.

Validation and cutover

What to verify after the import job, in what order — and how to fail safely when something is wrong.

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 healthy7882. 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 audience94. 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.

Migration partners and tools

Mailchimp Pro Partners, iPaaS vendors, specialist migration shops — what each is good for and how to choose.

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 specialisation137. 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 →](/contact)

Mailchimp migration checklist

A phased punch list for moving contacts, audiences, tags, groups, merge fields, customer journeys, and e-commerce data into Mailchimp using its native import tool. Typical timeline: 2–8 weeks.

0. Decide & Plan10 tasks
  • Define migration scope by Mailchimp object. List every object in scope: contacts (email + SMS), audiences, tags, groups, segments, merge fields, customer journeys, classic automations, campaign archives, templates, signup forms, landing pages, and e-commerce store data. Mark each as in-scope or out-of-scope in writing.If skipped: Unscoped objects (especially e-commerce stores and customer journeys) surface mid-migration and extend the freeze window.
  • Decide the audience model: single audience vs multiple audiences. Mailchimp bills per contact, and duplicates across audiences each count separately. Decide whether to consolidate into one primary audience with tags and groups, or keep separate audiences for distinct business units. This decision drives every downstream mapping step.If skipped: Carrying over the source's audience sprawl inflates the contact bill from day one and prevents Mailchimp's default dedup from working across audiences.
  • Decide historical-engagement scope and time horizon. Pick a hard cutoff for opens, clicks, and campaign history (for example: last 24 months). Source engagement metrics do not import natively into Mailchimp's reports — decide whether to preserve them in custom merge fields, attach as tags, or drop.
  • Confirm Mailchimp plan tier and contact ceiling. Free, Essentials, Standard, and Premium have different contact ceilings (250 / 50,000 / 100,000 / higher) and per-audience limits (1 / 3 / 5 / unlimited). Importing past the ceiling forces an upgrade or blocks sends.If skipped: Crossing the contact ceiling places a hold on live sends until the bill is upgraded.
  • Decide whether Mandrill transactional sending is in scope. Mandrill is a separate product with separate billing. If transactional email is part of the move, plan it as a parallel workstream — credentials, templates, and dedicated IP setup do not transfer from the marketing side.If skipped: Treating transactional and marketing as one project conflates two pricing models and two sending surfaces, breaking both.
  • Choose the upsert key for contacts. Mailchimp uses lowercase email as the primary key. Decide how to handle source records with missing or duplicate emails — drop, hold for manual review, or assign synthetic addresses for SMS-only contacts.
  • Document success criteria for the migration. Define falsifiable tests: per-audience contact counts, tag coverage match, merge-field population rate, campaign archive parity, customer journey re-creation completeness, and UAT sign-off from a named owner.
  • Set the cutover date, source-system freeze window, and rollback gate. Pick the date when the old platform goes read-only, the cutover window itself, and the hour by which a no-go call must be made if validation fails.If skipped: Without a pre-agreed rollback gate, partial loads get pushed through and create reconciliation work that takes weeks.
  • Identify legal and compliance constraints. Capture GDPR consent records that must accompany EU contacts, CAN-SPAM unsubscribe lists, CASL express consent timestamps, and any retention or residency rules. Mailchimp is SOC 2 and GDPR-compliant but is NOT HIPAA-compliant — protected health information cannot move into Mailchimp.If skipped: Loading PHI into Mailchimp violates HIPAA and forces a forensic deletion.
  • Document explicit out-of-scope items. Write down what is NOT migrating (cold contacts older than X, unsubscribed contacts beyond the legally required suppression list, dormant audiences, deprecated automations) so it does not creep back in.
1. Pre-Migration Prep25 tasks
  • Export baseline record counts per source object. Capture a snapshot of contact counts (subscribed, unsubscribed, cleaned, bounced), tag counts, segment counts, automation counts, and campaign counts on a known date. This is the reconciliation anchor for Phase 6.If skipped: Without a baseline, post-migration delta investigation has nothing to compare against.
  • Normalize all source email addresses to lowercase. Convert the email column to lowercase before any dedup pass. Mailchimp matches on lowercase email — case-variant duplicates are invisible until normalized.If skipped: Case-variant duplicates collide silently inside Mailchimp and history attaches to the wrong record.
  • Run dedup on source contacts using email as the match key. Strip whitespace, lowercase, then group by email. Resolve duplicates in the source — choose the record with the most complete profile as the keeper.If skipped: Importing duplicates inflates the contact bill and overwrites the most recent profile on each successive load.
  • Flag and review fuzzy duplicates on first name + last name + company. After exact-email dedup, run a second pass on name plus company to surface contacts who switched email addresses. Manual review only — auto-merge typically produces 10–25% false positives in B2B lists.
  • Remove syntactically invalid email addresses. Strip emails missing @ or domain TLDs, with internal whitespace, or with double dots. Mailchimp's import flags these as syntax errors and they fail to load.If skipped: Syntax errors silently skip rows on import without aborting the job, so totals look correct but addresses are missing.
  • Compile the legal suppression list of unsubscribes and complaints. Pull every unsubscribed, bounced-hard, and spam-complaint email from the source. These must be loaded as suppressions in Mailchimp BEFORE active contacts to prevent accidental re-mailing.If skipped: Mailing a previously unsubscribed contact violates CAN-SPAM and CASL and damages sending reputation.
  • Standardize phone numbers to E.164 format with country code. Mailchimp's SMS contacts require the country code as part of the phone number. Convert all numbers to +[country][digits] with no spaces or punctuation.If skipped: Phone numbers without country codes fail SMS delivery and may block the entire SMS contact import.
  • Standardize country codes to ISO 3166 two-letter codes. Convert country names (United States, USA, U.S., US) to a single canonical two-letter code per record.
  • Identify contacts missing required fields per the new audience schema. Flag any contact missing an email (for email audiences) or SMS phone number (for SMS audiences). These are the only Mailchimp-required fields, but missing values block the row.
  • Re-encode all source files as UTF-8. Open each export in a text editor or scripting tool of your choice and confirm UTF-8 encoding. Mailchimp's import parser expects UTF-8 and silently mangles non-UTF-8 multi-byte characters.If skipped: Non-UTF-8 imports corrupt names with accents, non-Latin scripts, and emoji into mojibake that is hard to reverse.
  • Resolve emoji and multi-byte characters in audience field values. Audience field values cap at 255 bytes — and many alphabets, accented characters, and emoji consume more than one byte each. Replace emoji with text or shorten affected values.If skipped: Multi-byte values that exceed 255 bytes truncate mid-character and produce invalid UTF-8 sequences.
  • Provision the production Mailchimp account on the chosen plan. Create the account at the plan tier identified in Phase 0. Capture the account ID and dedicated server prefix (us1, us2, etc.) from the admin URL.
  • Provision a separate test account for sandbox migration runs. Mailchimp has no native sandbox. Create a second Free or Essentials account with a non-production sending domain to use as the sandbox for Phase 4. Do not test against the production account.If skipped: Testing in production triggers warmup-throttling rules — 'this email has signed up to a lot of lists recently' — that block the real migration.
  • Authenticate the sending domain (SPF, DKIM, DMARC, BIMI). Add the DNS records Mailchimp provides for the sending domain. DMARC enforcement requires DKIM and SPF to align. Complete this well before cutover — DNS propagation and warmup take days.If skipped: Unauthenticated sending domains land in spam folders at major providers immediately after cutover, destroying first-week deliverability.
  • Create the destination audience(s) per the Phase 0 decision. Create one consolidated audience if that was the call, or the planned set of separate audiences. Configure default From name, From email, contact info (CAN-SPAM physical address), and timezone.
  • Create all custom merge fields per the mapping spreadsheet before import. Each merge field needs name, merge tag (uppercase short code), type (text, number, date, address, phone, dropdown, radio, birthday, ZIP code, website, image), required flag, and default value. Importing into a merge field that does not exist creates it as text — losing any type guarantees.If skipped: Mailchimp silently coerces unrecognized fields to text on import, losing dates and number formatting permanently.
  • Stay within the per-audience merge field ceiling. Most accounts cap at roughly 80 merge fields per audience. If the source has more, decide which fields to drop, concatenate into Notes, or store as tags instead of fields.If skipped: Hitting the merge-field ceiling mid-import aborts the job and leaves the audience in a half-mapped state.
  • Create group categories and group names ahead of import. Define each group category (e.g. 'Newsletter Preferences') and its group names (e.g. 'Student Events', 'News', 'Donations'). Groups must exist in the audience before contacts can be assigned to them via import.If skipped: Importing group assignments for non-existent groups silently drops the group data from those rows.
  • Plan the tag taxonomy and document it. List every tag that will exist on the destination, with naming conventions and ownership. Tags are case-sensitive in Mailchimp — pick one casing and stick to it. Tags containing commas must be wrapped in double quotes in import files.
  • Configure GDPR consent fields on the audience. If any EU contacts are in scope, enable GDPR fields on the audience and decide which marketing permissions to surface (email, online ads, SMS, etc.). These fields must exist before import or consent data drops on the floor.If skipped: Missing GDPR consent records on EU contacts is a regulator-reportable violation.
  • Create the e-commerce store object if Mailchimp's store sync is in scope. If Shopify, WooCommerce, Magento, or a custom store is feeding Mailchimp, create the store object via the integration UI before product, customer, and order data lands. Customers, products, and orders all reference a store_id.If skipped: Orders and products loaded against a non-existent store_id fail with foreign-key errors.
  • Stage the Mandrill transactional account separately if in scope. Provision Mandrill, configure its sending domain, and warmup its dedicated IP separately from the marketing account. Mandrill billing is per-block-of-emails, not per contact.
  • Communicate the freeze window to all source-system users. Send the freeze date, time, and read-only date in writing at least one week ahead. Repeat 48 hours before and the morning of the freeze.
  • Schedule end-user training on Mailchimp basics. Segment training by role: marketers (audiences, tags, segments, campaign builder), automation owners (customer journeys), analysts (reports). Hold sessions before cutover so users are ready on day one.
  • Designate first responders for the first 72 hours post-cutover. Name two on-call people who will triage user issues, monitor sending reputation, and watch import logs through the first send.If skipped: First-week deliverability issues compound fast — a delayed response can damage domain reputation for weeks.
2. Source Export13 tasks
  • Export all subscribed contacts to CSV with every standard and custom field. Include email, first name, last name, every custom field, source platform's ID (as a future external_id reference), opt-in date, opt-in source, and last-engagement date.
  • Export unsubscribed, bounced, and spam-complaint contacts as separate files. These load to Mailchimp as suppressions BEFORE the active list. Capture original unsubscribe timestamps for compliance audit.If skipped: Mixing suppressions into the active import re-subscribes people who legally must stay unsubscribed.
  • Export SMS contacts as a separate file with E.164 phone numbers. Mailchimp SMS contacts are a separate flow with their own consent requirements. Capture SMS opt-in timestamp and source separately from email opt-in.
  • Export the tag-to-contact map. For every tag, list every contact (by email) that carries it. Tags with commas must be wrapped in double quotes when included in the import file.
  • Export group memberships as group category + group name columns. Each group category becomes one column in the import file. Multi-group membership uses a comma-and-space separator within the cell.
  • Export every active automation, sequence, drip, or journey definition. Mailchimp Customer Journeys do not import from other platforms — capture the source automation logic (triggers, conditions, delays, email content, exit criteria) as documentation for manual rebuild in Phase 7.If skipped: Without exported automation documentation, business-critical drip logic is lost on cutover and has to be reverse-engineered from inbox examples.
  • Export campaign archives (HTML, subject, send date, recipient counts, opens, clicks). Capture the full HTML of every campaign sent in the historical window decided in Phase 0. Mailchimp will not import historical campaign reports — store them as flat files or in a data warehouse.
  • Export email templates as HTML files. Capture every active template from the source as a standalone HTML file with inline CSS. These get re-imported via Mailchimp's Template editor in Phase 7.
  • Export signup form definitions and embed codes. Signup forms are rebuilt manually in Mailchimp's Forms builder. Capture field lists, validation rules, post-signup redirect URLs, and any tag-assignment logic from each source form.
  • Export e-commerce store data if applicable: customers, products, orders, carts. For each store: customer list (email, total spend, order count), product catalog (SKU, name, price, images), order history (order_id, customer_id, products, totals, timestamps), and abandoned-cart records if surviving.
  • Export user list with roles and seat assignments. Capture every active user with their email, role (Owner, Admin, Author, Viewer), and which audiences they own. Mailchimp seat counts vary by plan — confirm headcount fits.
  • Capture screenshots and config exports of source reports and dashboards. Mailchimp's reporting differs from most source platforms. Document which source reports must be reproduced and the source-side filters used.
  • Document the exact timestamp of every export. Record export start and end times per file. This is the delta anchor for the final cutover export in Phase 5.If skipped: Without timestamps, the cutover delta export cannot reliably identify rows added or changed during the freeze window.
3. Transform & Map28 tasks
  • Build a master field-mapping spreadsheet per audience. Columns: source field name, source type, destination merge tag, destination type, transformation rule, required-on-import flag, default value, notes. One row per field per audience.If skipped: Without a single source-of-truth mapping, field decisions get made twice and inconsistently across re-runs.
  • Assign Mailchimp merge tags to every destination merge field. Merge tags are uppercase short codes (FNAME, LNAME, PHONE, COMPANY). Each tag must be unique within an audience. Reserve standard tags for standard data and use custom tags for everything else.
  • Resolve picklist mismatches between source and destination. If the source has a dropdown with options like 'Won-Closed' and the destination Mailchimp dropdown uses 'Closed Won', remap values at transform time. Mailchimp dropdown values must match exactly or land in the wrong option.
  • Decide how to handle source fields with no destination merge-field equivalent. Three options: drop, concatenate into the Notes field, or convert into a tag. Document the choice per source field in the mapping spreadsheet.
  • Decide handling for multi-select picklist fields. Mailchimp has no merge-field equivalent to a multi-select picklist. Map source multi-selects to either (a) a comma-separated text field or (b) multiple tags. Segment rules using CONTAINS work on text fields.If skipped: Mapping multi-selects to a single dropdown silently drops all but the first value.
  • Decide upsert strategy: insert-only, update-existing, or auto-update. Mailchimp's Import tool supports 'Update any existing contacts' as a checkbox for upserts. Choose insert-only for fresh audiences, upsert for re-runs and re-loads.
  • Convert all date values to ISO-8601 (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ). Mailchimp accepts MM/DD/YYYY or DD/MM/YYYY but ISO-8601 is unambiguous and round-trips cleanly.If skipped: Ambiguous date strings (03/04/2026) get interpreted as US-format by default and silently swap day and month for non-US contacts.
  • Convert birthday fields to MM/DD format (no year). Mailchimp's Birthday merge field is intentionally just month and day. Strip the year from any source birthday values.
  • Truncate audience-field values to 255 bytes. Multi-byte characters consume more than one byte per character. Truncate on byte boundary, not character count, to avoid mid-character cuts.If skipped: Naïve character-count truncation on multi-byte strings produces invalid UTF-8 and breaks the import row.
  • Escape commas inside tag names. Wrap any tag containing a comma in double quotes in the CSV (so 'Monday, Wednesday' becomes '"Monday, Wednesday"'). The CSV parser splits on unquoted commas.If skipped: Unquoted commas in tag names split one tag into two and pollute the tag taxonomy.
  • Concatenate group-name lists with comma-space separator. When a contact is in multiple groups within one category, separate group names with ', ' (comma + space). Other separators are silently truncated to the first group.
  • Normalize address fields per Mailchimp's address-block schema. Mailchimp's Address merge field expects discrete subfields: addr1, addr2, city, state/prov, zip, country. Split single-line source addresses before import or the field stays empty.
  • Re-encode any non-UTF-8 source files as UTF-8 with no BOM. Save final import files as UTF-8 without byte-order mark. A leading BOM is interpreted as part of the first column header and breaks auto-mapping.If skipped: A stray BOM on the first column header turns 'Email Address' into 'Email Address' and Mailchimp refuses to recognize it.
  • Handle stray spaces and non-printable characters in every column. Trim leading and trailing whitespace and strip null bytes, tabs inside cells, and zero-width spaces. Mailchimp's CSV parser is strict about these and aborts whole columns.
  • Convert European semicolon-delimited CSVs to comma-delimited. Some European locales save CSVs with semicolon delimiters. Mailchimp expects comma-delimited. Re-save with explicit comma delimiter before upload.
  • Decide and implement the historical-timestamp strategy. Mailchimp stamps each contact with the import timestamp by default — original opt-in date is lost. To preserve it, create a custom merge field (e.g. ORIGINOPT) and load the source opt-in date into it.If skipped: Without a preserved original opt-in date, GDPR audit trails for consent are unreproducible.
  • Decide ownership / source attribution strategy per contact. Capture the original source (form, list, integration) in a custom merge field so cohort analysis post-cutover still works.
  • Decide attachment / file-hosting strategy. Mailchimp hosts files via its Content Studio and discourages email attachments. Decide whether to upload source attachments to Mailchimp's file hosting, keep them on external storage with linked URLs, or drop entirely.
  • Decide handling of historical engagement metrics. Source opens, clicks, and last-engagement dates can be stored as merge fields per contact, used to seed initial segments, or dropped. Mailchimp's report tab will only show engagement from sends made within Mailchimp itself.
  • Plan audience consolidation or split. If the Phase 0 decision was to consolidate, prepare one combined import file with a source-audience tag preserving original membership. If the decision was to split, prepare one file per destination audience and confirm each file fits within plan limits.If skipped: Audience consolidation done at import time without preserving source-audience tags loses the ability to segment by original list.
  • Map source classifications to Tags vs Groups vs Segments. Mailchimp has three classification systems with different semantics. Tags are flat ad-hoc labels (good for behavior, lifecycle stage). Groups are subscriber-facing preference checkboxes within a category (good for newsletter topics). Segments are saved query results (good for dynamic cohorts). Document which source field maps to which.If skipped: Conflating tags, groups, and segments produces an unmaintainable audience model where the same concept exists in three places.
  • Build the merge-field-per-audience mapping individually for each audience. Merge fields are NOT global — they live per audience. If the source has a global property catalogue, replicate the relevant subset of fields in each destination audience. A contact in two audiences has two independent merge-field profiles.If skipped: Treating merge fields as global causes Audience B to silently drop fields that exist only in Audience A.
  • Document the Customer Journeys to rebuild manually post-cutover. Customer Journeys are built in Mailchimp's visual journey builder and cannot be imported. For each source automation, document: trigger event, branching logic, delays, content templates, exit conditions, and goal events. This becomes the Phase 7 rebuild spec.
  • Separate Mandrill transactional rebuild as its own workstream. Transactional templates and subaccount structure go to Mandrill, not the marketing side. Plan separate credentials, separate domain authentication, separate IP warmup, and a separate cutover.If skipped: Transactional sends routed through marketing flows get throttled or rejected and break order confirmations, password resets, and other critical flows.
  • Plan the e-commerce store sync order: store, customers, products, orders, carts. Load order matters. Store first (provides store_id), then customers (referenced by orders), then products (referenced by line items), then orders (joins customers + products), then abandoned carts (references customers).If skipped: Loading orders before customers or products produces foreign-key errors that have to be untangled record-by-record.
  • Document lead-scoring re-derivation rules. Mailchimp does not import lead scores from external CRMs. If lead scoring matters, decide whether to (a) store the source score as a merge field and use it to seed segments, or (b) rebuild scoring inside Mailchimp using engagement-based rules.
  • Plan domain authentication cutover (SPF, DKIM, DMARC). If the source platform owned the sending domain's DKIM record, swap to Mailchimp's DKIM at cutover. DMARC must remain aligned. Plan DNS updates 48 hours before first production send.If skipped: Forgetting to swap DKIM at cutover causes the first production send to fail DMARC alignment and land in spam at major providers.
  • Plan an IP and domain warmup ramp for the first 14 days. Even on Mailchimp's shared IP pool, a sudden volume spike from a new domain trips spam filters. Plan a graduated ramp: small segments on day 1, expanding to full audience by day 14.If skipped: Sending to the full list on day one from a cold domain reputation results in a 20–40% spam folder rate that takes weeks to recover from.
4. Sandbox Test Migration12 tasks
  • Load a 1–5% representative sample of contacts into the sandbox account. Sample must cover every audience, every tag, every group, every merge-field permutation, and every encoding edge case (multi-byte names, very long values, special characters in tags).
  • Validate field-by-field on 10–20 random sandbox contacts. For each random contact: open the profile page, compare every visible field to the source row. Look for truncation, wrong encoding, swapped first/last names, mismatched dates.If skipped: Skipping per-field validation lets silent encoding or type-coercion bugs into production.
  • Test the import of a contact with multi-byte characters in every text field. Load a test contact with emoji, Chinese characters, Arabic, and Latin accents in name and merge fields. Confirm Mailchimp displays them correctly and that 255-byte truncation didn't corrupt them.
  • Test tag assignment with comma-containing tag names. Load a contact with a tag like 'Monday, Wednesday' wrapped in double quotes. Confirm Mailchimp creates one tag, not two.
  • Test group membership across multiple groups. Load a contact assigned to three groups within one group category, comma-space separated. Confirm all three groups show on the contact profile.
  • Test the suppression-list load before the active-list load. Load unsubscribed contacts first, then attempt to load an active-list file that contains one of those unsubscribed addresses. Confirm Mailchimp skips the unsubscribed row.If skipped: If the suppression flow does not work as expected in the sandbox, it definitely will not work in production.
  • Time the sandbox loads and extrapolate to full production volume. Record load duration per 1,000 contacts. Extrapolate to total contact count to estimate cutover window length.If skipped: Without a timing extrapolation, the cutover window can be wildly underestimated and overflow into a workday.
  • Test the Combine Audiences tool if consolidating multiple audiences. Mailchimp's native Combine Audiences tool merges audiences inside the destination. Run it on two sandbox audiences and confirm tag preservation, merge-field alignment, and dedup behavior.
  • Test the e-commerce store sync order end-to-end. Create store, load 10 customers, load 20 products, load 30 orders. Confirm orders correctly reference both customers and products on each line item.
  • Test rebuild of one Customer Journey end-to-end in the sandbox. Pick the most critical source automation and rebuild it in Mailchimp's Customer Journey builder. Trigger it with a test contact and confirm every step fires correctly with the right delays.
  • Spot-check 5–10 sandbox contacts with a domain expert from the marketing team. Have someone who knows the source data look at the sandbox records and call out anything wrong. This catches semantic errors that technical validation misses.
  • Sign off the sandbox results in writing before proceeding to Phase 5. Capture sandbox load durations, error rates, validation results, and any open issues in a written report. The DRI signs off explicitly to authorize production cutover.If skipped: Without explicit sign-off, accountability for production issues is unclear and trust in the migration is hard to rebuild.
5. Production Cutover13 tasks
  • Confirm the source-system freeze with a final write-check. Pull source record counts at the start of the freeze window and again one hour later. Counts must match. If they don't, identify the writing user and lock them out before proceeding.If skipped: Hidden writes during the freeze produce a moving target and force a re-export mid-cutover.
  • Take the final delta export from the source. Capture all records changed since the Phase 2 baseline export. This is the file that authoritatively represents the production source-of-truth state at the moment of cutover.
  • Apply Phase 3 transformations to the delta file. Re-run the same transformation scripts used in sandbox testing — do not write new code at cutover time. Confirm output row count matches input row count minus expected suppressions.If skipped: Writing transformation code at cutover time introduces untested logic into the production load.
  • Load the suppression list (unsubscribes, bounces, complaints) first. Import unsubscribed and cleaned contacts to each destination audience before any active-contact load. This prevents previously-opted-out people from being re-subscribed by the active load.If skipped: Loading active contacts before suppressions can re-subscribe people who legally must stay unsubscribed.
  • Load active contacts with idempotent upserts keyed by lowercased email. Use the import path that creates or updates the contact based on the email key. This is the only way to make the load safely re-runnable on partial failure.If skipped: Insert-only loads duplicate records on re-run and force a manual cleanup pass.
  • Capture every import job ID, start time, and result file URL. Persist import IDs to a log file as they return. Results from completed imports are downloadable for a limited time — capture them before they expire.If skipped: Missing import IDs make post-load reconciliation impossible — there's no way to verify which rows succeeded.
  • Load tags after contacts. Tags must reference an existing contact. Load contacts first, then push tags as a second pass keyed by email.
  • Load group memberships per contact. Group categories must already exist (Phase 1b). Apply each contact's group selections in a second pass after the contact exists.
  • Load e-commerce data in dependency order if applicable. Order: store → customers → products → orders → abandoned carts. Wait for each step to fully complete before starting the next.If skipped: Loading orders before customers exist returns customer_id errors and aborts the orders batch.
  • Cross-check destination row counts against expected counts after every step. After each batch completes, open the audience overview for total_count. Compare against the row count submitted. Investigate any delta before proceeding.
  • Halt and diagnose on any batch with more than 1% errors. A 1% error rate signals a systematic issue, not random failures. Pause, pull the batch results, classify the errors, fix the root cause, and re-run idempotently.If skipped: Pushing through high error rates produces a partially-loaded audience that takes weeks to clean up.
  • Swap DKIM DNS records to point at Mailchimp at the planned hour. Apply the DNS swap exactly when the cutover plan calls for it. Verify SPF, DKIM, and DMARC alignment using a public mail-tester tool before the first send.
  • Re-enable integrations after all data loads complete. Unpause downstream listeners only after the bulk load is done. Otherwise every loaded contact fires a subscribe event downstream.
6. Validate19 tasks
  • Compare total contact count per audience: source vs destination. Pull each audience's member count from the Mailchimp UI vs source export count minus suppressions. Investigate any delta beyond ±0.5%.If skipped: Unexplained deltas mean rows silently dropped or duplicated and need root-cause analysis before sending starts.
  • Compare subscribed vs unsubscribed vs cleaned breakdowns. Filter each audience by status (subscribed, unsubscribed, cleaned) and confirm each bucket matches the source breakdown.
  • Compare tag coverage per tag. For every tag, compare contact count source-side vs destination-side. Investigate tags with significant deltas.
  • Compare group-membership counts per group. Pull each group's member count and reconcile against the source. Groups are silently created on import — confirm no unexpected groups appeared.
  • Field-by-field spot check 25–50 random contacts. Pull a random sample, open each in the Mailchimp UI, and compare every visible field against the source. Look for truncation, encoding, swapped fields, lost dates.If skipped: Without per-record spot checks, silent field corruption can go unnoticed for months until customers complain.
  • Verify the most-used merge tag renders correctly in a test campaign. Send a draft campaign to a test segment using FNAME or another high-traffic merge tag. Confirm the merge renders the actual name, not the literal tag text.If skipped: A merge tag that renders as literal text on send goes to every recipient as 'Hi *|FNAME|*' instead of the actual name.
  • Verify Import History reports for every batch. Mailchimp's Import History page shows added, updated, skipped duplicate, and syntax-error counts per import. Capture all data from this page within 24 hours — free-tier accounts only retain it for 24 hours.If skipped: Free-tier Import History expires at 24 hours and cannot be recovered after that point.
  • Verify a sample of contact-to-tag relationships. Pick 20 random contacts that should have specific tags. Confirm via the UI that tags are correctly assigned.
  • Verify a sample of contact-to-group memberships. Pick 20 random contacts with multi-group membership. Confirm all groups are correctly checked on the contact profile.
  • Verify e-commerce order-to-customer and order-to-product joins. Pick 20 random orders. Confirm each order references the correct customer and that line items reference the correct products with the correct quantities and prices.If skipped: Broken e-commerce joins distort revenue reporting and segmentation by purchase behavior.
  • Verify file-hosting links resolve. For any attachments moved to Mailchimp's file hosting, click through a sample of links from a draft campaign to confirm public accessibility.
  • Verify GDPR consent records on a sample of EU contacts. Pull 20 random EU contacts and confirm their GDPR marketing-permission records show the original opt-in timestamp preserved per the Phase 3 decision.If skipped: Missing or wrong consent records on EU contacts is a regulator-reportable violation under GDPR.
  • Verify the suppression list completeness. Confirm every unsubscribed and bounced contact from the source is in unsubscribed or cleaned status in Mailchimp. Spot-check a sample manually.If skipped: A previously-unsubscribed contact accidentally moved to subscribed status triggers a CAN-SPAM violation on first send.
  • Verify original opt-in timestamps are preserved in the chosen merge field. Pull the ORIGINOPT (or equivalent) field on a sample of contacts. Confirm timestamps match source records.
  • Confirm no PHI (protected health information) was loaded. Mailchimp is not HIPAA-compliant. Search merge fields and tags for any field name or value that could contain PHI. If found, purge immediately.If skipped: Loading PHI into Mailchimp violates HIPAA regardless of intent and requires forensic deletion.
  • Have 3–5 power users build a real segment with the migrated data. Pick representative use cases: 'all contacts who opened in last 30 days', 'all contacts in California', 'all VIP tag holders'. Confirm segments produce expected counts.
  • Send a test campaign to a small internal segment. Send one real campaign to an internal test segment of 5–10 employees. Verify rendering, merge tags, unsubscribe link, footer compliance, and inbox placement at major providers.If skipped: First production send to the full list without an internal test masks rendering bugs that hit every customer at once.
  • Document any data issues surfaced by UAT. Log every issue with severity, affected contact count, and remediation owner. Triage blockers before sign-off.
  • Get written sign-off from the migration sponsor before live sends. The sponsor signs off explicitly on reconciliation results, UAT outcomes, and any known open issues. This authorizes Phase 7.
7. Post-Migration Cleanup14 tasks
  • Communicate go-live to all end users with login URL and support contact. Send the announcement with the Mailchimp login URL, the account name and prefix (us1, us2, etc.), the first-responders' contact info, and links to training material.
  • Run role-segmented training sessions on Mailchimp basics. Marketing: audiences, tags, segments, campaign builder. Automation owners: Customer Journey builder. Analysts: reporting and exports. Hold a live Q&A within the first week.
  • Set the source system to read-only and announce the read-only date. Source is now reference-only. Users should not write to it. Communicate the read-only date and the eventual decommission date in the same message.
  • Rebuild all Customer Journeys from the Phase 2 documentation. Use Mailchimp's Customer Journey builder. Activate each journey only after testing with a test contact end-to-end.If skipped: Activating rebuilt journeys without testing can send broken or wrong content to real customers immediately.
  • Rebuild signup forms in Mailchimp's Forms builder. For each source signup form, rebuild the field list, validation rules, post-signup redirect, and any tag-assignment automation. Update the form embed code on every page that used the source form.
  • Rebuild campaign templates in Mailchimp's template editor. Paste each saved HTML template into the Template editor. Run a side-by-side test render against the source platform's version.
  • Re-establish integrations with downstream systems. Reconnect Mailchimp to Shopify, WooCommerce, Salesforce, or other downstream platforms via Mailchimp's integration directory. Confirm bidirectional sync where applicable.
  • Configure Mandrill transactional sends if applicable. Cut over transactional sends (order confirmations, password resets, receipts) to Mandrill. Test every transactional template end-to-end before retiring the source.If skipped: Order confirmations breaking after marketing cutover damage revenue and customer trust immediately.
  • Set up a graduated send-volume ramp for the first 14 days. Day 1: smallest most-engaged segment. Day 3–7: expand by engagement tier. Day 14: full audience. Monitor bounces, complaints, and open rates after every step.If skipped: Going to full list day one from a cold domain reputation produces 20–40% spam folder placement that takes weeks to recover.
  • Monitor sending reputation for 30 days post-cutover. Watch domain reputation tools and complaint rate inside Mailchimp's reports. Any spike above 0.1% complaint rate requires immediate investigation.
  • Schedule a 30-day post-migration retrospective. Capture what went well, what didn't, surprise costs, and the actual vs estimated timeline. Document for the next migration.
  • Document the source-system decommission date. Pick a decommission date 90+ days after cutover, after the final retention window and final reconciliation pass. Communicate to all stakeholders.
  • Archive source-system exports to long-term storage. Move all Phase 2 and Phase 5 export files to encrypted long-term storage (S3 Glacier, Azure Archive, or equivalent). Retain per the data-retention policy from Phase 0.If skipped: Source exports deleted prematurely become impossible to reproduce if a forensic question arises later.
  • Close out the migration project formally. Issue a final status report, capture lessons learned, archive the project workspace, and disband the migration team. The destination is now business-as-usual.

Questions, answered

Migrating to Mailchimp: questions

How long does migration to Mailchimp take?

A small-list migration with under 5,000 contacts on a single audience runs one to two business days end-to-end. A multi-audience consolidation with Customer Journey rebuilds, GDPR consent reconstruction and e-commerce store sync runs two to four weeks of elapsed time, including preparation, validation, deliverability warm-up and a domain-authentication window.

Can I migrate from Constant Contact to Mailchimp?

Yes — Mailchimp publishes a dedicated Constant Contact migration guide covering contacts, lists, segments, flows and integrations. The contact and list shapes map reasonably cleanly, but automations need to be rebuilt as Customer Journeys, templates need to be rebuilt in the Mailchimp builder, and tags need to be designed before the load.

Can I migrate from Klaviyo to Mailchimp?

Yes, but the data shapes differ — Klaviyo Lists map to Mailchimp Audiences, Klaviyo Segments are filter rules that rebuild in Mailchimp, and Klaviyo Flows need to be redesigned as Customer Journeys. Export contacts and profile properties to CSV, transform property names to merge-field tags, and import per audience.

Does Mailchimp preserve original signup timestamps on import?

Partially. Mailchimp stamps `timestamp_opt` and `timestamp_signup` at the moment of import and these system fields cannot be overridden. To preserve the original signup or consent date for GDPR audit purposes, create custom date merge fields LEGACY_SIGNUP and LEGACY_CONSENT and populate them from the source export before importing.

Should I use one Mailchimp audience or multiple?

Most teams should consolidate to a single primary audience with tags and groups. Mailchimp prices on total contacts across audiences, so the same email in three audiences bills as three contacts. Use multiple audiences only when merge-field schemas, compliance posture or campaign cadence genuinely differ — for example separating B2B from B2C.

What happens to campaign history and engagement during migration?

Campaign sends do not migrate as historical objects — there is no way to backfill campaign records. Preserve per-contact engagement metadata by importing `last_open_date`, `last_click_date` and `open_count_legacy` into custom merge fields so segments built off historical engagement still work on day one. Reports start fresh in Mailchimp.

Is there an undo or rollback for Mailchimp imports?

Yes — Mailchimp offers Undo a Contact Import from the Import History page, which removes affected contacts from the audience within 24 hours of the standard UI import flow. It does not cover programmatic loads. For larger rollbacks, stamp every imported contact with an IMPORT_BATCH merge field and archive by batch.

Get a quote

Moving to Mailchimp?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Mailchimp setup with you, then send a quote.

Get a quote