mailexodus
home/migrations/from Brevo
// migrate from

leave Brevo. keep the work.

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

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

see what moves out of Brevo.

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

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

why teams leave Brevo.

  • →
    Brevo migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, segments, custom fields.
  • →
    Automation detail can be partial depending on Brevo plan
// transfer boundary

what mailexodus pulls from Brevo.

can migrate
  • +
    subscribers
  • +
    lists
  • +
    segments
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
  • +
    templates
  • +
    automations
needs review
  • ?
    Automation detail can be partial depending on Brevo plan
cannot migrate
  • x
    tags
  • 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 with attributes. Lists and filters map to lists or segments. Campaigns, templates, and automation email content map to content items

Automation detail can be partial depending on Brevo plan

// the playbook

how an agent migrates Brevo → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Brevo, 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 Brevo, open SMTP & API, API keys, then create or copy a v3 API key with read access to contacts, lists, campaigns, templates, and automations

01subscribersmigrates
readGET /v3/contacts (Read subscribers from Brevo.)
mapContacts map to subscribers with attributes. Lists and filters map to lists or segments. Campaigns, templates, and automation email content map to 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 /v3/contacts/lists (Read lists from Brevo.)
mapContacts map to subscribers with attributes. Lists and filters map to lists or segments. Campaigns, templates, and automation email content map to 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.)
03segmentsmigrates
readGET /v3/contacts/segments (Read segments from Brevo.)
mapContacts map to subscribers with attributes. Lists and filters map to lists or segments. Campaigns, templates, and automation email content map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_segment (Write or stage segments in Sequenzy.)
04custom fieldsmigrates
readGET /v3/contacts/attributes (Read custom fields from Brevo.)
mapContacts map to subscribers with attributes. Lists and filters map to lists or segments. Campaigns, templates, and automation email content map to 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.)
05suppressionsmigrates
readGET /v3/smtp/blockedContacts (Read suppressions from Brevo.) GET /v3/contacts (Read suppressions from Brevo.)
mapContacts map to subscribers with attributes. Lists and filters map to lists or segments. Campaigns, templates, and automation email content map to content items 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.)
06campaignsmigrates
readGET /v3/emailCampaigns (Read campaigns from Brevo.)
mapContacts map to subscribers with attributes. Lists and filters map to lists or segments. Campaigns, templates, and automation email content map to 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.)
07templatesmigrates
readGET /v3/smtp/templates (Read templates from Brevo.)
mapContacts map to subscribers with attributes. Lists and filters map to lists or segments. Campaigns, templates, and automation email content map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_template (Write or stage templates in Sequenzy.)
08automationsmigrates
readGET /v3/marketing/automation/workflows (Read automations from Brevo.)
mapContacts map to subscribers with attributes. Lists and filters map to lists or segments. Campaigns, templates, and automation email content map to 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
  • tags
  • 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
  • provider-native design blocks, product widgets, coupons, and private assets that are not exposed by API
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 Brevo, open SMTP & API, API keys, then create or copy a v3 API key with read access to contacts, lists, campaigns, templates, and automations

inspect

provider coverage

npx mailexodus@latest info brevo

guide

agent playbook

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

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