mailexodus
home/migrations/from Buttondown
// migrate from

leave Buttondown. keep the work.

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

agentUse mailexodus skill: Buttondown → Sequenzy playbook
// try it

see what moves out of Buttondown.

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

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

why teams leave Buttondown.

  • →
    Buttondown migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, tags, custom fields.
  • →
    Template and automation coverage is limited and should not be treated as full export support
// transfer boundary

what mailexodus pulls from Buttondown.

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

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

// the playbook

how an agent migrates Buttondown → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Buttondown, 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 a Buttondown API key with read access to subscribers, emails, tags, newsletters, and automations. Paste the API key, or JSON with apiKey

01subscribersmigrates
readGET /v1/subscribers (Read subscribers from Buttondown.)
mapSubscriber metadata maps to custom attributes. Tags map to tags. Newsletters can map to lists. Emails 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 /v1/newsletters (Read lists from Buttondown.)
mapSubscriber metadata maps to custom attributes. Tags map to tags. Newsletters can map to lists. Emails 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.)
03tagsmigrates
readGET /v1/tags (Read tags from Buttondown.)
mapSubscriber metadata maps to custom attributes. Tags map to tags. Newsletters can map to lists. Emails map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_tag (Write or stage tags in Sequenzy.)
04custom fieldsmigrates
readGET /v1/subscribers (Read custom fields from Buttondown.)
mapSubscriber metadata maps to custom attributes. Tags map to tags. Newsletters can map to lists. Emails 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 /v1/subscribers?type=unsubscribed (Read suppressions from Buttondown.)
mapSubscriber metadata maps to custom attributes. Tags map to tags. Newsletters can map to lists. Emails 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 /v1/emails (Read campaigns from Buttondown.)
mapSubscriber metadata maps to custom attributes. Tags map to tags. Newsletters can map to lists. Emails 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.)
07automationsneeds review
readGET /v1/emails?email_type=automation (Read automations from Buttondown.)
mapSubscriber metadata maps to custom attributes. Tags map to tags. Newsletters can map to lists. Emails map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_sequence (Write or stage automations in Sequenzy.) POST insert_sequence_step (Write or stage automations in Sequenzy.)
stays behind
  • segments
  • templates
  • 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 a Buttondown API key with read access to subscribers, emails, tags, newsletters, and automations. Paste the API key, or JSON with apiKey

inspect

provider coverage

npx mailexodus@latest info buttondown

guide

agent playbook

npx mailexodus@latest guide --from buttondown --to sequenzy

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