mailexodus
home/migrations/from Sender
// migrate from

leave Sender. keep the work.

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

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

see what moves out of Sender.

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

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

why teams leave Sender.

  • →
    Sender migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, segments, custom fields.
  • →
    Tags, reusable templates, and automation workflow import/export were not verified as first-class API surfaces
// transfer boundary

what mailexodus pulls from Sender.

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

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

// the playbook

how an agent migrates Sender → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Sender, 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 Sender API token with read access to subscribers, groups, segments, fields, and campaigns. Paste the token, or JSON with apiKey

01subscribersmigrates
readGET /v2/subscribers (Read subscribers from Sender.)
mapGroups map to lists. Subscribers map to subscribers. Segments map to segments. Campaigns map to campaign content 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 /v2/groups (Read lists from Sender.)
mapGroups map to lists. Subscribers map to subscribers. Segments map to segments. Campaigns map to campaign content 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.)
03segmentsneeds review
readGET /v2/segments (Read segments from Sender.)
mapGroups map to lists. Subscribers map to subscribers. Segments map to segments. Campaigns map to campaign content mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_segment (Write or stage segments in Sequenzy.)
04custom fieldsmigrates
readGET /v2/custom-fields (Read custom fields from Sender.)
mapGroups map to lists. Subscribers map to subscribers. Segments map to segments. Campaigns map to campaign content 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.)
05campaignsneeds review
readGET /v2/campaigns (Read campaigns from Sender.)
mapGroups map to lists. Subscribers map to subscribers. Segments map to segments. Campaigns map to campaign content mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_campaign (Write or stage campaigns in Sequenzy.)
stays behind
  • tags
  • suppressions
  • templates
  • automations
  • sender reputation and domain warmup
  • historical analytics, revenue attribution, and aggregate reporting
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 Sender API token with read access to subscribers, groups, segments, fields, and campaigns. Paste the token, or JSON with apiKey

inspect

provider coverage

npx mailexodus@latest info sender

guide

agent playbook

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

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