mailexodus
home/migrations/from Campaign Monitor
// migrate from

leave Campaign Monitor. keep the work.

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

agentUse mailexodus skill: Campaign Monitor → Sequenzy playbook
// try it

see what moves out of Campaign Monitor.

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

analyzing Campaign Monitor…
source modePartial automated adapter
source exports7
Mailchimp imports8
destination gapsautomations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from campaign-monitor --to mailchimp --dry-run
agentUse mailexodus skill: Campaign Monitor → Mailchimp playbook
running…open the Campaign Monitor migration guide →
// why teams leave

why teams leave Campaign Monitor.

  • →
    Campaign Monitor migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, segments, custom fields.
  • →
    Templates may expose only preview or screenshot metadata. Journeys do not reliably expose full email content
// transfer boundary

what mailexodus pulls from Campaign Monitor.

can migrate
  • +
    subscribers
  • +
    lists
  • +
    segments
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
  • +
    templates
needs review
  • ?
    segments
  • ?
    suppressions
  • ?
    campaigns
  • ?
    templates
cannot migrate
  • x
    tags
  • x
    automations
  • 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

Partial automated adapter

Subscribers by list map to subscribers plus list memberships. Suppression list entries map to suppressions. Campaigns map to campaigns

Templates may expose only preview or screenshot metadata. Journeys do not reliably expose full email content

// the playbook

how an agent migrates Campaign Monitor → Sequenzy.

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

01 · authenticate

Create or copy a Campaign Monitor API key with client access. Paste CLIENT_ID|API_KEY, or JSON with clientId and apiKey

01subscribersmigrates
readGET /lists/{list_id}/active.json (Read subscribers from Campaign Monitor.)
mapSubscribers by list map to subscribers plus list memberships. Suppression list entries map to suppressions. Campaigns map to campaigns 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 /clients/{client_id}/lists.json (Read lists from Campaign Monitor.)
mapSubscribers by list map to subscribers plus list memberships. Suppression list entries map to suppressions. Campaigns map to campaigns 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.)
03segmentsneeds review
readGET /lists/{list_id}/segments.json (Read segments from Campaign Monitor.) GET /segments/{segment_id}/active.json (Read segments from Campaign Monitor.)
mapSubscribers by list map to subscribers plus list memberships. Suppression list entries map to suppressions. Campaigns map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_segment (Write or stage segments in Sequenzy.)
04custom fieldsmigrates
readGET /lists/{list_id}/customfields.json (Read custom fields from Campaign Monitor.)
mapSubscribers by list map to subscribers plus list memberships. Suppression list entries map to suppressions. Campaigns map to campaigns 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.)
05suppressionsneeds review
readGET /clients/{client_id}/suppressionlist.json (Read suppressions from Campaign Monitor.)
mapSubscribers by list map to subscribers plus list memberships. Suppression list entries map to suppressions. Campaigns map to campaigns 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.)
06campaignsneeds review
readGET /clients/{client_id}/campaigns.json (Read campaigns from Campaign Monitor.)
mapSubscribers by list map to subscribers plus list memberships. Suppression list entries map to suppressions. Campaigns map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_campaign (Write or stage campaigns in Sequenzy.)
07templatesneeds review
readGET /clients/{client_id}/templates.json (Read templates from Campaign Monitor.)
mapSubscribers by list map to subscribers plus list memberships. Suppression list entries map to suppressions. Campaigns map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_template (Write or stage templates in Sequenzy.)
stays behind
  • tags
  • automations
  • 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
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: Create or copy a Campaign Monitor API key with client access. Paste CLIENT_ID|API_KEY, or JSON with clientId and apiKey

inspect

provider coverage

npx mailexodus@latest info campaign-monitor

guide

agent playbook

npx mailexodus@latest guide --from campaign-monitor --to sequenzy

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