mailexodus
home/migrations/to Mailgun
// migrate to

move to Mailgun without rebuilding by hand.

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

agentUse mailexodus skill: your source → Mailgun playbook
// try it

bring your data into Mailgun.

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

analyzing Klaviyo…
source modeAutomated adapter
source exports8
Mailgun imports5
destination gapstags, segments, campaigns, automations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from klaviyo --to mailgun --dry-run
agentUse mailexodus skill: Klaviyo → Mailgun playbook
running…open the Klaviyo migration guide →
// fit

when Mailgun is the right move.

Mailgun is a strong fit for teams that want mailgun teams separating transactional templates and suppressions from lifecycle email operations. 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 Mailgun objects.

// inbound

what Mailgun receives.

can import
  • +
    subscribers
  • +
    lists
  • +
    custom fields
  • +
    suppressions
  • +
    templates
needs review
  • ?
    destination mappings still need final operator review
not exposed for import
  • x
    tags
  • x
    segments
  • x
    campaigns
  • x
    automations
destination adapter

Partial automated adapter

Mailing lists map to lists. Members map to subscribers. Member vars map to custom attributes. Suppressions map to suppression records. Templates map to transactional templates

Mailgun does not provide marketing campaign or automation export coverage Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to Mailgun.

  1. Authenticate your sending domain in Mailgun (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 Mailgun.
  3. QA migrated templates and segments inside Mailgun, and send seed tests before any live campaign.
  4. Keep your current platform active until in-flight automations finish and Mailgun 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 mailgun

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=mailgun

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