Migrate from Brevo Marketing Platform to Microsoft Dynamics 365 Sales

Brevo uses a single Contact object with a lifecycle stage property (subscriber, lead, marketing qualified, sales qualified, customer, evangelist). Dynamics 365 Sales splits unqualified contacts into Lead records and qualified contacts into Contact records attached to an Account. We define the split rule during scoping based on the customer's lifecycle stage matrix. Lifecycle Stage from Brevo is preserved in a custom field on both the Lead and Contact in Dynamics for audit. Email address serves as the dedupe key for both Lead and Contact. Brevo list membership is preserved as a custom multi-select picklist on the contact or lead rather than as a native list object.

Brevo Companies map to Dynamics 365 Sales Accounts. The Company name becomes Account Name, domain becomes Website, and address fields map directly. We create or upsert Accounts before any Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. Brevo allows multiple Contacts per Company; Dynamics models this as multiple Contact records all pointing to the same AccountId. Company hierarchy in Brevo (parent-company relationships) maps to the Account hierarchy feature in Dynamics if the customer uses it.

Brevo Deals map to Dynamics 365 Opportunities. The deal value maps to Amount, close date maps to CloseDate, stage maps to StageName, and pipeline maps to a Dynamics Record Type and Sales Process. Brevo's pipeline-stage combinations are pre-configured as Sales Processes in Dynamics before migration so that stage probability and probability-based forecasting are active from day one. Custom deal properties (lost reason, win reason, internal notes) become custom fields on the Opportunity object.

Brevo Pipelines become Dynamics Record Types on Opportunity. Each Record Type gets its own Sales Process that defines the allowed StageName values and their probabilities. We export the Brevo pipeline configuration via the CRM Deals API, translate stage names and probabilities, and deploy Record Types and Sales Processes to the destination org before any Deal data is imported.

Brevo engagement records (call, email, meeting, task, note) map to Dynamics Task and Event objects. Calls use Task with TaskSubtype = Call and duration preserved in a custom field. Emails with content map to EmailMessage linked to a Task for the activity timeline. Meetings map to Event with start and end time preserved. Notes map to the Note (or Enhanced Note) object linked via the regarding field to the parent Contact, Lead, Account, or Opportunity. All timestamps are preserved as ActivityDate so the historical timeline is intact.

Brevo custom contact attributes are stored as flat key-value pairs on the Contact object. We map these to Dynamics 365 custom fields on the Contact entity (or Lead, Account, or Opportunity depending on what the attribute describes). Data type is inferred from the Brevo attribute value format and mapped to the corresponding Dynamics field type (string, number, boolean, date). We pre-create the custom field schema in Dynamics before migration so that the import payload has valid field references.

Brevo tags are flat key-value labels applied to Contacts. Dynamics 365 Sales does not have a native tag object. Tags are mapped to a custom multi-select picklist field on Contact or Lead. During scoping, the customer chooses which tags to preserve as persistent labels and which to discard. High-cardinality tags (more than 50 distinct values) are flagged for review as multi-select picklist limits vary by Dynamics edition.

Brevo segments are dynamic lists defined by filter conditions on contact attributes. Dynamics 365 Sales does not have native dynamic segment logic. Segments are recreated as Views (Saved Queries) using the equivalent filter criteria on the Contact or Lead entity. Active segments are documented with their filter logic during scoping. Segments requiring real-time dynamic membership require a custom Power Automate flow, which is flagged for the customer's admin to configure post-migration.

Brevo owners (users assigned to Contact, Company, or Deal records) map to Dynamics 365 Users by email address. We extract the distinct owner set from all migrating records, match by email against the destination org's User table, and flag any owner without a matching User for the customer's Dynamics admin to provision. Active status and role assignment are determined by the admin based on whether the original Brevo owner is still active in the new system.

Brevo SMS campaigns, sender IDs, and phone number configuration do not have a direct Dynamics 365 Sales equivalent. Dynamics 365 Customer Insights – Journeys (a separate module) supports SMS but requires separate licensing and configuration. We export SMS campaign metadata and configuration settings as a written document for the customer's admin to review. SMS sender IDs and phone number provisioning must be set up independently in the destination platform.

Brevo email campaigns and their performance metrics (opens, clicks, unsubscribes) are marketing objects without a direct Dynamics 365 Sales equivalent. We export campaign names, subjects, and send dates as reference records linked to the relevant Brevo Contact. Campaign performance metrics are preserved as a separate reporting artifact for the customer's marketing team to reference. Dynamics 365 Customer Insights – Journeys supports equivalent marketing campaigns but requires separate licensing.