mailexodus
home/migrations/to Campaign Monitor
// migrate to

move to Campaign Monitor without rebuilding by hand.

mailexodus normalizes your current platform into one portable schema, then checks what Campaign Monitor can actually import. You get a route report before your agent writes anything.

agentUse mailexodus skill: your source → Campaign Monitor playbook
// try it

bring your data into Campaign Monitor.

Pick the platform you're leaving and generate a route playbook. The report shows what maps cleanly into Campaign Monitor's model and what needs review — before you approve writes.

analyzing Klaviyo…
source modeAutomated adapter
source exports8
Campaign Monitor imports7
destination gapstags, automations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from klaviyo --to campaign-monitor --dry-run
agentUse mailexodus skill: Klaviyo → Campaign Monitor playbook
running…open the Klaviyo migration guide →
// fit

when Campaign Monitor is the right move.

Campaign Monitor is a strong fit for teams that want campaign monitor email teams moving subscribers, lists, segments, templates, and campaigns into a cleaner operating model. The migration risk is rarely the CSV — it is the automation graph: triggers, delays, branches, template references, and consent state. mailexodus puts a portable schema in the middle so those objects are inspected before they become Campaign Monitor objects.

// inbound

what Campaign Monitor receives.

can import
  • +
    subscribers
  • +
    lists
  • +
    segments
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
  • +
    templates
needs review
  • ?
    destination mappings still need final operator review
not exposed for import
  • x
    tags
  • x
    automations
destination 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 Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to Campaign Monitor.

  1. Authenticate your sending domain in Campaign Monitor (SPF, DKIM, DMARC) and plan a warmup window — sender reputation is earned here, it does not transfer.
  2. Bring consent and suppression state across first, so unsubscribes and bounces are honored from the first send in Campaign Monitor.
  3. QA migrated templates and segments inside Campaign Monitor, and send seed tests before any live campaign.
  4. Keep your current platform active until in-flight automations finish and Campaign Monitor is warmed and trusted.
// migrate it

start with the route playbook.

The agent prompt returns a route report with source exports, destination imports, skipped objects, and manual-review tasks. When it looks right, wire credentials and approve writes from a controlled machine.

inspect

destination coverage

npx mailexodus@latest info campaign-monitor

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=campaign-monitor

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