mailexodus
home/migrations/from Mailtrap
// migrate from

leave Mailtrap. keep the work.

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

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

see what moves out of Mailtrap.

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

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

why teams leave Mailtrap.

  • →
    Mailtrap migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, custom fields, suppressions.
  • →
    Campaign, segment, and automation retrieval were not verified
// transfer boundary

what mailexodus pulls from Mailtrap.

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

Contacts map to subscribers. Lists map to lists. Fields map to custom attributes. Templates map to templates

Campaign, segment, and automation retrieval were not verified

// the playbook

how an agent migrates Mailtrap → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Mailtrap, 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 Mailtrap API token with contacts, contact lists, contact fields, suppressions, and templates access. Paste the token, or JSON with apiKey

01subscribersmigrates
readGET /api/accounts/{account_id}/contacts (Read subscribers from Mailtrap.)
mapContacts map to subscribers. Lists map to lists. Fields map to custom attributes. Templates map to 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.)
02listsmigrates
readGET /api/accounts/{account_id}/contact_lists (Read lists from Mailtrap.)
mapContacts map to subscribers. Lists map to lists. Fields map to custom attributes. Templates map to templates 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.)
03custom fieldsmigrates
readGET /api/accounts/{account_id}/contact_fields (Read custom fields from Mailtrap.)
mapContacts map to subscribers. Lists map to lists. Fields map to custom attributes. Templates map to templates 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.)
04suppressionsneeds review
readGET /api/accounts/{account_id}/suppressions (Read suppressions from Mailtrap.)
mapContacts map to subscribers. Lists map to lists. Fields map to custom attributes. Templates map to 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.)
05templatesneeds review
readGET /api/accounts/{account_id}/email_templates (Read templates from Mailtrap.)
mapContacts map to subscribers. Lists map to lists. Fields map to custom attributes. Templates map to 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
  • tags
  • segments
  • campaigns
  • 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 Mailtrap API token with contacts, contact lists, contact fields, suppressions, and templates access. Paste the token, or JSON with apiKey

inspect

provider coverage

npx mailexodus@latest info mailtrap

guide

agent playbook

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

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