mailexodus
home/migrations/to Mailtrap
// migrate to

move to Mailtrap without rebuilding by hand.

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

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

bring your data into Mailtrap.

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

analyzing Klaviyo…
source modeAutomated adapter
source exports8
Mailtrap imports5
destination gapstags, segments, campaigns, automations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from klaviyo --to mailtrap --dry-run
agentUse mailexodus skill: Klaviyo → Mailtrap playbook
running…open the Klaviyo migration guide →
// fit

when Mailtrap is the right move.

Mailtrap is a strong fit for teams that want mailtrap teams separating transactional templates and suppressions from lifecycle email operations. 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 Mailtrap objects.

// inbound

what Mailtrap receives.

can import
  • +
    subscribers
  • +
    lists
  • +
    custom fields
  • +
    suppressions
  • +
    templates
needs review
  • ?
    destination mappings still need final operator review
not exposed for import
  • x
    tags
  • x
    segments
  • x
    campaigns
  • x
    automations
destination 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 Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to Mailtrap.

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

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=mailtrap

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