Migrate from Brevo Marketing Platform to Pipedrive

Brevo Contacts map to Pipedrive People. Email address is the dedupe key. All standard contact attributes (first name, last name, phone, address, attributes) migrate via the Pipedrive API. Custom attributes migrate as custom fields on Person if the destination Pipedrive plan supports custom fields. Brevo tag assignments migrate as Pipedrive Person fields or as activity notes depending on the tag volume. Brevo list membership (segment membership) migrates as Pipedrive Person fields with the list name as field label.

Brevo Companies map to Pipedrive Organizations. Organization is created or upserted first so that the Organization lookup reference is satisfied at the moment of Person import. Brevo company attributes map to Pipedrive Organization custom fields. We use the Brevo company domain as the Organization name fallback when the company name field is blank. Multiple Brevo contacts associated with a single company link to the same Organization record.

Brevo Deals map to Pipedrive Deals. The deal title maps to Pipedrive Deal title, the Brevo dealstage maps to a Pipedrive stage within the designated pipeline, and the Brevo pipeline assignment maps to a Pipedrive pipeline. Closed-won and closed-lost status from Brevo map to Pipedrive status values. We preserve the original deal ID as a custom field for audit trails.

Brevo pipeline stages migrate to Pipedrive stages within the target pipeline. Stage probability percentages migrate from Brevo to Pipedrive. We configure the Pipedrive pipeline in the destination account before migration so that the stage reference exists before any Deal record is inserted. Custom stage names are preserved as written on Pipedrive.

Brevo's multiple deal pipelines map to Pipedrive pipelines. We create the Pipedrive pipeline configuration (name, stages, probabilities) during the pre-migration schema setup phase. If Brevo has more pipelines than the destination Pipedrive plan supports, we discuss consolidation options with the customer during scoping.

Brevo Custom Objects (Enterprise or Pro only) migrate to Pipedrive custom fields on the closest standard entity (Person, Organization, or Deal). Pipedrive's Advanced plan supports custom entities, which we evaluate against the customer's custom object count and relationship complexity. If the destination plan does not support the equivalent custom entity type, we map custom attributes to Person or Organization custom fields as flat key-value pairs and flag the limitation for the customer.

Brevo task engagements map to Pipedrive Activities with type=Task. Subject, body, due date, completion status, and owner assignment migrate. We resolve Brevo owner email to Pipedrive User by email match. If the owner has no Pipedrive User, the activity is held in a reconciliation queue for the customer to provision the user or reassign.

Brevo call engagements map to Pipedrive Activities with type=Call. Call duration, disposition notes, and timestamp migrate. We link the activity to the corresponding Person or Organization record. Recording URLs do not migrate through the API as Pipedrive does not store call recordings as a standard field.

Brevo meeting engagements map to Pipedrive Activities with type=Meeting. Start time, end time, location, and title migrate. Attendees resolve to Person records by email match. If a participant has no matching Person, we link the meeting to the Deal or Organization instead.

Brevo note engagements map to Pipedrive Notes attached to the relevant Person, Organization, or Deal. Note body and timestamp migrate. We use the note's associated contact or deal as the target entity reference. If a note references multiple contacts, we attach it to the primary Person and add a reference in the note body to the secondary contacts.

Brevo tags are flat key-value labels on Contacts. We export all tag assignments and either map them to Pipedrive Person custom fields (if tag count is under 50 and discrete values) or attach them as Pipedrive Labels on the Person record. The customer chooses the tag strategy during scoping based on the tag count and usage pattern.

Brevo Owners (sales reps with CRM access) map to Pipedrive Users. We resolve by email address. Any Brevo Owner without a matching Pipedrive User goes to a reconciliation queue. The customer provisions the Pipedrive User before migration resumes. Owner assignments on Deals and Contacts resolve after the User mapping is complete.