home/migrations/from Listmonk
// migrate from

leave Listmonk. keep the work.

mailexodus reads Listmonk over its API and normalizes subscribers, lists, custom fields, suppressions into one portable schema — so you move with a report, not a 40-item checklist.

agentUse mailexodus skill: Listmonk → Sequenzy playbook
// try it

see what moves out of Listmonk.

A live route check, computed from Listmonk's real API surface. Pick any destination to compare import support — nothing is written.

analyzing Listmonk
source modePartial automated adapter
source exports6
Mailchimp imports8
destination gapsautomations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from listmonk --to mailchimp --dry-run
agentUse mailexodus skill: ListmonkMailchimp playbook
// why teams leave

why teams leave Listmonk.

  • Listmonk migrations need an explicit boundary around what the API exposes.
  • Teams want a dry-run report before rebuilding subscribers, lists, custom fields, suppressions.
  • No native automation export
// transfer boundary

what mailexodus pulls from Listmonk.

can migrate
  • +
    subscribers
  • +
    lists
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
  • +
    templates
needs review
  • ?
    suppressions
  • ?
    campaigns
  • ?
    templates
cannot migrate
  • x
    tags
  • x
    segments
  • x
    automations
  • x
    sender reputation and domain warmup
  • x
    historical analytics, revenue attribution, and aggregate reporting
  • x
    contacts already mid-flight inside active automations
  • x
    A/B test results and provider-specific experiment history
  • x
    provider-native design blocks, product widgets, coupons, and private assets that are not exposed by API
source adapter

Partial automated adapter

Subscriber attribs map to custom attributes. Lists map to lists. SQL segmentation can map to segments only when the query is supplied or discovered. Campaigns and templates map to content items

No native automation export

// the playbook

how an agent migrates Listmonk → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Listmonk, map it to the portable schema, write it to the destination. mailexodus never writes; your agent does, with this report in hand.

01 · authenticate

Create a Listmonk API user/token with read permissions. Paste BASE_URL|USERNAME|ACCESS_TOKEN, or JSON with baseUrl, username, and apiKey

01subscribersmigrates
readGET /api/subscribers (Read subscribers from Listmonk.)
mapSubscriber attribs map to custom attributes. Lists map to lists. SQL segmentation can map to segments only when the query is supplied or discovered. Campaigns and templates 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/lists (Read lists from Listmonk.)
mapSubscriber attribs map to custom attributes. Lists map to lists. SQL segmentation can map to segments only when the query is supplied or discovered. Campaigns and templates 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.)
03custom fieldsmigrates
readGET /api/subscribers (Read custom fields from Listmonk.)
mapSubscriber attribs map to custom attributes. Lists map to lists. SQL segmentation can map to segments only when the query is supplied or discovered. Campaigns and templates 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.)
04suppressionsneeds review
readGET /api/subscribers?blocklisted=true (Read suppressions from Listmonk.)
mapSubscriber attribs map to custom attributes. Lists map to lists. SQL segmentation can map to segments only when the query is supplied or discovered. Campaigns and templates 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.)
05campaignsneeds review
readGET /api/campaigns (Read campaigns from Listmonk.)
mapSubscriber attribs map to custom attributes. Lists map to lists. SQL segmentation can map to segments only when the query is supplied or discovered. Campaigns and templates 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.)
06templatesneeds review
readGET /api/templates (Read templates from Listmonk.)
mapSubscriber attribs map to custom attributes. Lists map to lists. SQL segmentation can map to segments only when the query is supplied or discovered. Campaigns and templates map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_template (Write or stage templates in Sequenzy.)
stays behind
  • tags
  • segments
  • automations
  • sender reputation and domain warmup
  • historical analytics, revenue attribution, and aggregate reporting
  • contacts already mid-flight inside active automations
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.
// run it

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 Listmonk API user/token with read permissions. Paste BASE_URL|USERNAME|ACCESS_TOKEN, or JSON with baseUrl, username, and apiKey

inspect

provider coverage

npx mailexodus@latest info listmonk

guide

agent playbook

npx mailexodus@latest guide --from listmonk --to sequenzy

agentUse mailexodus skill: Listmonk → Sequenzy playbook