Brevo migration · automations

Your Brevo automations, rebuilt from a chat.

Brevo's API can't export automation workflows (only contacts, lists, templates and campaigns). So flows must be rebuilt — but NewsletterMCP makes it fast: describe each Brevo automation to Claude and it builds the flow via MCP. See which Brevo flow types are natively rebuildable.

The honest constraint: Brevo's public API exposes contacts, lists, templates and campaigns — but not automation workflows (triggers, waits, branches). No tool can auto-export them. So flows are rebuilt, not imported. The good news: with NewsletterMCP you rebuild them by describing each flow to Claude, which calls flow_create / flow_add_step — minutes, not a dashboard.

How to migrate your automations

Migrate the data first (via API): contacts, lists, tags, suppression, templates and past campaigns import cleanly — consent status and trail preserved, no forced re-confirmation.
Inventory your Brevo flows: list them (active first) from the Brevo automation view.
Rebuild each active flow from chat: describe the trigger → waits → mails → tags to Claude; it builds the flow in NewsletterMCP live.
Activate — your flows run on your own SES sending reputation, EU/DOI-compliant.

Which Brevo flow types are natively rebuildable

Brevo flow type	NewsletterMCP	How
DOI / double opt-in flows	✅ Native	Built-in DOI: subscribe → confirm → tag/list
Waitlist flows	✅ Native	subscribe/tag trigger → wait → send
Funnel (awareness → consideration → conversion)	✅ Native	Multi-step wait + send, tag-gated
Lead-magnet flows (e-book, content unlock)	✅ Native	tag trigger → send sequence
Tagging & list hygiene	✅ Native	add/remove tag steps + suppression
Giveaway / testcode (Meta, IG)	✅ Native	tag_added (ad lead) → DOI → send
Test + result mail (score-segmented)	✅ Via tags	Score comes in as a tag/attribute → tag trigger
Reactivation of inactive users	✅ Native (v0.9)	Inactive trigger: no open/click in N days
Newsletter A/B tests	✅ Native (v0.9)	A/B split → winner by open/click → send remainder

Coverage as of 2026. Score-segmented flows assume the score arrives as a tag/attribute (as most quiz/test apps already set). A/B testing and inactive-user reactivation triggers are supported natively.

Connect NewsletterMCP →