Migrate your Brevo Marketing Platform data

Contacts are the primary CRM object in Brevo. We export all standard attributes (email, phone, attributes, tags, lists) via the Contacts API endpoint. Note that daily exports were deprecated on May 30th, 2025 — we use the Contacts API or CSV exports from the UI for all outbound migrations. Inbound imports use the batch upsert endpoint, and we preserve list/segment assignments via the import API.

Companies represent organizations associated with Contacts. We export Companies and their attributes via the Companies API. On inbound, we create or upsert Companies first, then associate them with imported Contacts by matching on the Brevo company ID or unique company name.

Deals track sales opportunities and can be exported as CSV from the Deals UI or retrieved via the CRM Deals API. Each Deal has a pipeline and stage, which we map to the destination's equivalent pipeline model. Deal IDs are auto-generated strings that must be included in any bulk update file to avoid creating duplicates.

Brevo allows multiple Pipelines, each with configurable Stages. We export the pipeline and stage configuration via the CRM API and map them to the destination pipeline model. Custom stage names are preserved as labels; we do not recreate the Kanban structure itself on the destination unless explicitly requested.

Automation workflows (called Journeys in some UI contexts) are migrated as activity sequences. Brevo's new automation editor (introduced 2024) has a separate migration path — partially migratable workflows mark unsupported steps as inactive. We reconstruct the workflow logic as step descriptions in the destination and flag any steps that cannot be replicated due to platform differences.

Custom Objects are only available on Enterprise or Pro plans and can only be created via the API (not the UI). Bulk upsert uses the asynchronous /objects/{object_type}/batch/upsert endpoint. We migrate custom object schemas and records but require confirmation of the destination plan tier, as the destination must also support custom objects.

Email campaigns and their attributes (subject, sender, content blocks, scheduling) can be exported. Campaign content blocks are exported as HTML. We preserve campaign statistics separately as reporting data since campaign history does not automatically replicate to the destination.

SMS campaigns are exported with the same logic as email campaigns. SMS credits are not migratable — the destination platform must have its own SMS account provisioned. Sender IDs and phone numbers are preserved as attributes on the destination.

Tags are flat key-value labels applied to Contacts. Segments are dynamic lists based on filter conditions. We export tag assignments and segment definitions (filter logic) and recreate them on the destination. Dynamic segment membership is recalculated at import time rather than hard-imported.

Brevo bills per marketing seat at $9/month. User records (name, email, role) are exported but user seat assignment is a billing configuration rather than a data migration artifact. We flag whether the destination requires manual seat provisioning after the migration.

Brevo's transactional email log (SMTP relay or API-sent) is accessible via the Events API or the weekly event export webhook service. We can export up to 7 days of raw webhook events per export job. Historical log retention is unlimited on the platform side, but export scope is bounded by the API.

Landing pages are rendered as Brevo-hosted HTML with form integrations. We do not migrate landing page designs because the HTML is not independently exportable and the form-submission endpoints are tightly coupled to Brevo's contact capture. We migrate the resulting contact records instead.