Email & SMS (EU)
How to switch from Brevo (Sendinblue)
The EU-to-EU move: contacts and blocklist over in an afternoon, transactional and marketing mail split cleanly, and SMS that finally shares a profile with email.
About a day hands-on over 2–3 weeks of parallel running
| Brevo | WeZend |
|---|---|
| Contacts | Contacts |
| Contact attributes | Custom fields |
| Lists & folders | Lists (+ tags) |
| Blocklist (unsubscribed) | Suppression list |
| Automations | Journeys |
| Email campaigns | Campaigns + A/B & holdout |
| Transactional (SMTP / API) | POST /v1/messages/send (transactional) |
| SMS campaigns | SMS on the same profile |
| Signup forms | Lead forms |
Why this one is the easy move
Brevo and WeZend share the same instincts — EU roots, email + SMS in one product, sane pricing — so the concepts map almost one-to-one and nothing needs re-architecting. What you gain is the layer above: a real CDP (events, live segments, traits), journeys across six channels, and deliverability tooling with an actual inspector.
Step 1 — Blocklist first
Export Brevo's blocklisted/unsubscribed contacts (filter your contact export on blocklist status, or export the unsubscribed segment) and import into Audience → Suppressions before anything else. One import, permanent safety.
Step 2 — Contacts, attributes, lists
Export contacts to CSV from Brevo's contact overview — attributes and list memberships come along. Import per list in Audience → Contacts → Import; attributes map to custom fields in the mapping screen. Folder structure flattens to tags — tag on import (brevo-folder-x) if you want the grouping preserved.
Step 3 — Split transactional and marketing cleanly
If you send transactional mail through Brevo's SMTP or API, follow the SendGrid-style playbook: authenticate your domain in parallel (don't touch Brevo's DNS records yet), port templates, then cut over stream by stream with "category": "transactional" on every send. Marketing traffic follows the classic path: warm up on engaged contacts over 2–3 weeks.
Step 4 — SMS comes home
Register your sender IDs (start early — some countries need operator registration), and enjoy the actual upgrade: in WeZend, SMS and email live on the same contact profile, so "email first, SMS to non-openers after 2 days" is a standard journey branch instead of two disconnected lists — and frequency caps count across both channels.
Step 5 — Automations, forms, cutover
Rebuild automations as journeys (trigger → delay → branch → send maps directly; test-enroll each), swap signup forms for lead forms with double opt-in, run parallel for 2–3 weeks, delta-export late unsubscribes, close.
What does NOT come along
- Campaign statistics — export the reports you want to keep.
- Automation history — journeys count from zero.
- Brevo's Meetings/Conversations modules — out of scope; two-way messaging replies land in WeZend's Inbox, and meeting scheduling stays in your calendar tool.
Go-live checklist
- Blocklist exported and imported as suppressions FIRST
- Contacts imported per list; attributes mapped; folders preserved as tags
- Domain authenticated in parallel; Brevo DNS untouched until after cutover
- Transactional streams cut over one at a time with category set
- SMS sender IDs registered per destination country
- Automations rebuilt as journeys and test-enrolled
- Forms switched; parallel period done; delta export imported
Frequently asked about switching from Brevo
We chose Brevo for EU data residency. Does that change?
No — WeZend is EU-based with EU data residency, a DPA and a public sub-processor list, and GDPR tooling (export, anonymisation, retention) built into the product rather than bolted on. The residency argument that brought you to Brevo carries over intact.
Brevo's free tier carried us long — what's the entry cost here?
Start on pay-as-you-go: no subscription, no included quota, every message billed from a prepaid balance at rates you can read via the API before sending. Storing contacts is free, so importing your audience costs nothing while you evaluate.
Start free in minutes
- No credit card
- EU data residency
- 6 channels, one API
- GDPR built in
One platform. Every customer interaction.
Replace your patchwork of messaging APIs, CDP and automation tools with a single engagement platform built for scale.
No credit card required · EU data residency · 99.99% uptime SLA