mailexodus
home/migrations/to Mailjet
// migrate to

move to Mailjet without rebuilding by hand.

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

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

bring your data into Mailjet.

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

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

when Mailjet is the right move.

Mailjet is a strong fit for teams that want mailjet teams moving contacts, contact lists, custom fields, suppressions, campaigns, and templates into a cleaner operating model. 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 Mailjet objects.

// inbound

what Mailjet receives.

can import
  • +
    subscribers
  • +
    lists
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
  • +
    templates
needs review
  • ?
    destination mappings still need final operator review
not exposed for import
  • x
    tags
  • x
    segments
  • x
    automations
destination adapter

Automated adapter

Contacts map to subscribers. Contact lists map to lists. Contact data maps to custom attributes. Campaigns and templates map to content items

Automation import is not part of current native coverage Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to Mailjet.

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

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=mailjet

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