Migrate from Brevo Marketing Platform to Mailchimp

Brevo Contacts map to Mailchimp Audience Members. Email address serves as the primary dedupe key and is required on every record. We export Brevo contact attributes (first name, last name, phone, address fields, custom attributes) and map them to standard Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS) and any matching custom merge field names. Brevo's contact storage limit warning is surfaced during scoping: Starter at 5K emails/month caps at 500 contacts, which can silently exclude records during import if the Brevo email volume tier is insufficient for the migrating list size.

Brevo Companies map to contact properties in Mailchimp because Mailchimp has no standalone Company or Account object. We export Company attributes (domain, industry, employee count, address) and merge them into contact records as labeled properties (COMPANY_NAME, COMPANY_DOMAIN, COMPANY_INDUSTRY). This preserves the organizational context but flattens the relationship; contact-to-company lookups are lost. We flag this limitation in the scope document and recommend the customer review whether company-level reporting is needed post-migration.

Brevo Deals (pipeline stages, deal amount, closed-won/lost status) have no native Mailchimp equivalent. We export Deals as a CSV reference document listing each Contact's associated deal value, stage, and pipeline name. The customer's admin decides whether to populate deal values into a custom merge field (DEAL_VALUE, DEAL_STAGE) or retain the CSV as a separate reference sheet. Pipeline configurations do not migrate because Mailchimp's audience model does not support deal records or pipeline stages.

Brevo Tags are flat key-value labels applied to Contacts. They map directly to Mailchimp Tags, which are audience-level labels with no cardinality limits. We export the full tag assignment per contact and recreate them in Mailchimp during the audience import. Tag-based segmentation logic (which Brevo stores as segment filter rules) maps to Mailchimp Segments built from the imported tag assignments.

Brevo Segments are dynamic contact lists based on filter conditions (attribute values, tag membership, engagement status). We export the segment definition including all filter conditions and operators, then recreate each segment in Mailchimp's Segment builder using equivalent Mailchimp filter logic. Brevo's multi-condition AND/OR logic translates to Mailchimp's matching conditions. Static segments (where all members are pre-selected) migrate as Mailchimp Tags or Groups with the member list imported directly.

Brevo Email Campaigns (subject line, sender name, sender email, HTML content blocks) export as campaign metadata and HTML content. We import subject, preview text, and HTML body into Mailchimp Campaigns and Template content. Campaign send history (open rates, click rates) does not migrate because Mailchimp cannot backfill historical engagement metrics for campaigns created outside its platform; we deliver a campaign history report as a PDF inventory for the customer's records.

Brevo email templates export as HTML. We import the HTML into Mailchimp's template builder, preserving layout blocks, images (hosted on Brevo's CDN or re-uploaded to Mailchimp's asset library), and inline styles. Mailchimp's responsive template structure may require minor HTML adjustment if Brevo's email rendering uses non-standard markup. We flag any templates that require post-import adjustment.

Brevo automation Journeys are documented as a written inventory rather than migrated as code. Brevo's 2024 automation editor update introduced a separate migration path where partially migratable Journeys mark unsupported steps as inactive. We audit every active Journey, recording the trigger type, conditions, actions, and delays, then map each to an equivalent Mailchimp Customer Journey trigger and action. We deliver the inventory document to the customer's admin who rebuilds the Journeys in Mailchimp's builder. We do not auto-create Journeys in Mailchimp as part of standard migration scope.

Brevo Custom Objects (available on Enterprise and Pro plans only, API-only creation) have no native Mailchimp equivalent. We export each Custom Object's records and fields and map them to Mailchimp contact merge fields. Field names are preserved as merge field names (with Mailchimp's 30-character limit applied). Multi-record relationships (where one Contact has multiple Custom Object records) are flattened into comma-separated values in the merge field or exported as a separate reference CSV. We confirm during scoping whether the migrating account is on a plan that supports Custom Objects.