Move from Brevo to Bento.

Export your Brevo data, bring it into Bento, and rebuild what matters while Brevo keeps sending. Cancel only when Bento is ready.

Import from BrevoEasy migration
CSVsendinblue-contacts.csv12,400 rows, mapped
  • SubscribersImports directly
  • TagsImports directly
  • Custom fieldsImports directly
  • AutomationsRebuild in Bento
  • TemplatesRebuild in Bento
  • Commerce dataPartly moves
  • Email historyStays behind
3 of 7kinds of data import directly
  • Laravel News
  • Examine
  • Less Annoying CRM
  • Geocodio
  • Authority Hacker
  • HeadshotPro
  • QuickMail

Brevo to Bento, at a glance.

From Bento's Brevo migration guide. Still deciding? Read Bento vs Brevo.

Easy

Migration difficulty

Varies by contacts, automations, channels, and integrations.

3 of 7

Kinds of data that import directly

The rest you rebuild in Bento or leave behind.

4

Export steps in Brevo

Each one is written out below, with tips.

Your time depends on list size and how many flows you rebuild.

Four steps off Brevo.

Brevo keeps sending the whole time. You cancel only after Bento carries your mail.

  1. Export from Brevo.

    4 steps in Brevo, in the order below. Nothing changes for your subscribers yet.

    Export from Brevo4 steps
    1. 1Log in to BrevoGo to Brevo.com and log in.
    2. 2Export ContactsGo to Contacts > Lists. Export each list as CSV.
    3. 3Document AutomationsScreenshot your automation workflows.
    4. 4Export Blocklisted ContactsExport blocklisted contacts for suppression.
    Keep Brevo sending while you export.
  2. Import into Bento.

    Upload the CSV and map each column to a Bento field or tag. Suppressions go in first, so nobody who left gets mail.

    PeopleImportssendinblue-contacts.csv

    Start import
    CSV columnBento fieldType
    • emailEmailIdentity
    • first_nameFirst nameField
    • last_nameLast nameField
    • tagsTagsTags
    • planplanCustom field
    • last_order_atlast_order_atCustom field

    Rows

    12,400

    Before sending

    • Suppressions imported first
    • Unsubscribes kept unsubscribed
    • Tags created from the tags column
  3. Test, then switch.

    Authenticate your sending domain, rebuild the flow that earns the most, and send a seed test while Brevo keeps sending.

    Launch checklist4 of 5
    • Sending domain authenticated in Bento
    • Suppressions moved from Brevo
    • Seed test sent and checked
    • Highest-revenue flow rebuilt and tested
    • Switch sending to BentoNext
    Warm up with your most engaged subscribers first.
  4. Cancel Brevo last.

    Warm up with your most engaged subscribers, move the rest of your sending, and cancel Brevo only once Bento carries it.

    Sending, by phase
    PhaseBrevoBento
    1. ExportSendingNot yet
    2. ImportSendingImporting
    3. Rebuild and testSendingTesting
    4. Warm upSendingWarming
    5. Cancel BrevoOffSending
    No gap in sending at any phase.

Export your Brevo data.

Run these in Brevo before you change anything there. Keep the files somewhere safe until Bento is sending.

  1. 1

    Log in to Brevo

    Go to Brevo.com and log in.

  2. 2

    Export Contacts

    Go to Contacts > Lists. Export each list as CSV.

  3. 3

    Document Automations

    Screenshot your automation workflows.

  4. 4

    Export Blocklisted Contacts

    Export blocklisted contacts for suppression.

What comes with you.

3 of 7 kinds of data import directly. The rest you rebuild in Bento or leave behind.

Your import checklist

Import from Brevo3 of 7 direct
  • SubscribersImports directly
  • TagsImports directly
  • Custom fieldsImports directly
  • AutomationsRebuild in Bento
  • TemplatesRebuild in Bento
  • Commerce dataPartly moves
  • Email historyStays behind

Same ideas, new names

BrevoBento
  • ContactPersonIndividual subscriber
  • ListTagBento uses tags
  • ScenarioAutomationAutomated workflows
  • CampaignBroadcastOne-time sends

Before you cancel Brevo

  • Brevo exports contacts and selected attributes as CSV
  • Include List ID and subscription status, then map Brevo lists to Bento tags
  • CRM deals and conversation history need separate migration plans
  • Automations, templates, landing pages, and message history do not transfer through a contact CSV

Get a person to plan the move.

Tell us your current provider, list size, and what you need to keep. We map the order to move things and review your domain setup before you send.

A migration request

you@example.comMigration quote

We are on Brevo with 12,400 contacts. We need to keep subscribers, tags, and suppressions.

Bento teamReplied

Thanks. Start with suppressions, then your list, then the flows that make money. We can review your domain setup before you send.

Teams switch for deliverability and stay for the support.

“Moving to Bento was the best thing I ever did for my list and its profitability”
Iliane L.G2
“I love how easy it is to use to design SaaS emailing sequences. You can also see rapidly which campaigns are the money makers. But what I love the most is undoubtedly the deliverability that you have once you've set up custom domain tracking”
Arnaud B.G2
“The support and community within Bento is hands down the best I've ever seen from any company, ever.”
Luke J.G2

Questions about leaving Brevo.

Will I lose my Brevo contacts and automations when I switch?
Brevo can export contacts, selected standard and custom attributes, List ID, and subscription status as CSV. Map lists to Bento tags and import suppressions before sending. Automations need to be rebuilt and tested because a contact CSV does not transfer workflow definitions.
Will switching hurt my email deliverability?
No provider can guarantee inbox placement after a switch. Preserve suppressions, configure authentication, warm the sending setup with engaged recipients, and monitor bounces and complaints. Bento includes reputation monitoring and sending controls, but your audience, content, and sender reputation still matter.
How long does a Brevo migration take?
The timeline depends on your contacts, automations, templates, landing pages, sales workflows, channels, integrations, domains, and reporting needs. A contact-only move is smaller than migrating the full Brevo suite, so plan a phased cutover instead of a fixed hour estimate.
Will there be downtime?
No. Keep Brevo running while you import, test, authenticate your sending domain, and warm up. Once Bento is ready, move your sending and phase out Brevo.
Can the Bento team help if I get stuck?
Yes. The team can review your current setup, help you decide what to move first, and advise on deliverability, data mapping, and launch order.

Other migration guides.

Start your move from Brevo.

Free for 30 days. We help you move your lists, flows, and templates.