mailexodus
home/migrations/from Mailchimp
// migrate from

leave Mailchimp. keep the work.

mailexodus reads Mailchimp over its API and normalizes subscribers, lists, tags, segments into one portable schema — so you move with a report, not a 40-item checklist.

agentUse mailexodus skill: Mailchimp → Sequenzy playbook
// try it

see what moves out of Mailchimp.

A live route check, computed from Mailchimp's real API surface. Pick any destination to compare import support — nothing is written.

analyzing Mailchimp…
source modeAutomated adapter
source exports9
Klaviyo imports8
destination gapstags
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from mailchimp --to klaviyo --dry-run
agentUse mailexodus skill: Mailchimp → Klaviyo playbook
running…open the Mailchimp migration guide →
// why teams leave

why teams leave Mailchimp.

  • →
    Mailchimp migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, tags, segments.
  • →
    Journey reconstruction can require manual review
// transfer boundary

what mailexodus pulls from Mailchimp.

can migrate
  • +
    subscribers
  • +
    lists
  • +
    tags
  • +
    segments
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
  • +
    templates
  • +
    automations
needs review
  • ?
    Journey reconstruction can require manual review
cannot migrate
  • x
    sender reputation and domain warmup
  • x
    historical analytics, revenue attribution, and aggregate reporting
  • x
    contacts already mid-flight inside active automations
  • x
    A/B test results and provider-specific experiment history
  • x
    provider-native design blocks, product widgets, coupons, and private assets that are not exposed by API
source adapter

Automated adapter

Audience members map to subscribers and list memberships. Merge fields map to custom attributes. Tags, segments, campaigns, templates, and journey emails map directly where possible

Journey reconstruction can require manual review

// the playbook

how an agent migrates Mailchimp → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Mailchimp, map it to the portable schema, write it to the destination. mailexodus never writes; your agent does, with this report in hand.

01 · authenticate

In Mailchimp, open Profile, Extras, API keys, then create or copy an API key with access to audiences, campaigns, templates, and automations

01subscribersmigrates
readGET /lists/{list_id}/members (Read subscribers from Mailchimp.)
mapAudience members map to subscribers and list memberships. Merge fields map to custom attributes. Tags, segments, campaigns, templates, and journey emails map directly where possible mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST add_subscriber (Write or stage subscribers in Sequenzy.) PATCH update_subscriber (Write or stage subscribers in Sequenzy.)
02listsmigrates
readGET /lists (Read lists from Mailchimp.)
mapAudience members map to subscribers and list memberships. Merge fields map to custom attributes. Tags, segments, campaigns, templates, and journey emails map directly where possible mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_list (Write or stage lists in Sequenzy.) POST add_subscribers_to_list (Write or stage lists in Sequenzy.)
03tagsmigrates
readGET /lists/{list_id}/tag-search (Read tags from Mailchimp.) GET /lists/{list_id}/members/{subscriber_hash}/tags (Read tags from Mailchimp.)
mapAudience members map to subscribers and list memberships. Merge fields map to custom attributes. Tags, segments, campaigns, templates, and journey emails map directly where possible mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_tag (Write or stage tags in Sequenzy.)
04segmentsmigrates
readGET /lists/{list_id}/segments (Read segments from Mailchimp.) GET /lists/{list_id}/segments/{segment_id}/members (Read segments from Mailchimp.)
mapAudience members map to subscribers and list memberships. Merge fields map to custom attributes. Tags, segments, campaigns, templates, and journey emails map directly where possible mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_segment (Write or stage segments in Sequenzy.)
05custom fieldsmigrates
readGET /lists/{list_id}/merge-fields (Read custom fields from Mailchimp.)
mapAudience members map to subscribers and list memberships. Merge fields map to custom attributes. Tags, segments, campaigns, templates, and journey emails map directly where possible mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePATCH update_subscriber.customAttributes (Write or stage custom fields in Sequenzy.)
06suppressionsmigrates
readGET /lists/{list_id}/members?status=unsubscribed (Read suppressions from Mailchimp.) GET /lists/{list_id}/members?status=cleaned (Read suppressions from Mailchimp.)
mapAudience members map to subscribers and list memberships. Merge fields map to custom attributes. Tags, segments, campaigns, templates, and journey emails map directly where possible mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePATCH update_subscriber.status (Write or stage suppressions in Sequenzy.)
07campaignsmigrates
readGET /campaigns (Read campaigns from Mailchimp.) GET /campaigns/{campaign_id}/content (Read campaigns from Mailchimp.)
mapAudience members map to subscribers and list memberships. Merge fields map to custom attributes. Tags, segments, campaigns, templates, and journey emails map directly where possible mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_campaign (Write or stage campaigns in Sequenzy.)
08templatesmigrates
readGET /templates (Read templates from Mailchimp.) GET /templates/{template_id}/default-content (Read templates from Mailchimp.)
mapAudience members map to subscribers and list memberships. Merge fields map to custom attributes. Tags, segments, campaigns, templates, and journey emails map directly where possible mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_template (Write or stage templates in Sequenzy.)
09automationsmigrates
readGET /automations (Read automations from Mailchimp.) GET /customer-journeys/journeys (Read automations from Mailchimp.)
mapAudience members map to subscribers and list memberships. Merge fields map to custom attributes. Tags, segments, campaigns, templates, and journey emails map directly where possible mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_sequence (Write or stage automations in Sequenzy.) POST insert_sequence_step (Write or stage automations in Sequenzy.)
stays behind
  • sender reputation and domain warmup
  • historical analytics, revenue attribution, and aggregate reporting
  • contacts already mid-flight inside active automations
  • A/B test results and provider-specific experiment history
  • provider-native design blocks, product widgets, coupons, and private assets that are not exposed by API
guardrails
  • Sender reputation is earned at the destination — set up SPF/DKIM/DMARC and a warmup ramp; it does not transfer.
  • Keep the source platform active until authentication, warmup, and in-flight automations have finished.
  • Honor suppressions before the first send.
  • After writing, verify counts per object type against the source before switching live sends.
// run it

guide your agent, or follow it yourself.

Pull the full playbook from the skill prompt, CLI, or MCP server, then work the steps. Start by confirming credentials: In Mailchimp, open Profile, Extras, API keys, then create or copy an API key with access to audiences, campaigns, templates, and automations

inspect

provider coverage

npx mailexodus@latest info mailchimp

guide

agent playbook

npx mailexodus@latest guide --from mailchimp --to sequenzy

agentUse mailexodus skill: Mailchimp → Sequenzy playbook
compare Mailchimp alternatives →browse every migration page →