Migrate from Brevo Marketing Platform to Salesforce Sales Cloud

Brevo's single flat Contact list has no lifecycle qualification field equivalent to Salesforce's Lead-Contact split. We apply a split rule during migration scoping: Contacts with Brevo attributes indicating marketing-qualified status (opened emails, clicked links, tag-based lead scores) or sales-owned status (linked Deals, assigned Owner with sales role) map to Salesforce Contact attached to Account. All other contacts map to Salesforce Lead. The original Brevo contact attributes (tags, attributes, list memberships) are preserved in custom fields on both Lead and Contact for audit. No Contact is imported without an AccountId parent lookup, so Account creation must complete before Contact import.

Brevo Company records map directly to Salesforce Account. The Brevo company name becomes the Account Name; the domain or website attribute becomes the Account Website field. Company address fields map to BillingAddress. We use Brevo company ID as the dedupe key during import to prevent duplicate Accounts. Account is created before any Contact import so that the AccountId lookup is satisfied at Contact insert time.

Brevo links Contacts to Companies via a company_id attribute on the Contact record. We resolve this relationship at migration time by querying Brevo's contact-company associations and setting AccountId on the Salesforce Contact to the corresponding Account record created from the Company. Any Contact with a company_id referencing a Company that did not export cleanly is held in a reconciliation queue.

Brevo Deal records map to Salesforce Opportunity. The Brevo deal amount maps to Opportunity.Amount; pipeline maps to a Salesforce Record Type and Sales Process; stage maps to Opportunity.StageName. Closed-Won and Closed-Lost stages from Brevo trigger the corresponding Salesforce stage with IsClosed and IsWon flags set. The Brevo deal Owner resolves to Salesforce OwnerId via email match against the User table.

Brevo Deals can have multiple linked Contacts. We migrate these as Salesforce OpportunityContactRole junction records after both the Opportunity and the Contacts exist in Salesforce. Role defaults to 'Decision Maker' unless a role attribute was specified in Brevo; we flag any role ambiguity for manual resolution.

Brevo supports multiple Pipelines each with configurable Stages. We create a Salesforce Record Type per Brevo Pipeline and assign a corresponding Sales Process that whitelists the stage values. Stage probability percentages migrate from Brevo to Salesforce StageProbability. Custom stage names are preserved as picklist values on the Sales Process.

Custom Objects migrate only if the source Brevo account is on Enterprise or Pro plan — Starter and Standard accounts cannot create or receive custom object data. We pre-create the destination custom object schema in Salesforce (API name with __c suffix, all custom fields with typed Salesforce equivalents, lookup relationships, and validation rules) before any data loads. Custom objects that reference Account or Contact via lookup fields are imported last, after the parent records exist.

Brevo tags are flat key-value labels applied to Contacts. We map tags to Salesforce multi-select picklist fields on Contact or Lead depending on the split outcome. For content-classification tags, we map to Salesforce Topics with TopicAssignment records. The customer chooses the tag strategy during scoping.

Brevo Segments are dynamic lists defined by filter conditions on contact attributes. We export the segment filter logic as a written definition and map segments to Salesforce Campaigns with Campaign Member Status logic. Complex behavioral segments (based on event data) are flagged as requiring Salesforce CDP or manual rebuild as Salesforce Reports with filters.

Brevo Email Campaigns and their metadata (subject, sender, send date, list target) migrate as Salesforce Campaign records with Campaign Member Status. Campaign HTML content migrates as a ContentDocument attached to the Campaign. Campaign performance statistics (open rate, click rate, bounce rate) migrate as Campaign custom fields rather than native Salesforce reporting fields.

SMS campaign metadata migrates as Salesforce Campaign records. SMS content, sender IDs, and phone numbers migrate as Campaign custom fields. SMS credits do not migrate — the destination Salesforce org must have its own SMS account provisioned (Twilio, MobilePush, or Salesforce SMS). Sender ID configuration requires manual re-setup in the destination SMS provider.

Brevo Automation Journeys (the drag-and-drop workflow builder) do not migrate as Salesforce Flow because the automation models are architecturally different. Brevo's Journeys use event triggers, delays, and CRM action blocks; Salesforce Flow uses record-triggered, scheduled, and screen variants with different action types. We audit every active Journey, document its trigger conditions and action sequence, and deliver a written map with recommended Salesforce Flow equivalents for the customer's admin to rebuild. Any steps unsupported by Brevo's migration tool land as inactive and are flagged in the inventory.

Brevo Owner records (name, email, role) export via the CRM API. We match Owners by email against the Salesforce destination org's User table. Any Brevo Owner without a matching Salesforce User goes to a reconciliation queue for admin provisioning before record import proceeds. Inactive Salesforce Users cannot own records; we flag any such case for the admin to decide whether to provision a User or reassign ownership.

Brevo's transactional email event log (SMTP or API-sent) is accessible via the Events API with up to 7 days of raw webhook events per export job. We migrate event records as Task records with custom fields capturing event type (delivered, bounced, opened, clicked, failed), timestamp, and message ID. Historical event data beyond the 7-day window requires pre-arranged data pulls from Brevo before migration begins.