mailexodus
home/migrations/from Drip
// migrate from

leave Drip. keep the work.

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

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

see what moves out of Drip.

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

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

why teams leave Drip.

  • →
    Drip migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, tags, custom fields, campaigns.
  • →
    List-like structure is inferred from tags and campaigns; workflow graph import is not exposed as a clean write surface
// transfer boundary

what mailexodus pulls from Drip.

can migrate
  • +
    subscribers
  • +
    tags
  • +
    custom fields
  • +
    campaigns
  • +
    automations
needs review
  • ?
    List-like structure is inferred from tags and campaigns; workflow graph import is not exposed as a clean write surface
cannot migrate
  • x
    lists
  • x
    segments
  • x
    suppressions
  • x
    templates
  • 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

Subscribers map to subscribers. Tags and custom fields map directly. Broadcast and campaign emails map to content items. Workflow email steps map to automation inventory when bodies are available

List-like structure is inferred from tags and campaigns; workflow graph import is not exposed as a clean write surface

// the playbook

how an agent migrates Drip → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Drip, 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 Drip, open User Settings, API Token, then paste a token with read access to subscribers, tags, custom fields, broadcasts, campaigns, and workflows

01subscribersmigrates
readGET /v2/{account_id}/subscribers (Read subscribers from Drip.)
mapSubscribers map to subscribers. Tags and custom fields map directly. Broadcast and campaign emails map to content items. Workflow email steps map to automation inventory when bodies are available 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.)
02tagsmigrates
readGET /v2/{account_id}/tags (Read tags from Drip.)
mapSubscribers map to subscribers. Tags and custom fields map directly. Broadcast and campaign emails map to content items. Workflow email steps map to automation inventory when bodies are available mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_tag (Write or stage tags in Sequenzy.)
03custom fieldsmigrates
readGET /v2/{account_id}/custom_field_identifiers (Read custom fields from Drip.)
mapSubscribers map to subscribers. Tags and custom fields map directly. Broadcast and campaign emails map to content items. Workflow email steps map to automation inventory when bodies are available 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.)
04campaignsmigrates
readGET /v2/{account_id}/broadcasts (Read campaigns from Drip.) GET /v2/{account_id}/campaigns (Read campaigns from Drip.)
mapSubscribers map to subscribers. Tags and custom fields map directly. Broadcast and campaign emails map to content items. Workflow email steps map to automation inventory when bodies are available mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_campaign (Write or stage campaigns in Sequenzy.)
05automationsmigrates
readGET /v2/{account_id}/workflows (Read automations from Drip.)
mapSubscribers map to subscribers. Tags and custom fields map directly. Broadcast and campaign emails map to content items. Workflow email steps map to automation inventory when bodies are available 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
  • lists
  • segments
  • suppressions
  • templates
  • 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 Drip, open User Settings, API Token, then paste a token with read access to subscribers, tags, custom fields, broadcasts, campaigns, and workflows

inspect

provider coverage

npx mailexodus@latest info drip

guide

agent playbook

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

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