mailexodus
home/migrations/to Sender
// migrate to

move to Sender without rebuilding by hand.

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

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

bring your data into Sender.

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

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

when Sender is the right move.

Sender is a strong fit for teams that want sender teams moving subscribers, groups, segments, custom fields, and campaigns with a conservative migration report. 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 Sender objects.

// inbound

what Sender receives.

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

Partial automated adapter

Groups map to lists. Subscribers map to subscribers. Segments map to segments. Campaigns map to campaign content

Tags, reusable templates, and automation workflow import/export were not verified as first-class API surfaces Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to Sender.

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

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=sender

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