home/migrations/from EmailOctopus
// migrate from

leave EmailOctopus. keep the work.

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

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

see what moves out of EmailOctopus.

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

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

why teams leave EmailOctopus.

  • EmailOctopus migrations need an explicit boundary around what the API exposes.
  • Teams want a dry-run report before rebuilding subscribers, lists, tags, custom fields.
  • No standalone saved segment, template, or automation retrieval was verified
// transfer boundary

what mailexodus pulls from EmailOctopus.

can migrate
  • +
    subscribers
  • +
    lists
  • +
    tags
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
needs review
  • ?
    suppressions
  • ?
    campaigns
cannot migrate
  • x
    segments
  • x
    templates
  • 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

List contacts map to subscribers. Fields map to custom attributes. Tags map to tags. Campaigns map to campaign content

No standalone saved segment, template, or automation retrieval was verified

// the playbook

how an agent migrates EmailOctopus → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from EmailOctopus, 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 an EmailOctopus API key with read access to lists, contacts, tags, campaigns, and reports. Paste the key, or JSON with apiKey

01subscribersmigrates
readGET /api/1.6/lists/{list_id}/contacts (Read subscribers from EmailOctopus.)
mapList contacts map to subscribers. Fields map to custom attributes. Tags map to tags. Campaigns map to campaign content 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/1.6/lists (Read lists from EmailOctopus.)
mapList contacts map to subscribers. Fields map to custom attributes. Tags map to tags. Campaigns map to campaign content 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.)
03tagsmigrates
readGET /api/1.6/lists/{list_id}/tags (Read tags from EmailOctopus.)
mapList contacts map to subscribers. Fields map to custom attributes. Tags map to tags. Campaigns map to campaign content mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_tag (Write or stage tags in Sequenzy.)
04custom fieldsmigrates
readGET /api/1.6/lists/{list_id} (Read custom fields from EmailOctopus.)
mapList contacts map to subscribers. Fields map to custom attributes. Tags map to tags. Campaigns map to campaign content 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.)
05suppressionsneeds review
readGET /api/1.6/lists/{list_id}/contacts?status=unsubscribed (Read suppressions from EmailOctopus.)
mapList contacts map to subscribers. Fields map to custom attributes. Tags map to tags. Campaigns map to campaign content 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.)
06campaignsneeds review
readGET /api/1.6/campaigns (Read campaigns from EmailOctopus.)
mapList contacts map to subscribers. Fields map to custom attributes. Tags map to tags. Campaigns map to campaign content mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_campaign (Write or stage campaigns in Sequenzy.)
stays behind
  • segments
  • templates
  • 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 an EmailOctopus API key with read access to lists, contacts, tags, campaigns, and reports. Paste the key, or JSON with apiKey

inspect

provider coverage

npx mailexodus@latest info emailoctopus

guide

agent playbook

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

agentUse mailexodus skill: EmailOctopus → Sequenzy playbook