Same billing model. A third of the price.
Brevo already bills by emails sent, so this is one of the simplest migrations there is — no model change to think about, no per-contact maths to redo. You are moving for price and for what is included on the entry plan.
Unlimited contacts (both), 100,000 sends/month · Typical migration: 2–4 days of work, over 1–2 weeks
Brevo and Bluey share the same send-based billing model, which makes this an unusually clean migration: no recalculating your costs against a different unit, and no surprises when the list grows. Contacts, attributes and the suppression list export as CSV. Automations are rebuilt, as always. At 100,000 sends a month, Brevo Business is $129 against $36 on Bluey Grow. The other reason people move is plan gating — Brevo puts several features behind higher tiers that Bluey includes on Spark, its entry plan.
What transfers, and what you rebuild
Stated up front, because finding out mid-migration is how a two-day job becomes a two-week one.
| What | Status | Detail |
|---|---|---|
| Contacts & attributes | Transfers | Brevo attributes map cleanly to Bluey custom fields. |
| Lists | Transfers | List membership exports and becomes Bluey segments. |
| Blocklist / unsubscribes | Transfers | Export Brevo's blocklist and import it before contacts. |
| Transactional sending | Partial | Swap SMTP credentials or the API endpoint. Templates export as HTML. |
| Automations | Rebuild | Rebuilt in Bluey; the common flows are templated. |
| Email templates | Partial | Export HTML and import. Check rendering after. |
| SMS campaigns | Rebuild | Bluey does not send SMS. If you use Brevo SMS, you will need a separate provider. |
| Forms & landing pages | Rebuild | Rebuild in Bluey and update the embed on your site. |
The migration plan, in order
- 1Day 1 — before any sendAuthenticate your sending domainPublish SPF, DKIM and, if you use one, DMARC records for the domain you will send from. Gmail and Yahoo have required authentication and one-click unsubscribe from bulk senders since February 2024, and an unauthenticated first send from a new platform is the fastest route to the spam folder. This is a DNS change and takes about fifteen minutes; allow up to a few hours for propagation.
- 2Day 1Export contacts, attributes and the blocklistBrevo's blocklist is your suppression list. Export it separately and import it into Bluey before contacts, so opted-out addresses are suppressed on arrival.
- 3Day 1–2Move transactional sending earlyIf you use Brevo for transactional email, swap the SMTP host and credentials or repoint the API call. This is usually the quickest win in the whole migration — the interfaces are close and Bluey's transactional tier starts at $4 a month for 15,000 emails.
- 4Day 2Rebuild automationsBrevo's automation builder maps reasonably onto Bluey's, so this is mostly transcription rather than redesign. Prioritise the flows that are actually sending.
- 5Week 1–2Run Bluey and Brevo in parallelSplit the audience rather than duplicating it: send to one segment from Bluey and leave the rest on Brevo. You get a like-for-like comparison of delivery, engagement and cost on your own data, and nobody receives the same campaign twice. Do not run both against the same contacts — that is the one way to make a careful migration look sloppy to your readers.
- 6Week 2 — graduallyRamp volume rather than switching itStart with your most engaged segment — people who opened or clicked in the last 30 days — and increase volume over several days. Receiving servers judge a new sending pattern partly on engagement, so leading with your best contacts builds reputation, while leading with your whole list including two-year-dormant addresses damages it. If you were on a dedicated IP, treat the new one as cold and warm it deliberately.
- 7Week 3Sort out SMS if you use itThis is the one genuine gap. Bluey does not send SMS, so if Brevo SMS is part of your programme you will need a separate provider for that channel, connected through Zapier or the API. Decide this before you cancel rather than after.
Mistakes people make leaving Brevo
Each of these is recoverable, and each is much cheaper to avoid than to fix.
Migration FAQ
Is migrating from Brevo easier than from other platforms?
Generally yes, because Brevo already bills by emails sent. There is no billing model to re-learn and no recalculating your costs against a different unit. The work is the same export, import and flow rebuild as any migration, without the mental adjustment.
How much cheaper is Bluey than Brevo?
At 100,000 sends a month, $36 on Bluey Grow against $129 on Brevo Business. The other difference is plan gating: Brevo reserves several features for higher tiers that Bluey includes on Spark, its entry plan.
Can I move my transactional email too?
Yes, and it is the easiest part. Bluey exposes SMTP and REST, so it is usually a host, a username and a password. Transactional Essentials is $4 a month for 15,000 emails and $14.95 for 100,000, and it is metered separately from your marketing sends.
What about my Brevo SMS campaigns?
Bluey does not send SMS. This is a real gap and the main reason to think twice about this particular migration. You would need a separate SMS provider, connected through Zapier or the API, which means an extra bill and an extra system.
Will my automations transfer?
No — they are rebuilt, as on every platform move. The good news is Brevo's automation model is close enough to Bluey's that it is mostly transcription rather than redesign.
Keep exploring
Run both in parallel. Then decide.
Seven days of full access, no credit card. Import a segment, send from Bluey while Brevo handles the rest, and compare delivery and cost on your own data before you move the domain.