Migrate From Brevo to Brew

​

Concepts

​

1. Export Contacts From Brevo

​

2. Map Your CSV

• Brevo attributes are UPPERCASE by convention, such as FIRSTNAME and LASTNAME. Brew properties use camelCase, such as firstName. Rename columns to match during mapping
• These names are reserved and can’t be used for custom properties: email, first_name, last_name, subscribed, created_at, updated_at, validation_status, last_validated_at, import_id

{{ contact.FIRSTNAME }}   →   {{ firstName | there }}

• If/else conditional blocks
• For loops that repeat a section of content
• Filters written with a pipe, such as {{ contact.ATTRIBUTE|filter }}
• Object variables, used only in automations triggered by a custom object, which has no Brew equivalent

​

3. Import Into Brew

​

4. Rebuild Segmentation

1. Write the derived signal onto the contact as a custom property, using an automation or the API on whatever cadence fits.
2. Build your Brew Audience on that property, not on the raw event.

​

5. Rebuild Templates

​

6. Rebuild Automations

​

7. Swap the API Calls in Your Code

import { ContactsApi, CreateContact } from "@getbrevo/brevo";

const contactsApi = new ContactsApi();
contactsApi.authentications.apiKey.apiKey = process.env.BREVO_API_KEY;

const contact = new CreateContact();
contact.email = "user@example.com";
contact.attributes = { FIRSTNAME: "Ada", LASTNAME: "Lovelace" };
contact.listIds = [Number(process.env.BREVO_LIST_ID)];
contact.updateEnabled = true;

await contactsApi.createContact(contact);

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. Warm up your Brew sending domain before any real volume. Send to your most engaged contacts first and ramp over several days. Gradual send does the ramping for you.
2. Rebuild contacts, segments, templates, and automations while Brevo keeps sending normally.
3. Move one message type at a time. A reasonable order is one-off emails first, then automations, then transactional.
4. Give single-recipient, account-critical messages extra care, whichever category they’re in. A password reset or a receipt qualifies.
5. Watch each moved type in analytics before you move the next.
6. Confirm recreated segments’ membership counts before their automations go live. See Step 4.
7. Point signup forms and any tracked events at Brew once everything upstream is verified.
8. Keep SMS, WhatsApp, and CRM on Brevo, or move them to a dedicated provider. Brew doesn’t cover these channels.
9. Keep Brevo active but unused for a couple of weeks as a fallback, then downgrade or cancel.

​

Quick Reference

​

Need Help?