mailexodus
home/migrations/to Loops
// migrate to

move to Loops without rebuilding by hand.

mailexodus normalizes your current platform into one portable schema, then checks what Loops can actually import. You get a route report before your agent writes anything.

agentUse mailexodus skill: your source → Loops playbook
// try it

bring your data into Loops.

Pick the platform you're leaving and generate a route playbook. The report shows what maps cleanly into Loops's model and what needs review — before you approve writes.

analyzing Klaviyo…
source modeAutomated adapter
source exports8
Loops imports5
destination gapstags, segments, suppressions, automations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from klaviyo --to loops --dry-run
agentUse mailexodus skill: Klaviyo → Loops playbook
running…open the Klaviyo migration guide →
// fit

when Loops is the right move.

Loops is a strong fit for teams that want loops teams moving lists, contact properties, campaigns, transactional templates, and workflow inventory into a cleaner operating model. The migration risk is rarely the CSV — it is the automation graph: triggers, delays, branches, template references, and consent state. mailexodus puts a portable schema in the middle so those objects are inspected before they become Loops objects.

// inbound

what Loops receives.

can import
  • +
    subscribers
  • +
    lists
  • +
    custom fields
  • +
    campaigns
  • +
    templates
needs review
  • ?
    campaigns
  • ?
    templates
not exposed for import
  • x
    tags
  • x
    segments
  • x
    suppressions
  • x
    automations
destination 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 Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to Loops.

  1. Authenticate your sending domain in Loops (SPF, DKIM, DMARC) and plan a warmup window — sender reputation is earned here, it does not transfer.
  2. Bring consent and suppression state across first, so unsubscribes and bounces are honored from the first send in Loops.
  3. QA migrated templates and segments inside Loops, and send seed tests before any live campaign.
  4. Keep your current platform active until in-flight automations finish and Loops is warmed and trusted.
// migrate it

start with the route playbook.

The agent prompt returns a route report with source exports, destination imports, skipped objects, and manual-review tasks. When it looks right, wire credentials and approve writes from a controlled machine.

inspect

destination coverage

npx mailexodus@latest info loops

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=loops

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