why teams leave Mailjet.
- →Mailjet migrations need an explicit boundary around what the API exposes.
- →Teams want a dry-run report before rebuilding subscribers, lists, custom fields, suppressions.
- →Automation import is not part of current native coverage
what mailexodus pulls from Mailjet.
- +subscribers
- +lists
- +custom fields
- +suppressions
- +campaigns
- +templates
- ?Automation import is not part of current native coverage
- xtags
- xsegments
- xautomations
- xsender reputation and domain warmup
- xhistorical analytics, revenue attribution, and aggregate reporting
- xcontacts already mid-flight inside active automations
- xA/B test results and provider-specific experiment history
- xprovider-native design blocks, product widgets, coupons, and private assets that are not exposed by API
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
how an agent migrates Mailjet → Sequenzy.
This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Mailjet, map it to the portable schema, write it to the destination. mailexodus never writes; your agent does, with this report in hand.
In Mailjet, open Account Settings, REST API, then paste credentials in API_KEY:API_SECRET format
- tags
- segments
- automations
- sender reputation and domain warmup
- historical analytics, revenue attribution, and aggregate reporting
- contacts already mid-flight inside active automations
- 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.
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: In Mailjet, open Account Settings, REST API, then paste credentials in API_KEY:API_SECRET format
provider coverage
npx mailexodus@latest info mailjet
agent playbook
npx mailexodus@latest guide --from mailjet --to sequenzy
Use mailexodus skill: Mailjet → Sequenzy playbook