Identical to Brevo, because it is Brevo. Contacts sit in named lists with attributes, and the account-wide blocklist spans all of them regardless of which name your login shows.
Getting the addresses out of Sendinblue
Contacts, select the list, then Export contacts. Identical to Brevo.
Before the first campaign, on the same reasoning as Brevo. The rename changed the logo and nothing about how the compliance review works.
What Sendinblue does with the file you bring back
The import rules decide what a re-import actually changes, which is worth knowing before you upload.
The short version
- Imports match on email and update the existing contact.
- Blocklisted addresses stay blocked account-wide.
- Contact attributes import alongside the address.
- The API is the same service under either name, so an old integration continues to work.
The mistake to avoid
Some addresses come back unresolved, and that is a fact about the receiving server rather than a gap in the check. We label those and never bill for them. What that means, and why roughly 28% of business addresses land there, is set out on our page about catch-all domains.
A 2019 account coming back to life
Say you opened a Sendinblue account in 2019, sent a dozen newsletters from a Gmail address, and stopped in 2022. A WordPress plugin kept adding signups the whole time, so 14,000 contacts are waiting. You log in, see the Brevo logo, and schedule a relaunch.
Two things changed while you were away. Your list aged, so suppose a check finds 2,100 invalid and 1,500 on catch-all domains. Sender rules moved as well, and they matter more for an account that used to mail from a free Gmail address than for anyone else. Brevo's help center says domain authentication has been mandatory since February 1, 2024, following Gmail's and Yahoo's requirements. Free mailbox domains can't be authenticated, and when a sender's domain isn't authenticated Brevo replaces it with a brevosend.com address. Your relaunch would reach people from a sender they've never seen, after a three-year silence.
Fix the sender first, then send to the 10,400 confirmed addresses. The 50,000 pack covers the check at $89 and leaves credits that don't expire.
A short inspection for a legacy login
Start at Senders, Domains and Dedicated IPs. You're looking for three records on a domain you own: the Brevo code, a DKIM record and a DMARC record. Brevo's compliance guide asks for a single DMARC record that carries a rua tag, which is the reporting address.
Next, find whatever is still writing to the account. An old plugin or signup form with a saved API key will keep adding contacts, and nobody has looked at its double opt-in setting in years. Open the form, submit a test address, and see what arrives.
Finally, compare the plan you're on with the current plan page. Accounts opened before the rename can carry allowances that no longer match what's published, and a daily sending cap you've forgotten about will stretch a 10,400-contact relaunch across several days. That's not a disaster for a dormant list, since a slow start is kinder to your sender reputation than one large burst.
Questions people ask
Does an import behave differently under the old name?
No. Matching, blocklist persistence and attribute handling are identical, because it is one platform with two names in circulation.
Which documentation should I follow?
Brevo's current pages. Sendinblue-era articles are still indexed and are frequently stale on compliance and review details.
Should I migrate my integration to the new name?
Not urgently, and worth doing when you next touch that code. The endpoints work, and the naming mismatch costs someone an hour of confusion eventually.