why teams leave MailerLite.
- →MailerLite migrations need an explicit boundary around what the API exposes.
- →Teams want a dry-run report before rebuilding subscribers, lists, segments, custom fields.
- →Automation details may need review before enabling imported sequences
what mailexodus pulls from MailerLite.
can migrate
- +subscribers
- +lists
- +segments
- +custom fields
- +suppressions
- +campaigns
- +automations
needs review
- ?Automation details may need review before enabling imported sequences
cannot migrate
- xtags
- xtemplates
- 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
source adapter
// the playbookAutomated adapter
Groups map to lists. Segments map to segments. Fields map to custom attributes. Campaigns and automation emails map to content items
Automation details may need review before enabling imported sequences
how an agent migrates MailerLite → Sequenzy.
This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from MailerLite, map it to the portable schema, write it to the destination. mailexodus never writes; your agent does, with this report in hand.
01 · authenticate
In MailerLite, open Integrations, API, then create or copy a token with read access to subscribers, groups, segments, fields, campaigns, automations, and suppressions
01subscribersmigrates
readGET /api/subscribers (Read subscribers from MailerLite.)
mapGroups map to lists. Segments map to segments. Fields map to custom attributes. Campaigns and automation emails map to content items 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/groups (Read lists from MailerLite.)
mapGroups map to lists. Segments map to segments. Fields map to custom attributes. Campaigns and automation emails map to content items 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.)
03segmentsmigrates
readGET /api/segments (Read segments from MailerLite.)
mapGroups map to lists. Segments map to segments. Fields map to custom attributes. Campaigns and automation emails map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_segment (Write or stage segments in Sequenzy.)
04custom fieldsmigrates
readGET /api/fields (Read custom fields from MailerLite.)
mapGroups map to lists. Segments map to segments. Fields map to custom attributes. Campaigns and automation emails map to content items 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.)
05suppressionsmigrates
readGET /api/subscribers?filter[status]=unsubscribed (Read suppressions from MailerLite.)
mapGroups map to lists. Segments map to segments. Fields map to custom attributes. Campaigns and automation emails map to content items 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.)
06campaignsmigrates
readGET /api/campaigns (Read campaigns from MailerLite.)
mapGroups map to lists. Segments map to segments. Fields map to custom attributes. Campaigns and automation emails map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_campaign (Write or stage campaigns in Sequenzy.)
07automationsmigrates
readGET /api/automations (Read automations from MailerLite.)
mapGroups map to lists. Segments map to segments. Fields map to custom attributes. Campaigns and automation emails map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_sequence (Write or stage automations in Sequenzy.) POST insert_sequence_step (Write or stage automations in Sequenzy.)
stays behind
- tags
- templates
- sender reputation and domain warmup
- historical analytics, revenue attribution, and aggregate reporting
- contacts already mid-flight inside active automations
- A/B test results and provider-specific experiment history
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.
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 MailerLite, open Integrations, API, then create or copy a token with read access to subscribers, groups, segments, fields, campaigns, automations, and suppressions
inspect
provider coverage
npx mailexodus@latest info mailerlite
guide
agent playbook
npx mailexodus@latest guide --from mailerlite --to sequenzy
agent
Use mailexodus skill: MailerLite → Sequenzy playbook