Migrate from Brevo to Brew

​

Concepts

​

1. Export Contacts, Consent, and Suppression

​

2. Map Your CSV

• Don’t import a status column as it is. Brew reads opt-outs only from a Subscribed column, so any other column becomes a plain custom property and those people import as subscribed.
• Brevo attributes are UPPERCASE by convention, such as FIRSTNAME and LASTNAME. Brew properties use camelCase, such as firstName. Rename columns to match during mapping.
• Save as UTF-8. Garbled characters at the mapping step usually mean it wasn’t.
• Dates: day-first dates such as 03/04/2026 (3 April) import correctly when you pick day first at the mapping step, and YYYY-MM-DD needs no choice. See date formats.

​

3. Import into Brew

​

Bring Your Consent Records

• Export the evidence. Include any opt-in date, double opt-in confirmation, or signup source your Brevo export carries. Keep those columns as custom properties.
• In the app, tick the consent checkbox at the review step. Brew records consent once for the whole file, dated the day you import.
• To keep each person’s original opt-in date, import over the API instead, with a consent record per contact. See Add Contacts for the consent fields.

{
  "contacts": [
    {
      "email": "jane@example.com",
      "consent": { "source": "import", "capturedAt": "2024-03-02T10:15:00Z", "evidence": "Brevo double opt-in form" }
    }
  ]
}

​

4. Rebuild Segmentation

​

5. Rebuild Templates and Merge Tags

​

Translate Merge Tags

{{ contact.FIRSTNAME }}   →   {{ firstName | there }}
{{ params.orderId }}      →   {{ trigger.orderId }}

​

6. Rebuild Automations

​

7. Swap the API Calls in Your Code

import { BrevoClient } from "@getbrevo/brevo";

const brevo = new BrevoClient({ apiKey: process.env.BREVO_API_KEY });

await brevo.contacts.createContact({
  email: "user@example.com",
  attributes: { FIRSTNAME: "Ada", LASTNAME: "Lovelace" },
  listIds: [Number(process.env.BREVO_LIST_ID)],
  updateEnabled: true,
});

await fetch('https://brew.new/api/v1/contacts', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.BREW_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    email: "user@example.com",
    firstName: "Ada",
    lastName: "Lovelace",
  }),
});

await fetch('https://api.brevo.com/v3/events', {
  method: 'POST',
  headers: {
    'api-key': process.env.BREVO_API_KEY,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    event_name: "trial_started",
    identifiers: { email_id: "user@example.com" },
    event_properties: { plan: "pro" },
  }),
});

await fetch(
  `https://brew.new/api/v1/automations/triggers/${process.env.BREW_TRIAL_STARTED_TRIGGER_ID}/fire`,
  {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${process.env.BREW_API_KEY}`,
      'Content-Type': 'application/json',
      'Idempotency-Key': `trial-started-${subscription.id}`,
    },
    body: JSON.stringify({
      payload: { email: "user@example.com", plan: "pro" },
    }),
  },
);

​

8. Cut Over

1. Rebuild while Brevo keeps sending. Import contacts and rebuild segments, templates, and automations. None of it touches live sending. Keep every Brew automation unpublished.
2. Check your segments. Confirm each recreated Audience’s membership count against the original. See Step 4.
3. Refresh opt-outs. Right before your first Brew send, export Brevo’s new unsubscribes and bounces and import them into Brew as Subscribed: false. That stops marketing only. Transactional sends still reach these contacts, so don’t fire transactional triggers for addresses that hard-bounced or complained. Repeat before each type you move, until Brevo stops sending. Anyone who opted out during the rebuild stays opted out.
4. Warm up with the first type you move. Pause that type on Brevo first, so nobody gets it from both. Send to your most engaged contacts first and ramp over several days. Gradual send does the ramping for you. No history means no reputation, even on a verified domain.
5. Move one type at a time. One-off emails first, then automations. For each automation, in order: pause it on Brevo, publish the Brew version, then point its signup forms or tracked events at Brew. Watch each in analytics before you move the next.
6. Move transactional email last. Before you move any, add a separate transactional-purpose subdomain (see Transactional Email). A fire for a new address creates a subscribed contact, so only send marketing to people who opted in. Resets and receipts are the highest-stakes sends. Cut them over one at a time, and test-run each automation with a real payload before you point production code at its trigger.
7. Keep Brevo as a fallback. Keep its marketing side active but unused for a couple of weeks, then downgrade to whatever still covers the channels that stay. Keep SMS, WhatsApp, and CRM on Brevo, or move them to a dedicated provider.

​

From an Agent or Code

“Import subscribed.csv, then unsubscribed.csv, as separate batches, and record the consent source as import.”

“Create an audience of subscribed contacts whose plan is pro, and tell me how many it holds.”

“Import this HTML as an editable email called Newsletter.”

• Contacts. POST /v1/contacts/import-csv, or brew-cli contacts import-csv --file contacts.csv, once per file. Add Contacts covers limits and the consent record.
• Segments. POST /v1/audiences with a name and filters, or brew-cli audiences create.
• Templates. POST /v1/emails/import with the format and content. Import is free and uses no AI.

​

Quick Reference

​

Need Help?