mailexodus
home/migrations/from AWeber
// migrate from

leave AWeber. keep the work.

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

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

see what moves out of AWeber.

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

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

why teams leave AWeber.

  • →
    AWeber migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, segments, tags.
  • →
    AWeber's newer automation campaign builder is not fully exposed by the public API
// transfer boundary

what mailexodus pulls from AWeber.

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

Subscribers map to subscribers. Lists map to lists. Tags and custom fields map directly. Broadcasts and follow-ups map to campaigns when content is available

AWeber's newer automation campaign builder is not fully exposed by the public API

// the playbook

how an agent migrates AWeber → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from AWeber, 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 AWeber OAuth access token with account.read, list.read, subscriber.read, and email.read scopes. Paste ACCOUNT_ID|ACCESS_TOKEN, or JSON with accountId and accessToken

01subscribersmigrates
readGET /1.0/accounts/{account_id}/lists/{list_id}/subscribers (Read subscribers from AWeber.)
mapSubscribers map to subscribers. Lists map to lists. Tags and custom fields map directly. Broadcasts and follow-ups map to campaigns when content is 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.)
02listsmigrates
readGET /1.0/accounts/{account_id}/lists (Read lists from AWeber.)
mapSubscribers map to subscribers. Lists map to lists. Tags and custom fields map directly. Broadcasts and follow-ups map to campaigns when content is available 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 /1.0/accounts/{account_id}/lists/{list_id}/subscribers?ws.op=find&tag={tag} (Read tags from AWeber.)
mapSubscribers map to subscribers. Lists map to lists. Tags and custom fields map directly. Broadcasts and follow-ups map to campaigns when content is 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.)
04segmentsneeds review
readGET /1.0/accounts/{account_id}/lists/{list_id}/segments (Read segments from AWeber.)
mapSubscribers map to subscribers. Lists map to lists. Tags and custom fields map directly. Broadcasts and follow-ups map to campaigns when content is available mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_segment (Write or stage segments in Sequenzy.)
05custom fieldsmigrates
readGET /1.0/accounts/{account_id}/lists/{list_id}/custom_fields (Read custom fields from AWeber.)
mapSubscribers map to subscribers. Lists map to lists. Tags and custom fields map directly. Broadcasts and follow-ups map to campaigns when content is 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.)
06suppressionsneeds review
readGET /1.0/accounts/{account_id}/lists/{list_id}/subscribers?status=unsubscribed (Read suppressions from AWeber.)
mapSubscribers map to subscribers. Lists map to lists. Tags and custom fields map directly. Broadcasts and follow-ups map to campaigns when content is available 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.)
07campaignsneeds review
readGET /1.0/accounts/{account_id}/lists/{list_id}/broadcasts (Read campaigns from AWeber.) GET /1.0/accounts/{account_id}/lists/{list_id}/followups (Read campaigns from AWeber.)
mapSubscribers map to subscribers. Lists map to lists. Tags and custom fields map directly. Broadcasts and follow-ups map to campaigns when content is 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.)
stays behind
  • templates
  • automations
  • sender reputation and domain warmup
  • historical analytics, revenue attribution, and aggregate reporting
  • contacts already mid-flight inside active automations
  • A/B test results and provider-specific experiment history
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 AWeber OAuth access token with account.read, list.read, subscriber.read, and email.read scopes. Paste ACCOUNT_ID|ACCESS_TOKEN, or JSON with accountId and accessToken

inspect

provider coverage

npx mailexodus@latest info aweber

guide

agent playbook

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

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