mailexodus
home/migrations/from MailerSend
// migrate from

leave MailerSend. keep the work.

mailexodus reads MailerSend over its API and normalizes subscribers, suppressions, templates into one portable schema — so you move with a report, not a 40-item checklist.

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

see what moves out of MailerSend.

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

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

why teams leave MailerSend.

  • →
    MailerSend migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, suppressions, templates.
  • →
    Campaign, segment, list, and automation export were not verified
// transfer boundary

what mailexodus pulls from MailerSend.

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

Recipients map to subscribers when email identity and consent state are sufficient. Suppressions map to suppression records. Templates map to transactional templates

Campaign, segment, list, and automation export were not verified

// the playbook

how an agent migrates MailerSend → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from MailerSend, 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 MailerSend API token with recipients_read, suppressions_read, domains_read, and template access. Paste the token, or JSON with apiKey

01subscribersmigrates
readGET /v1/recipients (Read subscribers from MailerSend.)
mapRecipients map to subscribers when email identity and consent state are sufficient. Suppressions map to suppression records. Templates map to transactional templates 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.)
02suppressionsneeds review
readGET /v1/suppressions (Read suppressions from MailerSend.)
mapRecipients map to subscribers when email identity and consent state are sufficient. Suppressions map to suppression records. Templates map to transactional templates 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.)
03templatesneeds review
readGET /v1/templates (Read templates from MailerSend.)
mapRecipients map to subscribers when email identity and consent state are sufficient. Suppressions map to suppression records. Templates map to transactional templates mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_template (Write or stage templates in Sequenzy.)
stays behind
  • lists
  • tags
  • segments
  • custom fields
  • campaigns
  • automations
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 MailerSend API token with recipients_read, suppressions_read, domains_read, and template access. Paste the token, or JSON with apiKey

inspect

provider coverage

npx mailexodus@latest info mailersend

guide

agent playbook

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

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