Assessment summary. Assessment type: Research-desk assessment (vendor help docs fetched 2026-10-11, third-party migration guides, Mar–Oct 2026 third-party pricing checks) — not a hands-on test cycle. We did not run a live migration; every procedure below is sourced from vendor help documentation and third-party migration guides, with sources and hedges stated inline. Brevo and ActiveCampaign pricing pages are the final authority. Last updated: October 2026.
We may earn a commission if you buy through our links — it doesn’t change our verdicts.
Quick Answer: Migrating from ActiveCampaign to Brevo is a rebuild, not a transfer. Contacts move (via Brevo’s official integration or CSV export/import), but automations, templates, scoring rules, and engagement history do not. The migration economics: Brevo bills your sends, ActiveCampaign bills your list — so Brevo wins for large lists with low send frequency, while small lists with automation needs can cost more on Brevo than on ActiveCampaign Starter. Run a 2–4 week parallel warm-up, keep ActiveCampaign alive until Brevo sending is stable, and never email a contact whose opt-out existed only in the system you turned off.
The ActiveCampaign-to-Brevo migration is one of the most tempting moves an agency can pitch a client: our ActiveCampaign alternatives comparison named Brevo as the cost leader, and the billing-model difference is genuinely structural. But the migration itself has sharp edges, and most of the advice floating around underweights two of them: nothing about the automation layer transfers, and Brevo’s entry-tier pricing has contact limits that didn’t exist until roughly October 2025 — the $9/mo headline doesn’t fit a 1,000-contact list. This checklist covers every step in order, the cost math at realistic volumes, and the failure modes to plan around. It is compiled from Brevo’s and ActiveCampaign’s own help documentation (fetched 2026-10-11) and third-party migration guides — read it as a research-desk briefing, not a vendor promise.
Brevo bills your sends; ActiveCampaign bills your list. Automations don’t migrate — they get rebuilt. Budget for both facts and the move is fine.
What you gain The billing-model flip: Brevo charges for sends, ActiveCampaign charges for list size — for large lists with low send frequency, the math favors Brevo structurally.
What you lose. Every automation, template, scoring rule, and webhook gets rebuilt by hand — nothing transfers. Engagement history stays behind. And Brevo’s shared sending pool has a deliverability ceiling (EmailTooltester 2026 measured 79.8% inbox placement) — plus entry-tier contact caps that the $9/mo headline doesn’t show.
Why the Move Looks Attractive — and What It’s Really Built On
ActiveCampaign bills contact-based: your list size sets the invoice. Starter is $19/mo at 1,000 contacts (monthly-billed; $15/mo annual), rising to $189/mo at 10,000 contacts, with Starter reportedly capping out above 10–25k contacts (per our #7 pricing brief). Brevo bills email-volume-based: Starter starts at $9/mo for 5,000 emails/month, $17/mo at 10,000, with contact storage that scales separately.
The honest frame: Brevo wins when (large list) × (low send frequency) — the classic newsletter/retention program. ActiveCampaign can win at small lists with automation needs. Two reasons, and both are gotchas we’ll price below:
1. Brevo’s entry-tier contact caps (new since ~Oct 2025): the $9/5,000-email tier caps at 500 contacts — a 1,000-contact list physically cannot sit on it. Size Brevo by max(contacts, emails). 2. Automation requires Brevo Standard ($18/mo+): Starter has no automation, no A/B testing, no landing pages. Anyone rebuilding ActiveCampaign automations starts at Standard, not Starter — which can erase the headline savings for automation-heavy small shops.
The Cost Scenarios: 1K, 10K, 50K Contacts
Scenario math below uses illustrative send-frequency assumptions — stated explicitly, never presented as measured data. Brevo figures are monthly-billed; ActiveCampaign figures come from our ActiveCampaign review pricing ladder (monthly-billed):
| Scenario | ActiveCampaign | Brevo (equivalent) |
|---|---|---|
| 1,000 contacts, light sending (~4k emails/mo, no automation) | Starter $19/mo | Starter 10k-email tier $17/mo (the $9/5k tier is contact-capped at 500) |
| 1,000 contacts, with automation | Starter $19/mo (ActiveCampaign Starter workflows reportedly capped at 5 actions/automation — fahimai.com, single source, verify) | Standard 10k-email tier ~$35/mo (Mar-2026 third-party figure; automation forces Standard) |
| 10,000 contacts, 4 campaigns/mo (~40k emails/mo) | Starter $189/mo | Starter 40k-email tier $39–46/mo (disputed between Mar and Jun 2026 sources); Standard ~$75/mo |
| 50,000 contacts, 1 campaign/mo (~50k emails/mo) | Plus $759/mo (Starter caps out) | Starter 50k-email tier $56/mo (Oct 2026 third-party check) |
| 50,000 contacts, 4 campaigns/mo (~200k emails/mo) | Plus $759/mo | Professional territory ($499/mo from 150k emails; band pricing above 100k is thinly sourced) |
Prices last verified: October 11, 2026 (vendor docs) — per-source pricing from Mar–Oct 2026 third-party checks; disputed bands shown as ranges. Vendor pages are the final authority.
The reversal, non-obvious: at 1,000 contacts with automation, Brevo (~$35/mo Standard) can cost more than ActiveCampaign Starter ($19/mo) — Brevo’s entry-tier contact caps and the Standard automation gate erase the headline gap. Never assume the switch saves money: model both directions. Billing-model shock works both ways — ActiveCampaign bills list growth, Brevo bills send frequency. A high-frequency sender can find Brevo the expensive side.
Related hedges: Brevo’s volume-band prices disagree across sources on the 20k/40k/100k bands (shown as ranges above); the logo-removal add-on is $12/mo per one verified source, $9/mo per another — verify live; multi-user access at $12/user/mo is single-source, verify.
Phase 0 — Audit (1–3 Days)
Before touching anything, inventory the ActiveCampaign estate. Migration failures start here — skipping the audit means discovering webhooks mid-cutover.
– Every list, tag, and custom field. Export a list of all custom fields with their types; they’ll need to exist on the Brevo side before mapping. – Every automation. Document per workflow: entry criteria, re-entry rules, goals/completion conditions, wait durations and timezone assumptions, every branch, scoring thresholds, webhook steps, each message’s personalization tokens, fallbacks, links, and unsubscribe handling. Screenshot the automation logic — you will rebuild these by hand in Brevo. – In-flight contacts. Record, for every live automation, which contacts are mid-flow, what they’ve completed, and their intended next action. In-flight contacts must NOT be restarted at step one — resume them through a tested path (konabayev.com migration checklist, Oct 2026). – Every form and embed. Each old ActiveCampaign form still posting to the old account silently splits the audience (konabayev.com). Every form is a cutover line item. – Every integration, webhook, and API consumer. Everything that posts to ActiveCampaign’s API or receives its automation webhooks gets its endpoint and credentials repointed at Brevo’s v3 API — treat this as an inventory line item, not a quick edit. Note: ActiveCampaign’s webhook automation action is unavailable on Starter — Starter migrants likely have fewer webhooks to port; Plus/Pro migrants must inventory them all. – The suppression list. Export unsubscribed, bounced, and unconfirmed contacts separately. Suppressions must survive the move — this is a legal/compliance item, not housekeeping. – Template HTML and scoring rules. Export template HTML from ActiveCampaign; document every scoring rule — lead and contact scores export as current values; the scoring rules must be rebuilt (smbcrm.com).
Phase 1 — Contacts: Export (Hours)
Two paths, different coverage. Pick based on what needs to move.
### Path A — Brevo’s official ActiveCampaign integration (the simple path)
Brevo ships an official ActiveCampaign contacts integration (help.brevo.com, article 360006115039, fetched 2026-10-11). It’s free: connect with your ActiveCampaign account URL + API key, and contacts sync in real time — existing and new, with updates and blocklists syncing both ways. Mandatory checkbox: confirm the contacts gave explicit consent to receive communications. Consent proof is a vendor gate, not optional.
Two limits, both verbatim from Brevo’s help doc:
– Only ONE ActiveCampaign list per integration. Agencies with multiple client lists create multiple integrations. – “Custom fields won’t be imported” via this integration. Standard fields (email/SMS, names, phone) map; custom attributes do not. If custom fields matter, use Path B.
Brevo’s marketing page claims “migrate up to 130,000 contacts at no charge with dedicated migration tools” (brevo.com) — treat this as their marketing claim, not a verified process; what “dedicated migration tools” covers is not published.
### Path B — CSV export → CSV import (the complete-data path)
Export from ActiveCampaign (help.activecampaign.com): Contacts > Exports. The CSV includes selected custom fields, lead scores, deal scores, and tags in a single column. List export adds list name, email, first/last name, phone, status, date created, IP address, and user agent. Watch the status trap: single-contact export leaves the Status column blank — status must come from list exports. The download link is valid 7 days; the export runs in the background (safe to navigate away or log out).
Import into Brevo (help.brevo.com): Contacts > Import, accepts CSV/XLS/XLSX or copy-paste. At least one of EMAIL, SMS, WHATSAPP, LANDLINE_NUMBER, or EXT_ID is required. The header row should match Brevo attribute names, but custom attributes can be created during mapping — no need to pre-create them. Duplicates dedupe by email (skip / merge / overwrite).
The suppression rule: export each list by status separately (Active / Unsubscribed / Bounced / Unconfirmed) — smbcrm.com migration guide. Brevo’s subscribe state is a global per-contact blocklist flag, not a per-list flag (third-party-reported; verify). Importing everyone into one list and flagging unsubscribed contacts as blocklisted preserves suppression.
Phase 2 — The Brevo Build (1–2 Days)
### Lists, attributes, segments
Map ActiveCampaign lists → Brevo lists one-to-one. For tags: we could not confirm a native contact-tag feature in Brevo from vendor docs, so the recommended approach (practice, not vendor-prescribed — verify Brevo’s segments UI yourself) is ActiveCampaign tags → Brevo segments (conditions on attributes or list membership) or a custom attribute holding the tag string for later segmentation. Brevo segments support up to 100 conditions (omnisend.com, Oct 2026).
### Domain authentication
From help.brevo.com (article 12163873383186, fetched 2026-10-11): account dropdown → Senders, Domains & Dedicated IPs → Domains → Add a domain. Brevo issues three records:
– Brevo code (TXT verification) – DKIM (CNAME type, 2048-bit by default; TXT type is 1024-bit; 2048-bit TXT via support, key prefix `sib2k`) – DMARC with a rua tag required (e.g. `v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com`, or your own rua)
Two things to know: Brevo’s official position is that SPF and MX records are NOT required to authenticate a domain — SPF/MX are only issued for dedicated-IP setups. Third-party deliverability guides still recommend adding `include:spf.brevo.com`. Present both honestly: official minimum vs. deliverability best practice. And never run two SPF records — merge with the existing one; two SPF records fail outright. The domain shows “Authenticated” after verification; Brevo allows retrying within 48 hours.
### Templates
No template transfer mechanism exists. Rebuild path (help.brevo.com, verified): Brevo template editor → “HTML custom code” option → paste your HTML → Actions > Save as template. Template share links only work Brevo-to-Brevo. And personalization syntax differs: Brevo uses `{{ contact.FIRSTNAME }}` style variables while ActiveCampaign’s field syntax is different — every personalization token must be rewritten. Verify both syntaxes yourself before bulk rebuild.
### Automations — the rebuild
Automations do not transfer — period. ActiveCampaign’s share links are snapshots for ActiveCampaign-to-ActiveCampaign only; there is no cross-platform import compatibility (smbcrm.com; HubSpot community migration thread). Every workflow gets rebuilt in Brevo’s automation builder from your Phase 0 documentation. This is the largest labor block of the migration — budget for it, and note the pricing consequence: rebuilding automations means Brevo Standard minimum ($18/mo+), since Starter ships no automation at all.
Historical engagement data (opens/clicks) does not transfer either; expect a few weeks to rebuild behavioral segments (techno-pulse.com, Mar 2026). Contact notes are excluded from ActiveCampaign exports; deal exports need export permission and exclude deal notes.
Phase 3 — Import + Verify (1 Day)
– Run a small-batch test import first; check field mapping before bulk (“if matching is wrong, stop and correct” — smbcrm.com). – Import unsubscribed contacts as blocklisted — suppression first, sending second. – Regenerate keys on the Brevo side: SMTP & API → API keys → Generate a new API key (Brevo UI per third-party setup doc, Oct 2026). Then repoint every external system from ActiveCampaign’s endpoints to Brevo’s v3 API — the Phase 0 inventory becomes the execution list. – Keep the suppression data in both systems during the entire overlap.
Phase 4 — Warm-Up + Parallel Run (2–4 Weeks)
The new sending IP starts cold even though the domain has history — open rates typically dip for two to three weeks while the new setup re-earns trust (adapty.io, Aug 2026). Throttle to warmup pace: sending at old volume anyway can burn the domain’s reputation. Warmup = weeks, not days.
Structural caveat worth knowing before cutover: EmailTooltester’s 2026 testing put Brevo at 79.8% average inbox placement (one round at 72%, a Hotmail/Outlook issue) — behind Postmark (93.8%) and SMTP2GO (95.5%) on the same methodology (smtp2go.com, Sep 2026). Brevo runs marketing and transactional mail through shared reputation; if deliverability is non-negotiable, keep a separate sender domain/subdomain for transactional mail. Run both systems in parallel during this window — do NOT cancel ActiveCampaign yet.
Phase 5 — Cutover
– Swap forms, API keys, and webhook endpoints. – Update DNS per the Phase 2 authentication. – Monitor placement via Google Postmaster Tools / Microsoft SNDS. – Never keep ActiveCampaign’s authentication pointed at the same sending streams after cutover without a plan — allow both senders during overlap (staged migration pattern per hostmycode.com, Oct 2026).
### Rollback
Keep the ActiveCampaign account active until Brevo-side sending is verified stable — at minimum through the warm-up window. If placement collapses: revert forms and API to ActiveCampaign, pause Brevo sends, diagnose before retrying. And the rule that outlives the whole project: suppression data must exist in both systems during the entire overlap — never email a contact whose opt-out lived only in the system you just turned off.
The Migration Verdict
The ActiveCampaign-to-Brevo move is real economics, not hype — but the economics have two traps and the migration has one giant labor line. The traps: entry-tier contact caps (size by contacts, not just emails) and the Standard automation gate (no automation on Starter). The labor: every automation, template, scoring rule, and webhook gets rebuilt by hand — nothing transfers. Do the audit first, run the 2–4 week parallel warm-up, keep suppressions in both systems, and the move pays for itself. Skip any of that, and the “savings” arrive as a deliverability problem.
We may earn a commission if you buy through our links — it doesn’t change our verdicts.
*Pricing checked: October 11, 2026.*
Byline: Agency Tested Research Desk

Dr. Abdullah
Dr. Abdullah is the founder of Agency Tested, a research publication that scores B2B SaaS tools for marketing agencies. Every product is assessed against vendor documentation, live pricing pages, and verified user reports — never faked hands-on tests. Every score on this site carries his name and his rulebook.
FAQ
Can you migrate automations from ActiveCampaign to Brevo?
No — automations do not transfer between platforms, period. ActiveCampaign’s share links work AC-to-AC only. Every workflow must be rebuilt in Brevo’s automation builder from documentation: entry criteria, branches, wait durations, scoring thresholds, and webhook steps. Budget for this — it is the largest labor block of the migration, and rebuilding automations requires Brevo Standard ($18/mo+) since Starter has no automation.
How do I export contacts from ActiveCampaign for migration?
Contacts > Exports in ActiveCampaign. The CSV includes custom fields, lead scores, deal scores, and tags in a single column; list export adds status, date created, IP address, and user agent. Important: single-contact export leaves the Status column blank — use list exports for status. Download links are valid 7 days and the export runs in the background.
What is the cheapest way to move 1,000 contacts from ActiveCampaign to Brevo?
It depends on automation. Light sending with no automation: Brevo’s 10k-email Starter tier at ~$17/mo — the $9/5,000-email tier is contact-capped at 500 (new since ~Oct 2025), so it cannot hold a 1,000-contact list. With automation: Brevo Standard at ~$35/mo for the 10k-email band, which is actually more than ActiveCampaign Starter’s $19/mo. Model both before promising savings.
How long does an ActiveCampaign to Brevo migration take?
Realistically 3–6 weeks for an agency account: 1–3 days auditing, hours exporting, 1–2 days building in Brevo, 1 day importing and verifying, then a 2–4 week warm-up/parallel run before cutover. The warm-up is the long pole — a cold sending IP needs weeks to earn back inbox trust. Do not cancel ActiveCampaign until Brevo-side sending is verified stable.
Will my deliverability drop after migrating to Brevo?
Expect a dip — the new sending IP starts cold even though the domain has history; open rates typically dip for two to three weeks while the new setup re-earns trust (adapty.io, Aug 2026). Throttle to warmup pace. Separately, know Brevo’s shared-pool ceiling: EmailTooltester 2026 put Brevo at 79.8% inbox placement vs 93.8–95.5% for Postmark/SMTP2GO on the same methodology — keep transactional mail on a separate sender domain if deliverability is non-negotiable.
Do unsubscribes transfer from ActiveCampaign to Brevo?
They transfer only if you make them transfer. Export each list by status separately (Active / Unsubscribed / Bounced / Unconfirmed) and import unsubscribed contacts as blocklisted in Brevo — Brevo’s subscribe state is a global per-contact blocklist flag, not a per-list flag. Suppression data must exist in both systems during the entire overlap: never email a contact whose opt-out lived only in the system you turned off.