Move your transactional sending in stages, run both providers in parallel, and keep Brevo for campaigns if you still want it there.
A staged move for transactional mail, with a plain note on what stays behind in Brevo
List your domains, keys, templates, webhooks and suppressions.
Add MigoSMTP DNS records alongside the old ones.
Recreate templates and webhooks, import suppressions.
Shift traffic in stages and watch delivery.
Remove old records and keys once stable.
Terminology reflects the provider's documentation at the time of writing. Verify against current docs before publishing.
curl -X POST https://api.brevo.com/v3/smtp/email \
-H "api-key: BREVO_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "sender": { "name": "Your App", "email": "hello@yourdomain.com" },
"to": [{ "email": "user@example.com" }],
"subject": "Hello",
"htmlContent": "<p>Hi there</p>" }'curl https://api.migosmtp.com/v1/send \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "hello@yourdomain.com",
"to": "user@example.com",
"subject": "Hello",
"html": "<p>Hi there</p>"
}'Illustrative requests. See the API reference for the complete field list.
To move transactional email from Brevo to MigoSMTP, list the senders and domains, API keys, SMTP keys, templates and webhooks you use, then authenticate your domains with MigoSMTP while Brevo's DNS records stay in place. Create scoped keys, recreate templates, point webhooks at your handler, import suppressions, and move one stream at a time. Brevo was known as Sendinblue until 2023, so older integrations and documentation may still use that name.
Brevo is a marketing platform that also sends transactional mail. Its pricing page says all plans give access to transactional email features, including the API and SMTP. That is convenient if one team runs both, but it means a move has two parts. Transactional sending, such as receipts, password resets and alerts, moves to MigoSMTP. Campaigns, contact lists and automations stay in Brevo unless you decide to replace them separately, and this page does not cover that.
On price, Brevo's public page lists plan names (Free, Starter, Standard, Professional and Enterprise) and says the Free plan sends up to 300 emails a day after account approval, but it did not show monthly prices when we read it on 15 October 2026. We are not going to guess them. Open Brevo's live pricing page, find the plan that covers your monthly volume, and compare it with MigoSMTP's $10 for 10,000 and $75 for 100,000. Brevo's Enterprise plan lists a dedicated IP; check what your current plan includes.
List which messages are one-to-one and triggered by a user action. Those move. Newsletters and campaigns can stay in Brevo for now.
If an application sends over SMTP, create MigoSMTP credentials and change the host, port, username and password in staging. If it uses the API, update the endpoint and the key.
Brevo's API takes a sender object, a list of recipient objects, a subject and htmlContent. The MigoSMTP call has the same ideas under simpler field names, so changes are mostly renames.
Templates that use a Brevo template ID need to be rebuilt in MigoSMTP with the same variables. Test each one with real sample data before it goes live.
Map the delivery, bounce and complaint events your code actually reads, update the endpoint, and check signatures in the new payload.
Export blocked, hard-bounced and unsubscribed addresses from Brevo and import them before your first send.
Use the free SPF, DKIM and DMARC checker to confirm that your domain authorises Brevo and MigoSMTP at the same time before you move any traffic.
If you move to a dedicated IP, the IP warmup calculator gives you a day-by-day volume ramp so reputation builds steadily.
While both providers run, the bounce code lookup turns raw SMTP responses into plain explanations and a suggested fix.
Send our team your list of streams and rough volumes and ask for a review of the order in which to move them. This is offered on request.
The checker, calculator and lookup are free tools on this site. The cutover review is a conversation with our team, and you decide every change in your own account.
Write down each application, plugin and internal tool that sends through Brevo. Forgotten integrations, such as a CMS plugin, are the usual surprise.
Publish SPF and DKIM for MigoSMTP while keeping Brevo's records, so both can send for your domain during the overlap.
Begin with mail people expect and open, such as order confirmations. Strong early engagement helps a new sending source build trust.
A rising complaint rate at one mailbox provider is the earliest warning. Check it every day during the move.
Choose a quiet week so you have time to fix anything you find.
Remove Brevo keys first, wait a week, then remove old DNS records. Keep a note of what you removed and when.
Moving from Brevo? Our team can review your senders and templates before you start.
Inventory senders, domains, API and SMTP keys, templates and webhooks. Authenticate your domains with MigoSMTP alongside Brevo, create scoped keys, recreate templates, update webhooks, import suppressions, and move one stream at a time. Retire Brevo keys once the new setup has run cleanly for a few weeks.
Yes. Sendinblue renamed itself Brevo in 2023. If your code or settings still say Sendinblue, they point to the same service.
Moving transactional sending does not touch them. Contacts, campaigns and automations stay in Brevo until you decide otherwise.
We cannot say for your volume without seeing Brevo's live prices, which its public page did not show when we checked on 15 October 2026. MigoSMTP lists $10 for 10,000 emails and $75 for 100,000. Compare both at your own volume.
If most of your value comes from its campaign and automation tools, and your transactional volume is small, staying is reasonable. A move makes more sense when transactional email is the main workload and you want a sending-first service.
If you move to a dedicated IP, yes. A new IP has no history, so raise volume in steps. The warmup calculator gives a schedule.
Yes. Use the SMTP relay on port 587 with STARTTLS or port 465 with implicit TLS, or the REST API.
From Brevo's public pricing page, read on 15 October 2026. Check the live page before you decide, because providers change plans.
Tell us about your domains, volume and setup and we will help you plan a safe, staged cutover.
Create an account, add your domain and send your first email.