Migrate from Brevo Marketing Platform to Twenty CRM

Brevo Contacts map directly to Twenty Contacts. We extract via GET /contacts with cursor-based pagination (Brevo's standard pagination method, not the deprecated daily export), preserving all standard attributes (email, firstName, lastName, phone, sms, attributes). Custom attributes on Brevo contacts (any key-value attributes beyond standard fields) map to Twenty custom fields that we create during schema setup. Email subscription status (emailBlacklisted) maps to a boolean field we add to Twenty's Contact schema. The Brevo contact's assigned company (links to a Companies record) is resolved by creating the Company in Twenty first, then setting the contact's companyId lookup at insert time.

Brevo Companies map to Twenty Companies. We export via GET /companies, preserving companyName, address fields, industry, website, and any custom company attributes. The company domain is stored as website for deduplication reference. Twenty does not have a native industry picklist, so Brevo industry values migrate as free-text unless the customer has pre-configured a picklist in Twenty.

Brevo Deals map to Twenty Deals with the pipeline and stage preserved. Each Deal carries a Brevo pipelineId and stageId; we resolve these to Twenty's pipeline and stage model during schema setup. Deal amount, probability (if set in Brevo), close date (closeDate), and notes migrate directly. Deals without a linked company are migrated as unassociated deals and flagged for manual review.

Brevo pipelines (up to 5 on Standard, more on Professional/Enterprise) map to a Twenty pipeline. We create the pipeline in Twenty during schema setup, configure stage names and order to match Brevo's stage names and positions, and set stage probabilities to match Brevo's stage-level probability values where they exist. Stage-level win/loss status from Brevo maps to the stage type in Twenty (standard, won, lost).

Brevo Tags are flat key-value labels applied to Contacts and Companies. We extract all unique tag keys from Brevo and recreate them in Twenty. Tag assignments (which contacts carry which tags) migrate as multi-select label entries on the Twenty Contact record. If Twenty's tag model differs from a flat list, we map tags to a custom multi-select picklist field on Contact. The customer confirms the preferred tag strategy during scoping.

Brevo Custom Objects (available on Pro and Enterprise plans) map to custom tables in Twenty. We export the custom object schema (field names, types, relationships) from Brevo via the API, create matching custom fields in Twenty's Contact, Company, or Deal schema, and migrate the records with lookup resolution to parent records. If the destination uses a different data model for a custom object (for example, Brevo stores a custom object as its own top-level entity), we map it to a custom field group on the nearest standard object rather than a standalone entity.

Brevo Users (team members with assigned seats) map to Twenty Users. We extract user records (name, email, role) via GET /users. The Brevo marketing seat count ($9/month per seat) does not map directly to Twenty's per-seat pricing, but the number of active Brevo users serves as a baseline for estimating the Twenty seat count. Users without a matching email in the Twenty destination are placed in a reconciliation queue for the admin to provision before record import proceeds.

Brevo Notes (engagement type NOTE) attached to Contacts or Deals map to Twenty Comments. We extract note content, author (resolved to a Twenty User by email), and timestamp. Notes are associated with the parent Contact or Deal record via the appropriate lookup field in Twenty. Rich-text formatting in Brevo notes is preserved as-is in the comment body.

Brevo meeting engagements (Calendar events linked to Contacts) map to Twenty Comments with a timestamp and meeting indicator, or to a Task if the customer has configured a meeting task model. We extract event title, start/end datetime, attendee list, and notes. The organizer is resolved to a Twenty User by email match.

Brevo Segments (dynamic lists based on filter conditions) define filter logic against Contact attributes. We export the segment definitions (filter criteria, logic operators, combine rules) as a written document. Segments do not have a direct equivalent in Twenty CRM because Twenty's list model is based on saved filters rather than a separate segment object. We deliver a written segment catalog that maps each Brevo segment to a recommended Twenty saved filter configuration for the admin to implement.

Brevo Email Campaigns are marketing communication artifacts (subject lines, content blocks, send history, open/click data) that belong to a marketing platform, not a CRM. We export campaign metadata (name, subject, send date, recipient count, open rate, click rate) as a CSV reporting artifact. The campaign content (HTML blocks, templates) does not migrate. The customer should maintain this data in Brevo or a dedicated email marketing tool if reporting history is needed.

Brevo SMS Campaigns and SMS credits are marketing communication artifacts with no equivalent in Twenty CRM. We export SMS campaign metadata as a CSV reporting artifact. SMS sender IDs and phone numbers require provisioning on a separate SMS platform (Twilio, MessageBird, or similar) and are not CRM data. If the customer needs SMS capability in Twenty, we flag this as a separate integration scope.