Migrate from Brevo Marketing Platform to HubSpot

Brevo contacts migrate as HubSpot contacts. Brevo's standard attributes (email, firstname, lastname, phone, company, job title, city, country, created date) map directly to HubSpot contact properties. Brevo's owner_id resolves to HubSpot OwnerId by email match — un matched owners are flagged before the migration runs.

Brevo lifecycle_stage values (subscriber, lead, MQL, SQL, customer, evangelist) have no direct HubSpot CRM equivalent — HubSpot's lifecycle_stage property is the target. We create the lifecycle_stage property in HubSpot (if not already present) and map Brevo values value-by-value. Teams using Brevo's marketing automation to drive lifecycle progression will need to rebuild that logic in HubSpot workflows.

Brevo companies migrate as HubSpot companies. Standard attributes (name, domain, city, country, industry, phone, number of employees, annual revenue) map to HubSpot company properties. Brevo parent-company hierarchies use a parent_id field — we resolve this using HubSpot's Parent Company lookup once all company records are loaded.

Brevo deals migrate as HubSpot deals. Each deal carries its associated pipeline and stage name. HubSpot requires the pipeline to exist in the portal before deals are imported — we deliver a pipeline setup checklist as part of the migration plan so your HubSpot admin creates deal pipelines before the data load.

Brevo pipelines (each with its own set of stages) translate to HubSpot deal pipelines. HubSpot allows multiple named pipelines each with custom stage sequences. We map Brevo pipeline names to new HubSpot pipeline names and Brevo stage names to HubSpot stage names within each pipeline. Probability and forecast category are re-applied from HubSpot's stage defaults or your specified configuration.

Brevo users are matched to HubSpot owners by email address. The migration flags any Brevo user whose email does not find an existing HubSpot user — your team either creates the HubSpot user first or assigns their records to a fallback owner. No deal or contact lands in HubSpot without a resolved owner.

Brevo email history, meetings, and notes migrate as HubSpot engagements on the respective contact timeline. Emails become engagement events with subject, body, and timestamp. Meetings become calendar-style engagement entries with duration and title. Notes migrate as HubSpot notes with original create dates and owning user preserved.

Brevo custom attributes on contacts, companies, and deals (accessible only on Enterprise and Pro plans via API) become HubSpot custom properties. The HubSpot portal must have the custom property schema pre-created before migration — we deliver a schema definition sheet listing each Brevo custom attribute name, data type, and corresponding HubSpot property type to create.

Brevo contact tags map to a HubSpot contact property (a multi-value string property or a static list). Tags with high cardinality are reviewed with your team before import — excessively long tag lists on individual contacts can exceed HubSpot property length limits.

Brevo automation workflows and email sequences do not have a HubSpot equivalent that can receive a direct migration. The workflow logic, trigger conditions, and action steps are platform-specific. We export your Brevo workflow definitions as a JSON reference and provide a rebuild guide mapped to HubSpot's workflow builder so your admin can reconstruct the logic.