Skip to content
Docs

Guide

Move from Mailchimp to Emailit. Map audiences, groups, tags and merge fields, import subscribers without losing opt-outs, convert merge tags, and rebuild flows as automations.

Updated Oct 23, 2026

This guide moves your Mailchimp audiences, merge fields, tags, templates, campaigns and automation flows to Emailit. If you also send transactional email through Mailchimp Transactional (Mandrill), follow Migrate from Mandrill for that part. Read Migrate to Emailit first for the overall order.

Concepts

Mailchimp Emailit
Account Account and workspaces. Each workspace has its own domains, contacts, members and credits.
Audience Audience. A person on two Mailchimp audiences is two contacts; in Emailit they’re one contact on two audiences.
Contact Contact, with a subscriber entry for each audience it’s on
Audience fields and merge tags (FNAME, LNAME, custom fields) First name, last name and custom fields
Tags Tags
Groups Separate public audiences, which people choose between on the manage subscriptions page
Segments Pick and exclude audiences in each campaign. Segments are in alpha and open to the Emailit team only.
Contact statuses: subscribed, unsubscribed, non-subscribed, cleaned Subscribed audience members, and suppressions for opt-outs and bounces. See Move contacts.
Regular email campaigns Campaigns
A/B tests A/B testing with up to five versions
Marketing Automation Flows (formerly Customer Journeys) and classic automations Automations (beta)
Sign-up forms and pop-up forms Forms (early access), or an audience’s subscribe URL behind your own form
Double opt-in setting Double opt-in per audience
Email templates Templates with an alias and versions
Reports Campaign reports
Domain authentication Sending domains
Audience webhooks Webhooks with subscriber.* and contact.* events
Mailchimp Transactional (Mandrill) The Email API and SMTP relay

Mailchimp suggests one audience split with groups and tags. In Emailit, the number of audiences isn’t limited, so create one for each list people subscribe to, such as “Newsletter” and “Product updates”. Set their visibility to Public, and subscribers can choose between them on the manage subscriptions page, like they did with groups. Each plan limits how many subscribers one audience can hold; see Audiences.

Prepare your workspace

  1. Add and verify your sending domain. See Add a domain, and request production access. Mention that you’re moving from Mailchimp, how many subscribers you have and how you collected them.

  2. Create custom fields for the audience fields you use, in WorkspaceSettingsCustom fields. The import can only fill fields that already exist. Use the type that fits the data: Text for a company, Date for a signup date, Select for a plan.

  3. Create your audiences in Email MarketingAudiences, one for each Mailchimp audience or group. If you collect new sign-ups with double opt-in, turn it on in each audience’s Settings tab. See Double opt-in.

Move contacts

Mailchimp exports an audience as a ZIP file with one CSV file per contact status. Each file goes to a different place in Emailit:

Mailchimp file Where it goes
Subscribed Import into the matching audience.
Unsubscribed The suppression list, with the type unsubscribe. Campaigns skip these addresses, and transactional email still reaches them.
Cleaned (hard bounces) The suppression list, with the type recipient, which blocks all email to the address.
Non-subscribed Leave them out of audiences. They never opted in to your marketing email.

Pending contacts, who never confirmed double opt-in, and archived contacts aren’t in the export. Leave them out too.

An unsubscribe suppression stops every campaign in the workspace. If you move several audiences, don’t suppress people who unsubscribed from one audience but are still subscribed to another: importing them only into the audience they’re subscribed to is enough.

  1. Export the audience. In Mailchimp, go to Audience, choose the audience, select Export audience, then Export CSV. Mailchimp emails you when the file is ready. Download the ZIP and unpack it.

  2. Prepare the subscribed file. Keep Email Address, First Name, Last Name and the columns of the fields you created. You can delete Mailchimp’s own columns, such as MEMBER_RATING, OPTIN_TIME and LEID, or exclude them while mapping. Write dates as YYYY-MM-DD, and split the file into parts of up to 2,500 rows.

  3. Import it. Go to Email MarketingContacts and select Import. Map the email column, usually Email Address, to Email, the name columns to First name and Last name, and the other columns to your custom fields. Under Audiences, choose the audience. See Import and export contacts.

  4. Suppress opt-outs and bounces. Build one CSV from the unsubscribed and cleaned files with the columns email,type,reason:

    CSV
    email,type,reason
    left@example.com,unsubscribe,mailchimp unsubscribed
    gone@example.com,recipient,mailchimp cleaned

    In Email APISuppressions, select Import and upload it. Each file can have up to 10,000 rows and can be at most 8 MB. See Manage suppressions.

Imports don’t start automations and don’t send double opt-in or confirmation emails, so your existing subscribers aren’t welcomed a second time.

A few details:

  • Birthdays. Mailchimp birthday fields have no year (MM/DD), and Emailit date fields need a full date. Add a placeholder year, such as 2000-04-12. The Date anniversary automation trigger only uses the month and day.
  • Tags. The import wizard doesn’t read tags. Add them with the API after the import: Add tags takes the contact’s email address, so you can loop over the TAGS column of the export. It starts Tag added automations, so add tags before you start those automations.
  • Groups. The export has a column for each group category. Filter it by each group, and import each part into the audience you created for that group.
  • Large audiences. To import from code instead of files, call Add a subscriber for each person. It creates the contact and its audience membership in one call. Unlike the import, it starts Added to audience automations, so add everyone before you start those automations.

Move templates

In Mailchimp, custom-coded templates can be exported as HTML: open the template’s More options menu and choose Export as template. Drag-and-drop templates can’t be exported. For those, get the HTML of a campaign that uses the design with the Marketing API’s GET /3.0/campaigns/{campaign_id}/content, or rebuild the design in one of Emailit’s editors. Import each HTML file in Email MarketingTemplates with Import. If a template uses images hosted by Mailchimp, download them, point the src paths in the HTML at the files in an images/ folder, and import the HTML and the images as a ZIP package, so Emailit hosts them in your workspace. See Import and export templates.

Campaigns render with Temple, so replace Mailchimp merge tags:

Mailchimp Emailit
*|FNAME|*, *|LNAME|*, *|EMAIL|* {{first_name}}, {{last_name}}, {{email}}
*|COMPANY|* or another audience field {{cf.company}}, with the custom field’s key
A default value set in the audience field’s settings {{first_name|"there"}}
*|UNSUB|* {{unsubscribe_url}}
*|UPDATE_PROFILE|* {{manage_subscriptions_url}}
*|ARCHIVE|* {{webview_url}}
*|IF:FNAME|*…*|ELSE:|*…*|END:IF|* {{#if first_name}}…{{else}}…{{/if}}
*|IF:PLAN=pro|* Not supported. Store a Boolean field such as is_pro and use {{#if cf.is_pro}}.
*|INTERESTED:Category:Group|*…*|END:INTERESTED|* Not supported. Send a separate campaign to each audience.
*|LIST:COMPANY|*, *|LIST:ADDRESS|*, *|HTML:LIST_ADDRESS_HTML|* Write your company name and postal address into the footer, or keep them in global values such as {{global.address}}.
*|CURRENT_YEAR|*, *|DATE:Y|*, *|REWARDS|* and other system tags No equivalent. Remove them.

Anything else in double braces renders as empty, and Mailchimp tags left in *|…|* form are sent as plain text. Before you send, check each campaign with Preview as contact in the Preview and test step. See Merge tags.

Rebuild campaigns and flows

Create new campaigns in Email MarketingCampaigns from your imported templates with Choose from templates. Campaign reports and past sends don’t move, so export the Mailchimp reports you want to keep before you close the account. See Create a campaign.

Rebuild each Marketing Automation Flow (formerly Customer Journey) and classic automation as an automation in the Contact context. Starting points map to triggers like this:

Mailchimp starting point Emailit trigger
Contact signs up, or is added to an audience Added to audience
Tag is added or removed Tag added, Tag removed
Birthday or a date field Date anniversary, Date in contact field
Opens or clicks an email Email opened, Link clicked
Event sent with the API Custom event, on Business and Custom plans
Sign-up through a form Form submitted, for Emailit forms (early access)

Flow steps become Send email, Time delay, Wait until, Condition (If/Else), Add tags and the other automation steps. Start with a recipe if one is close to your flow. Start each automation before you move your sign-up forms, so new subscribers get their welcome emails from the first day.

Move sign-up forms

Replace Mailchimp’s embedded and pop-up forms with Emailit forms, which is in early access, or point your own form at the audience’s subscribe URL. Both respect the audience’s double opt-in setting.

Change DNS

Add your domain in Email APIDomains and publish the Emailit records. They use their own names (emailit._domainkey, emailit.<domain>, and optionally go and inbound), so they don’t conflict with Mailchimp’s DKIM CNAMEs, such as k2._domainkey. Keep your DMARC record. See DNS records.

After your last Mailchimp campaign, remove Mailchimp’s DKIM records. Mandrill uses its own records, mte1._domainkey and mte2._domainkey, so remove those only when you’ve moved your transactional email too.

Next steps

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.