why teams leave Moosend.
- →Moosend migrations need an explicit boundary around what the API exposes.
- →Teams want a dry-run report before rebuilding subscribers, lists, segments, tags.
- →Standalone template and automation export were not verified
what mailexodus pulls from Moosend.
- +subscribers
- +lists
- +tags
- +segments
- +custom fields
- +campaigns
- ?segments
- ?campaigns
- xsuppressions
- xtemplates
- 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
Partial automated adapter
Mailing lists map to lists. Subscribers map to subscribers. Segments map to segments. Campaigns map to campaign content
Standalone template and automation export were not verified
how an agent migrates Moosend → Sequenzy.
This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Moosend, map it to the portable schema, write it to the destination. mailexodus never writes; your agent does, with this report in hand.
Create a Moosend API key with mailing list, subscriber, segment, custom field, and campaign read access. Paste the key, or JSON with apiKey
- suppressions
- templates
- 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: Create a Moosend API key with mailing list, subscriber, segment, custom field, and campaign read access. Paste the key, or JSON with apiKey
provider coverage
npx mailexodus@latest info moosend
agent playbook
npx mailexodus@latest guide --from moosend --to sequenzy
Use mailexodus skill: Moosend → Sequenzy playbook