mailexodus
home/migrations/from ActiveCampaign
// migrate from

leave ActiveCampaign. keep the work.

mailexodus reads ActiveCampaign 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: ActiveCampaign → Sequenzy playbook
// try it

see what moves out of ActiveCampaign.

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

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

why teams leave ActiveCampaign.

  • →
    ActiveCampaign migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, tags, custom fields.
  • →
    Some automation metadata depends on the account's API visibility
// transfer boundary

what mailexodus pulls from ActiveCampaign.

can migrate
  • +
    subscribers
  • +
    lists
  • +
    tags
  • +
    custom fields
  • +
    campaigns
  • +
    automations
needs review
  • ?
    Some automation metadata depends on the account's API visibility
cannot migrate
  • 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

Contacts map to subscribers. Lists, tags, and custom fields map directly. Campaigns and automation emails map to draft content items

Some automation metadata depends on the account's API visibility

// the playbook

how an agent migrates ActiveCampaign → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from ActiveCampaign, 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 ActiveCampaign, open Settings, Developer, then copy your API URL and API key. Paste them separated by a pipe, for example https://account.api-us1.com|API_KEY. JSON with apiUrl and apiToken is also accepted

01subscribersmigrates
readGET /api/3/contacts (Read subscribers from ActiveCampaign.)
mapContacts map to subscribers. Lists, tags, and custom fields map directly. Campaigns and automation emails map to draft 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/3/lists (Read lists from ActiveCampaign.) GET /api/3/contactLists (Read lists from ActiveCampaign.)
mapContacts map to subscribers. Lists, tags, and custom fields map directly. Campaigns and automation emails map to draft 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.)
03tagsmigrates
readGET /api/3/tags (Read tags from ActiveCampaign.) GET /api/3/contactTags (Read tags from ActiveCampaign.)
mapContacts map to subscribers. Lists, tags, and custom fields map directly. Campaigns and automation emails map to draft content items 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/3/fields (Read custom fields from ActiveCampaign.) GET /api/3/fieldValues (Read custom fields from ActiveCampaign.)
mapContacts map to subscribers. Lists, tags, and custom fields map directly. Campaigns and automation emails map to draft 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.)
05campaignsmigrates
readGET /api/3/campaigns (Read campaigns from ActiveCampaign.) GET /api/3/messages (Read campaigns from ActiveCampaign.)
mapContacts map to subscribers. Lists, tags, and custom fields map directly. Campaigns and automation emails map to draft 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.)
06automationsmigrates
readGET /api/3/automations (Read automations from ActiveCampaign.) GET /api/3/automationLists (Read automations from ActiveCampaign.)
mapContacts map to subscribers. Lists, tags, and custom fields map directly. Campaigns and automation emails map to draft content items 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
  • segments
  • suppressions
  • templates
  • 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: In ActiveCampaign, open Settings, Developer, then copy your API URL and API key. Paste them separated by a pipe, for example https://account.api-us1.com|API_KEY. JSON with apiUrl and apiToken is also accepted

inspect

provider coverage

npx mailexodus@latest info active-campaign

guide

agent playbook

npx mailexodus@latest guide --from active-campaign --to sequenzy

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