mailexodus
home/migrations/to Buttondown
// migrate to

move to Buttondown without rebuilding by hand.

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

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

bring your data into Buttondown.

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

analyzing Klaviyo…
source modeAutomated adapter
source exports8
Buttondown imports7
destination gapssegments, templates
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from klaviyo --to buttondown --dry-run
agentUse mailexodus skill: Klaviyo → Buttondown playbook
running…open the Klaviyo migration guide →
// fit

when Buttondown is the right move.

Buttondown is a strong fit for teams that want buttondown teams with subscriber data, campaigns, and automation branches that need a migration report before rebuild. 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 Buttondown objects.

// inbound

what Buttondown receives.

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

Partial automated adapter

Subscriber metadata maps to custom attributes. Tags map to tags. Newsletters can map to lists. Emails map to campaigns

Template and automation coverage is limited and should not be treated as full export support Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to Buttondown.

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

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=buttondown

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