mailexodus
home/migrations/to Brevo
// migrate to

move to Brevo without rebuilding by hand.

mailexodus normalizes your current platform into one portable schema, then checks what Brevo can actually import. You get a route report before your agent writes anything.

agentUse mailexodus skill: your source → Brevo playbook
// try it

bring your data into Brevo.

Pick the platform you're leaving and generate a route playbook. The report shows what maps cleanly into Brevo's model and what needs review — before you approve writes.

analyzing Klaviyo…
source modeAutomated adapter
source exports8
Brevo imports6
destination gapstags, segments, automations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from klaviyo --to brevo --dry-run
agentUse mailexodus skill: Klaviyo → Brevo playbook
running…open the Klaviyo migration guide →
// fit

when Brevo is the right move.

Brevo is a strong fit for teams that want brevo teams with subscriber data, campaigns, and automation branches that need a migration report before rebuild. The migration risk is rarely the CSV — it is the automation graph: triggers, delays, branches, template references, and consent state. mailexodus puts a portable schema in the middle so those objects are inspected before they become Brevo objects.

// inbound

what Brevo receives.

can import
  • +
    subscribers
  • +
    lists
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
  • +
    templates
needs review
  • ?
    destination mappings still need final operator review
not exposed for import
  • x
    tags
  • x
    segments
  • x
    automations
destination 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

Brevo can receive contacts, lists, contact attributes, suppressions, email campaigns, and SMTP templates through exposed APIs. Saved segments and automation workflows are not exposed as clean create/import surfaces; rebuild them in Brevo using migrated attributes and draft content. Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to Brevo.

  1. Authenticate your sending domain in Brevo (SPF, DKIM, DMARC) and plan a warmup window — sender reputation is earned here, it does not transfer.
  2. Bring consent and suppression state across first, so unsubscribes and bounces are honored from the first send in Brevo.
  3. QA migrated templates and segments inside Brevo, and send seed tests before any live campaign.
  4. Keep your current platform active until in-flight automations finish and Brevo is warmed and trusted.
// migrate it

start with the route playbook.

The agent prompt returns a route report with source exports, destination imports, skipped objects, and manual-review tasks. When it looks right, wire credentials and approve writes from a controlled machine.

inspect

destination coverage

npx mailexodus@latest info brevo

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=brevo

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