Migration guideBrevo to Sendcorex

Migrate from Brevo. Keep your deliverability.

A step-by-step plan for moving off Brevo (formerly Sendinblue) — contacts, DNS records, SMTP or API credentials, and the parallel-sending window that keeps your sender reputation intact.

No credit card required · Migration usually takes 1–2 weeks end to end

Code changes

Minutes

Swap the endpoint, header and field names

DNS propagation

24–48h

SPF, DKIM and DMARC records need time to settle

Full migration

1–2 wks

Includes the parallel-sending warm-up window

Typical timeline for a mid-size sender. Larger lists or dedicated IP warm-up can take longer.

The migration

Six steps, in order

Get started free
  1. 1

    Create your Sendcorex account and API key

    Sign up free and generate an API key from the dashboard. Keep your Brevo account active — you'll run both in parallel for a few weeks, not cut over instantly. Decide what you use Brevo for: transactional email over SMTP or API, campaigns, or both. Export your contact lists and your blocklisted contacts as CSV so unsubscribes and hard bounces move with you.

  2. 2

    Add and verify your sending domain

    Add your domain in Sendcorex, then publish the SPF, DKIM and DMARC records it gives you as new DNS entries. Leave Brevo's verification code and DKIM record in place, and merge Sendcorex's SPF include into your existing SPF record rather than adding a second one.

  3. 3

    Wait for DNS to propagate, then verify

    Give it 24–48 hours. Check verification status in the Sendcorex dashboard before sending anything — sending through unverified DNS is what causes the deliverability problems people blame on migrations. While you wait, run your exported contacts through the Email Validator to catch invalid addresses before they reach a new sender.

  4. 4

    Update your code — endpoint and key only

    Brevo's API uses an api-key header with sender, to: [{ email }] and htmlContent. Swap that for a Bearer token and flat from, to, subject and html fields. If you send over SMTP, change the host from smtp-relay.brevo.com to smtp.sendcorex.com and use your new API key as both username and password. Campaigns built in Brevo's editor need recreating — export the HTML, then rebuild them with Sendcorex's newsletter tools.

  5. 5

    Shift volume gradually, not all at once

    Start with 10–20% of sends routed through Sendcorex, watch delivery and bounce rates in real time, then increase over 1–2 weeks. This lets Sendcorex's IPs warm up against mailbox providers instead of arriving as an unknown sender all at once. If you send campaigns as well, start them with your most engaged contacts.

  6. 6

    Cut over fully, then retire Brevo's DNS records

    Once 100% of volume runs cleanly through Sendcorex for a few days, remove Brevo's verification code and DKIM record and cancel the subscription. Keep your own DMARC policy in place — it protects your domain regardless of provider.

Step 4 in practice

The code change, side by side

Before — Brevo (Sendinblue) REST API
await fetch('https://api.brevo.com/v3/smtp/email', {
  method: 'POST',
  headers: {
    'api-key': 'BREVO_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    sender: { email: 'hello@yourdomain.com' },
    to: [{ email: 'customer@example.com' }],
    subject: 'Welcome!',
    htmlContent: '<h1>You are in.</h1>',
  }),
});
After — Sendcorex (plain REST, no SDK)
send.js
const response = await fetch('https://mail.sendcorex.com/v3.0/send', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    to: 'customer@example.com',
    from: 'hello@yourdomain.com',
    senderName: 'Your Company',
    subject: 'Welcome!',
    body: '<h1>You are in.</h1>',
  }),
});
Before you cut over

Pre-flight checklist

  • SPF is a single record that includes both Sendcorex and Brevo for now

  • DKIM selector for Sendcorex shows as verified in the dashboard

  • Test send delivered to Gmail, Outlook, and Yahoo test inboxes without landing in spam

  • Contacts and blocklisted contacts exported from Brevo, unsubscribes loaded into Sendcorex

  • Webhook or event listener updated to receive delivery and bounce events from Sendcorex

  • Bounce and complaint rate monitored daily during the ramp-up window

Before you switch

Common questions

Steps and timelines reflect typical migrations as of 2026 and may vary based on list size, DNS provider, and existing authentication setup.

Not if you run a parallel sending window instead of an instant cutover. Sender reputation lives on the sending domain and IP, so warming up Sendcorex's IPs for 1–2 weeks while gradually shifting volume avoids a deliverability dip.

Ready to move off Brevo?

Create your account, verify your domain, and start the parallel-sending window today.

Get started free

No credit card required