Agency Migration Guide
Brevo (formerly Sendinblue) to HubSpot Migration
What actually transfers, what quietly does not, and what has to be rebuilt by hand.
We mapped Brevo (formerly Sendinblue) against HubSpot feature by feature: 34 features, 4 synced objects, 8 documented traps and 27 items that have to be rebuilt. The whole map is on this page, ungated.
The PDF is the same reference, formatted to send to a client.
Get The Guide And The Calculator
The full Brevo (formerly Sendinblue) to HubSpot reference as a branded PDF you can send straight to a client, plus the Excel calculator we scope these migrations with: every one of the 34 features as a row, enter your counts, get hours.
Three files: the guide as a PDF, the same guide unbranded in Markdown for your AI tool, and the full Excel effort calculator.
Brevo (formerly Sendinblue) to HubSpot is a medium migration, typically 3-6 weeks. Of 34 features we mapped, 25 carry across as they are and 8 land with something lost. The work is not moving records: it is the 27 items nothing moves for you.
Migration Scorecard
- Migration complexity
- Medium
- Typical timeline
- 3-6 weeks
- Recommended method
- Brevo native integration for contact sync + CSV export for complete data, with manual rebuild of automations and templates
- Native sync
- Data sync, two way
- Smart transfer
- Not supported
- HubSpot subscription
- Free Brevo account and HubSpot CRM (Free or higher)
Feature parity across 34 capabilities
- Maps directly: 25 (74%)
- Maps partially: 8 (24%)
- No equivalent: 1 (3%)
4
Objects synced natively
8
Limitations and traps
27
Manual rebuild items
4
Source editions covered
Where this comes from: Our own research corpus, verified 2026-08-01, behind every number on this page.
The Four Objects That Sync Natively
What the connector moves for you, and which way each one flows.
Contacts
Out to sourceBecomes Contacts
Contacts sync from HubSpot to Brevo only. Contacts created in Brevo are NOT synced back to HubSpot. Updates made to contacts in HubSpot are reflected in Brevo. Limited to 600,000 contacts.
Companies
Out to sourceBecomes Companies
Companies sync from HubSpot to Brevo. Limited to 100,000 companies.
Deals
Out to sourceBecomes Deals
Deals sync from HubSpot to Brevo. Limited to 50,000 deals.
Email Campaign Events
Into HubSpotBecomes Contact Timeline Activities
Brevo email campaign events sync ONE-WAY to HubSpot contact timelines. Only works for campaigns sent to the synced list. Transactional email activity is NOT synced.
Eight Things the Sync Does Not Tell You
Each one is documented, and each one has ended a migration in a bad week.
Contacts Only Sync HubSpot to Brevo (not Reverse)
Contacts created directly in Brevo are not synced back to HubSpot. The contact sync is effectively one-way from HubSpot to Brevo, with email activity flowing back.
Workaround: Ensure all contact creation happens in HubSpot. Use Zapier or Make for reverse sync if needed.
Hard Volume Caps on Synced Records
The integration is limited to 600,000 contacts, 100,000 companies, and 50,000 deals.
Workaround: For larger databases, use selective list-based sync or a third-party middleware tool.
Date, Multi-choice, and Hs_ Fields Cannot Sync
Date fields, multiple-choice fields, and standard HubSpot system fields (prefixed with hs_, such as Lead Status or Company Domain) cannot be synced.
Workaround: Create custom text properties as intermediary fields and use HubSpot workflows to copy hs_ field values.
Only Static Lists Can Be Imported
Only HubSpot static lists can be synced to Brevo. Active (dynamic) lists are not supported.
Workaround: Create static list snapshots from active lists or use Brevo's own segmentation on synced contacts.
Transactional Email Activity Not Synced
Activity from Brevo transactional emails (order confirmations, password resets, etc.) is not synced to HubSpot.
Workaround: Use Brevo's own transactional email reporting or build a custom webhook integration.
Two-year Consent Window Requirement
Only contacts who have consented to receive updates in the last two years can be imported into Brevo from HubSpot.
Workaround: Re-engage or re-confirm consent for older contacts before migration.
Email Events Only Sync for the Designated List
Synchronization only works with the specific list selected during setup. Campaigns must be sent specifically to this list for events to be reflected in HubSpot.
Workaround: Send all marketing campaigns to the synced list or set up multiple sync configurations.
Automation Workflows Do Not Sync
Brevo automation scenarios, triggers, and workflow logic cannot be exported to or synced with HubSpot. Brevo does not provide API access to automation data.
Workaround: Manually document and rebuild all Brevo automations as HubSpot workflows.
One Brevo (formerly Sendinblue) Feature HubSpot Cannot Replace
Not a workaround away. If a client depends on one of these, it belongs in the conversation before the contract.
Web Push Notifications
HubSpot has no native web push notification feature. Use third-party tools (OneSignal, PushEngage).
The 27 Items That Get Rebuilt by Hand
This is the list that separates a quote that holds from one that does not.
Data And Objects
Contact Lists and Segments
Brevo lists hold contacts, with segments layered on as saved conditions.
HubSpot: Static lists and active lists
Lists import as static. Segments are rules and must be rebuilt as active lists or they freeze at import.
Suppression and Blocklists
Unsubscribed, bounced and blocked addresses held across the account.
HubSpot: Unsubscribed contacts and the opt-out list
Import before the first send. Brevo holds transactional and marketing suppression separately, so collect both.
Transactional Contact Data
Contacts that exist only because they received transactional mail.
HubSpot: Contacts, with a source property
These are usually customers rather than marketing contacts. Importing them without marking them inflates the marketing contact count and the bill.
Contact Attributes Outside the Standard Mapping
Brevo attributes with no obvious HubSpot counterpart.
HubSpot: Custom properties
Create the properties before the import. Attributes created on the fly land as text and lose their type.
Automation
Automation Scenarios
Brevo's multi-step automation flows.
HubSpot: Workflows
Rebuilt step by step. Capture each scenario visually before access ends, because the logic does not export readably.
Triggered Email Sequences
Sends fired by a contact action or attribute change.
HubSpot: Workflows
Check what each trigger watches. Brevo fires on attribute change more often than teams remember.
Branching Automation Logic
If/then paths inside Brevo automations.
HubSpot: Workflow branching logic
Branch conditions are where meaning shifts. Walk each branch with whoever owns the campaign rather than translating on sight.
Transactional Email Templates and Triggers
Templates and the API calls that fire them.
HubSpot: Transactional email or a dedicated sending service
Transactional sending is a separate purchase decision on HubSpot, and the sending code changes too. Confirm the route before scoping.
SMS Automation
Text sends inside Brevo automations, where used.
HubSpot: HubSpot SMS or a marketplace SMS app
Consent records move with the numbers. Confirm which SMS route the client is buying before scoping.
WhatsApp Campaign Automation
WhatsApp sends configured in Brevo, where used.
HubSpot: A marketplace WhatsApp app
Not a native HubSpot channel. This needs a third-party product and its own template approval process, which is a timeline risk, not just a cost.
Reporting
Campaign Performance Reports
Per-send open, click and bounce reporting.
HubSpot: Marketing email analytics
Historical sends do not transfer. Export a final set before the account closes.
Email Heat Maps
Brevo's click-position heat map on a send.
HubSpot: Click maps in email analytics
Available going forward only. Historical heat maps are lost with the send history.
Custom Report Dashboards
Saved dashboard views used for recurring reporting.
HubSpot: Dashboards and custom reports
Rebuild from the question each answers rather than reproducing the layout.
Transactional Delivery Reports
Delivery and bounce reporting for transactional sends.
HubSpot: Depends on the transactional route chosen
Reporting follows whichever transactional service replaces Brevo, so this cannot be scoped until that decision is made.
Sales And Marketing Config
Email Templates
Branded send templates built in Brevo's editor.
HubSpot: Marketing email templates
No import path between editors. Rebuild from brand assets rather than pasting exported HTML.
Landing Pages
Brevo hosted pages, where used.
HubSpot: Landing pages
Rebuilt page by page. Redirect any URL linked from ads or printed material.
Signup Forms
Embedded and hosted forms feeding Brevo lists.
HubSpot: Forms
Swap every website embed at cutover or signups keep landing in the old account.
SMS Campaigns
One-to-many text sends.
HubSpot: HubSpot SMS or a marketplace SMS app
Same decision as the SMS automation above. Scope them together rather than twice.
WhatsApp Campaigns
One-to-many WhatsApp sends.
HubSpot: A marketplace WhatsApp app
Needs a third-party product plus template approval. Raise it before the contract if the client runs WhatsApp at volume.
Lead Scoring Model
Scoring used to rank contacts by engagement.
HubSpot: Score properties
Built from scratch. The old weights are a hypothesis, not a specification.
Chat Widget
Brevo's on-site chat, where used.
HubSpot: HubSpot chat and the inbox
The widget swaps easily; the routing and availability rules behind it are the actual work.
Users And Permissions
User Accounts and Roles
Logins and the permission level attached to each.
HubSpot: Users and permission sets
Created fresh. Audit the list first rather than recreating dormant logins.
API Keys and Access Tokens
Credentials used by code and connectors talking to Brevo.
HubSpot: Private app tokens
Every consumer of an old key has to be found and repointed. Inventory them before the old account is closed, not after.
Integrations
Third-party App Connections
Commerce and CMS plugins joining Brevo to the stack.
HubSpot: App Marketplace integrations
Reconnected individually. Check field mapping on each rather than assuming parity by name.
Custom API Integrations
Bespoke code written against the Brevo API.
HubSpot: HubSpot APIs
Rewritten against a different object model. Scope against the code, not a description of it.
Webhook Configurations
Outbound webhooks fired by Brevo events.
HubSpot: Workflow webhook actions
The receiving endpoint expects Brevo's payload shape, so both ends usually need work.
Brevo Tracker Website Tracking
The on-site script recording visitor behaviour for Brevo.
HubSpot: The HubSpot tracking code
Swap the script at cutover. Historical visitor data does not come across, so behavioural reporting restarts.
The Sequence
Sync First, Then Migrate
Order is the content here. These are a dependency chain, and running them out of order is a documented way these migrations fail.
- 1
Audit Brevo Account
contact lists, automation scenarios, templates, transactional emails, integrations, SMS/WhatsApp campaigns
- 2
Export All Contacts as CSV With All Attributes
Export all contacts as CSV with all attributes
- 3
Export Blacklists/suppression Lists (unsubscribed, Bounced, Spam Reporters)
Export blacklists/suppression lists (unsubscribed, bounced, spam reporters)
- 4
Export Email Template HTML for Rebuild Reference
Export email template HTML for rebuild reference
- 5
Document All Automation Scenarios With Full Logic Trees
Document all automation scenarios with full logic trees
- 6
Document Transactional Email Templates and Triggers
Document transactional email templates and triggers
- 7
Clean Data
deduplicate, validate emails, handle consent dates
- 8
Import Suppression Lists Into HubSpot BEFORE Any Sends
Import suppression lists into HubSpot BEFORE any sends
- 9
Import Contacts With Proper Field Mapping
Import contacts with proper field mapping
- 10
Recreate Lists and Segments in HubSpot
Recreate lists and segments in HubSpot
- 11
Rebuild Email Templates in HubSpot
Rebuild email templates in HubSpot
- 12
Recreate Automation Workflows in HubSpot
Recreate automation workflows in HubSpot
- 13
Set up Transactional Email Solution (HubSpot Transactional or Third-party)
Set up transactional email solution (HubSpot transactional or third-party)
- 14
Replace Brevo Tracker With HubSpot Tracking Code on Website
Replace Brevo Tracker with HubSpot tracking code on website
- 15
Configure Email Authentication (SPF, DKIM, DMARC)
Configure email authentication (SPF, DKIM, DMARC)
- 16
Warm Sending Domain Over 4-6 Weeks
Warm sending domain over 4-6 weeks
- 17
Migrate SMS/WhatsApp Campaigns If Applicable
Migrate SMS/WhatsApp campaigns if applicable
- 18
Decommission Brevo After Full Transition
Decommission Brevo after full transition
Typically 3-6 weeks end to end, depending on how much of the source configuration is actually in use.
Effort Estimator
How Big Is This Migration?
A handful of questions, no email required. The ranges come from the research above: every feature we mapped carries an effort figure, and this adds up the ones that apply to you.
Estimated Effort
Answer a couple of questions and an hours range appears here.
Built from our research on 34 Brevo (formerly Sendinblue) features. It is a range, not a quote.
A planning range, not a quote. It is delivery effort only, with no project management line and no agency markup, so add your own. What moves it most in practice is data quality.
What Goes Wrong Most Often
The failures that show up again and again, in roughly the order they bite.
Contacts Created in Brevo Don't Sync Back to HubSpot, Creating Data Gaps
Contacts created in Brevo don't sync back to HubSpot, creating data gaps
Volume Limits Hitting Unexpectedly for Larger Databases
Volume limits hitting unexpectedly for larger databases
Transactional Email Activity Not Syncing, Losing Delivery Visibility
Transactional email activity not syncing, losing delivery visibility
Static-only List Import Limitation Blocking Dynamic Segmentation Workflows
Static-only list import limitation blocking dynamic segmentation workflows
Date and Hs_ Field Restrictions Causing Data Mapping Failures
Date and hs_ field restrictions causing data mapping failures
SMS and WhatsApp Both Exist in HubSpot but Neither Is Included
SMS needs the Marketing SMS add-on on Marketing Hub Professional, and WhatsApp needs a Meta Business account on Marketing or Service Hub Professional. Price both before quoting.
Two-year Consent Window Filtering Out Valid Contacts
Two-year consent window filtering out valid contacts
Brevo's Automation Builder Logic Not Directly Translating to HubSpot Workflow Branches
Brevo's automation builder logic not directly translating to HubSpot workflow branches
Questions
Brevo (formerly Sendinblue) To HubSpot, Answered
Yes. Data sync, two way, covering 4 objects. What it does not do is rebuild configuration: that is the 27 items below.
Typically 3-6 weeks. Complexity is driven by automation and reporting depth, not by record count: the connector moves records, so a large database is not by itself a long project.
Of 34 features we mapped, 25 (74%) carry across directly and 8 (24%) map partially, meaning something is lost or reshaped. 1 has no HubSpot equivalent at any tier.
27 items have to be rebuilt by hand, and 8 documented limitations are not surfaced by the connector at all. The full list of both is on this page.
Free Brevo account and HubSpot CRM (Free or higher)
1: Web Push Notifications. If a client depends on one, it belongs in the conversation before the contract.
Only in one direction. The sync is not bidirectional here, so a parallel period means picking a system of record and accepting drift in the other.
Ready to get started?
Let's do something great together.
Augment your agency's marketing team's bench with our end-to-end inbound and digital solutions and find out why we're "The HubSpot Agency for HubSpot Agencies."
Fill out this form, and someone from our Solutions team will be in touch with you soon!