mailexodus
home/migrations/from Loops
// migrate from

leave Loops. keep the work.

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

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

see what moves out of Loops.

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

analyzing Loops…
source modeAutomated adapter
source exports5
Mailchimp imports8
destination gapsautomations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from loops --to mailchimp --dry-run
agentUse mailexodus skill: Loops → Mailchimp playbook
running…open the Loops migration guide →
// why teams leave

why teams leave Loops.

  • →
    Loops migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding lists, custom fields, campaigns, templates.
  • →
    Subscriber discovery is limited by the available Loops API lookup surfaces. Workflow APIs are alpha and expose inventory/graph details, not workflow creation
// transfer boundary

what mailexodus pulls from Loops.

can migrate
  • +
    lists
  • +
    custom fields
  • +
    campaigns
  • +
    templates
  • +
    automations
needs review
  • ?
    Subscriber discovery is limited by the available Loops API lookup surfaces. Workflow APIs are alpha and expose inventory/graph details, not workflow creation
cannot migrate
  • x
    subscribers
  • x
    tags
  • x
    segments
  • x
    suppressions
  • 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

Automated adapter

Lists map to lists. Contact properties map to custom attributes. Campaigns and transactional emails map to content items. Workflows map to automation inventory for review

Subscriber discovery is limited by the available Loops API lookup surfaces. Workflow APIs are alpha and expose inventory/graph details, not workflow creation

// the playbook

how an agent migrates Loops → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Loops, 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 Loops, open Settings, API, then paste an API key with access to mailing lists, contact properties, campaigns, transactional emails, workflow inventory, and contact lookup/create/update

01listsmigrates
readGET /v1/lists (Read lists from Loops.)
mapLists map to lists. Contact properties map to custom attributes. Campaigns and transactional emails map to content items. Workflows map to automation inventory for review 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.)
02custom fieldsmigrates
readGET /v1/contacts/properties (Read custom fields from Loops.)
mapLists map to lists. Contact properties map to custom attributes. Campaigns and transactional emails map to content items. Workflows map to automation inventory for review 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.)
03campaignsmigrates
readGET /v1/campaigns (Read campaigns from Loops.)
mapLists map to lists. Contact properties map to custom attributes. Campaigns and transactional emails map to content items. Workflows map to automation inventory for review mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_campaign (Write or stage campaigns in Sequenzy.)
04templatesmigrates
readGET /v1/transactional (Read templates from Loops.) GET /v1/transactional/{id} (Read templates from Loops.) GET /v1/email-messages/{id} (Read templates from Loops.)
mapLists map to lists. Contact properties map to custom attributes. Campaigns and transactional emails map to content items. Workflows map to automation inventory for review mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_template (Write or stage templates in Sequenzy.)
05automationsmigrates
readGET /v1/workflows (Read automations from Loops.) GET /v1/workflows/{id} (Read automations from Loops.) GET /v1/workflows/{id}/nodes/{nodeId} (Read automations from Loops.)
mapLists map to lists. Contact properties map to custom attributes. Campaigns and transactional emails map to content items. Workflows map to automation inventory for review 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
  • subscribers
  • tags
  • segments
  • suppressions
  • sender reputation and domain warmup
  • historical analytics, revenue attribution, and aggregate reporting
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: In Loops, open Settings, API, then paste an API key with access to mailing lists, contact properties, campaigns, transactional emails, workflow inventory, and contact lookup/create/update

inspect

provider coverage

npx mailexodus@latest info loops

guide

agent playbook

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

agentUse mailexodus skill: Loops → Sequenzy playbook
compare Loops alternatives →browse every migration page →