Brevo Migration Guide: Move Your Contacts & Campaigns Seamlessly

Switching email marketing platforms can feel overwhelming, but with the right plan you can preserve your data, keep your automation flows, and avoid losing deliverability. This guide walks you through every stage of migrating to Brevo (formerly Sendinblue) – from initial audit to post‑migration testing.

Why Migrate to Brevo?

• All‑in‑one suite: email, SMS, chat, and CRM in one dashboard.
• Competitive pricing: pay‑as‑you‑grow plans suitable for small businesses.
• Advanced automation: visual workflow builder with trigger‑based messaging.
• GDPR‑ready: built‑in consent management and data protection tools.

Migration Checklist

1. Audit current data and assets.
   
   • Contact lists, custom fields, tags.
   • Campaign templates, saved designs.
   • Automation workflows and triggers.
2. Export data from your old ESP.
   
   • CSV for contacts (include subscription status).
   • HTML files for email templates.
   • JSON or XML for automation logic if available.
3. Prepare Brevo account.
   • Create an API key (SMTP & v3 API).
   • Set up sender identities and domain authentication (SPF/DKIM).
   • Configure custom attributes that match your exported fields.
4. Import contacts.
   • Use Brevo’s Import Contacts tool – map CSV columns to attributes.
   • Enable double‑opt‑in for new subscribers to stay compliant.
   • Segment lists during import to preserve original groups.
5. Recreate templates.
   • Paste exported HTML into Brevo’s drag‑and‑drop editor.
   • Replace merge tags (e.g., {{contact.FIRSTNAME}} → [[FIRSTNAME]]).
   • Save as transactional or marketing templates as needed.
6. Build automation workflows.
   • Translate old triggers into Brevo’s Automation nodes.
   • Test each step with a small segment before full rollout.
7. Validate deliverability.
   • Send test emails to multiple inbox providers.
   • Check spam‑score with tools like Mail‑Tester.
8. Finalize and go live.
   • Pause old ESP campaigns.
   • Monitor send logs and bounce rates for the first 48 hours.

Step‑by‑Step Technical Walkthrough

1. Export Contacts from the Legacy ESP

Navigate to Contacts → Export and choose a CSV with the following columns: Email, FirstName, LastName, Status, and any custom fields. Make sure to include the Unsubscribe flag so you don’t re‑import people who have opted out.

2. Set Up Your Brevo Account

Log in, go to SMTP & API → API Keys, and generate a new v3 key. Keep it safe – you’ll need it for bulk imports and for connecting your CRM.

3. Create Custom Attributes

In Contacts → Attributes, click Add Attribute. Match the names exactly (e.g., city, signup_source). This ensures a smooth CSV mapping.

4. Import CSV Using the UI or API

UI method: Choose Import Contacts, upload the file, and drag‑and‑drop column headers to the appropriate Brevo attributes. Enable Update existing contacts to avoid duplicates.

API method (Python example):

import requests, json url = "https://api.brevo.com/v3/contacts/import" headers = {"api-key": "YOUR_API_KEY", "Content-Type": "application/json"} payload = {     "fileUrl": "https://your-bucket.s3.amazonaws.com/contacts.csv",     "listIds": [2],     "notifyUrl": "https://example.com/notify" } response = requests.post(url, headers=headers, data=json.dumps(payload)) print(response.json()) 

5. Migrate Email Templates

Copy the raw HTML from your old platform, paste it into Brevo’s editor, then replace merge tags. Brevo uses double‑square brackets ([[...]]) for personalization. Test each template by sending a preview to yourself.

6. Rebuild Automation

Open Automation → Create. Choose a trigger (e.g., Contact subscribes to a list) and add actions such as Send email, Wait, or Update contact attribute. Replicate the logic from your previous workflows step‑by‑step.

Best Practices for a Smooth Transition

• Start with a pilot: Migrate a small list (5‑10 % of contacts) and run a test campaign.
• Maintain data hygiene: Remove hard bounces and inactive contacts before import.
• Document every mapping: Keep a spreadsheet of old field → new attribute for future reference.
• Monitor engagement metrics: Compare open and click‑through rates after migration to spot deliverability issues.
• Set up SPF/DKIM early: Helps keep your inbox placement high from day one.

FAQ

Can I migrate contacts directly from another ESP without exporting a CSV?

Yes – many platforms offer a native Brevo integration or allow API‑to‑API transfer. However, a CSV export is the most reliable fallback.

What happens to my unsubscribe list?

Export the unsubscribed contacts and import them into Brevo with the status set to unsubscribed. This prevents accidental re‑mailing.

Do I need to recreate all my segments?

Segments based on static lists can be rebuilt using imported list IDs. Dynamic segments will need to be re‑created using Brevo’s filter rules.

How long does DNS authentication take?

Typically 24‑48 hours for SPF/DKIM changes to propagate, but you can send test emails immediately after adding the records.

Is there a limit to the number of contacts I can import at once?

Brevo allows up to 10 000 contacts per CSV import via the UI; larger batches can be split or sent through the bulk import API.

Call to Action

Ready to migrate to Brevo and boost your email performance? Contact our migration specialist today for a free audit and step‑by‑step support.

Internal linking ideas: "How to Set Up SPF/DKIM for Better Deliverability" and "Top 5 Email Automation Workflows for Beginners".

External reference suggestion: Mention the official Brevo API documentation for developers.