Two approaches to choose from: keep Brevo as your sending engine and run your campaigns from MarketingAtelier, or migrate fully to native sending. Here is how to do it, what syncs, and how to choose.
Updated on June 22, 2026
Already using Brevo (formerly Sendinblue) for your sends and just discovering MarketingAtelier? Good news: you don't have to migrate everything overnight. Two approaches coexist. You can connect your Brevo account and keep sending through Brevo while building and running your campaigns from MarketingAtelier, or migrate fully to native sending. This guide covers both, what syncs, and how to choose.
This is the "zero disruption" option. You keep your Brevo account, your sender domain, your sending reputation and all your history. MarketingAtelier becomes the workshop where you design your emails and orchestrate your campaigns; Brevo stays the sending engine. Concretely, through SendAtelier and its ESP connector pattern:
You get the email builder, the design system and the platform's AI, without touching your sending infrastructure. Ideal if your Brevo domain is well warmed up and you don't want any deliverability risk.
If you want everything under a single platform, you can migrate fully. MarketingAtelier's native sending runs on a modern transactional infrastructure: you import your contacts via CSV, you verify your sending domain through DNS, and you send directly from MarketingAtelier with no external dependency. Your personalization tokens are then resolved on the platform side, one HTML per recipient.
This approach simplifies billing (a single subscription) and keeps your data — contacts, consents, statistics — in one place. It's the natural choice if Brevo only serves to send and you want to move away from it.
Connecting takes just a few minutes from SendAtelier:
Gotcha to know. With Brevo, the send test fails if the test address does not exist in your Brevo contacts. Add that address as a contact in Brevo first, then run the test again from MarketingAtelier. Once that detail is handled, everything goes through.
Beyond sending, the CRM can synchronize and import your contacts from your ESP, mapping the statuses to the right consent. Here is what flows between Brevo and MarketingAtelier depending on the approach you choose:
| Item | Connect Brevo | Migrate (native sending) |
|---|---|---|
| Campaign HTML | Pushed to Brevo | Rendered and sent natively |
| Send trigger | On Brevo's side | On MarketingAtelier's side |
| Personalization | Translated to Brevo syntax | Resolved on the platform |
| Statistics | Pulled via synchronization | Native in the platform |
| Contacts | Sync / import from the ESP | CSV import with consent |
| Consent | ESP status mapping | Opt-in proof at import |
You don't have to decide right away: many teams connect Brevo first, find their footing, then migrate once confident. To dig deeper into positioning, read our MarketingAtelier vs Brevo comparison.
Design your emails in MailAtelier, connect Brevo via SendAtelier or enable native sending, and keep your contacts up to date in the CRM. Compare the plans or create a free account to test the connection in a few minutes.
MarketingAtelier brings email, CRM, sites, forms, social and AI visual creation into a single platform. Try it for free.