Migrate from Brevo Marketing Platform to Odoo CRM

Brevo Contact records map directly to Odoo res.partner records with partner_type set to 'contact'. The contact email is the dedupe key. Standard Brevo attributes (first name, last name, phone, mobile, city, country, birthday) map to the corresponding Odoo contact fields. Brevo custom attributes (attributes array) migrate as Odoo custom fields on res.partner created in Odoo Studio before migration. Brevo tag assignments migrate as Odoo tags (mail.message.subtype) linked to the Contact via mail.followers. Any Brevo contact with no email address is held in a reconciliation queue because Odoo requires an email for partner deduplication.

Brevo Company records map to Odoo res.partner with partner_type = 'company' and is_company = True. The company name maps to name, domain maps to website, and Brevo address fields map to Odoo address fields on the related partner record. Odoo allows multiple contacts (employees) to be linked to a single company partner, matching Brevo's contact-to-company relationship. Company is created before any contact import so that the child contact can reference the parent company via parent_id.

Brevo Deal records map to Odoo crm.lead (Opportunity). The deal name becomes the Opportunity name, amount becomes expected_revenue, expected_close_date maps to date_deadline, and the Brevo pipeline and stage map to the Odoo pipeline and stage in the crm.lead record. Brevo deal contacts and companies link to the crm.lead's partner_id (primary contact) and partner_ids (multi-contact link) fields. Lost Deals migrate with the lost reason preserved as a note.

Brevo pipelines map to Odoo Sales Teams (crm.team), each with its own pipeline kanban view. We create Odoo Teams during schema setup, naming them to match the Brevo pipeline labels. Each Team's crm.lead.pipeline records get the corresponding stage columns created in Odoo's pipeline view. The Odoo team_id field on crm.lead is populated from the Brevo pipeline assignment.

Brevo stage names migrate as Odoo crm.stage records attached to each Odoo team. Stage probability percentages map from Brevo to Odoo's probability field, rounded to the nearest integer. Stage sequence order is preserved for kanban column ordering. Custom stage colors in Brevo do not transfer; Odoo stage colors are configured by the admin post-migration.

Brevo automation workflows (Journeys) do not migrate as code because the trigger-action model differs fundamentally from Odoo's Server Actions and Automated Actions. We deliver a written inventory of every active Brevo automation with its trigger type, conditions, actions, and a recommended Odoo Studio equivalent. Odoo's Studio Automated Actions support record-triggered, time-based, and cron-triggered automations, but Python-level Server Actions require developer involvement. Brevo workflow steps that cannot be represented in Odoo Studio are explicitly flagged in the inventory.

Brevo Custom Objects (Enterprise and Pro only) require pre-migration schema design in Odoo. If the destination Odoo instance uses the same custom object concept, we create a matching Odoo model via Studio or Python and populate it with Brevo's Custom Object records via the Odoo XML-RPC API. If the destination Odoo does not have custom model support enabled, we map the custom object attributes to custom fields on the Odoo res.partner record. All custom fields are created before data import begins.

Brevo email campaign metadata (name, subject, sender name, sender email, send date, status) migrate as Odoo mass.mailings records within a corresponding Odoo crm.tag or utm.campaign record for tracking. Campaign HTML content migrates as a template in Odoo's email template system. We do not migrate Brevo campaign delivery statistics (open rate, click rate) as Odoo does not store these natively — we deliver them as a CSV alongside the migration for the customer to import into a BI tool or spreadsheet.

Brevo SMS campaign metadata migrates to Odoo sms.sms records. SMS credits are not migratable — the destination Odoo instance must have its own SMS provider (Odoo's SMS module requires a Twilio or OVH integration). Sender ID and phone number formats are validated against the destination SMS provider's requirements during mapping. Brevo SMS content migrates as Odoo sms.sms body text.

Brevo tags stored as flat key-value labels on Contacts migrate as Odoo tags. We create the tag records in Odoo first (via the tag model's create API), then link them to the corresponding Contact records via mail.followers. The tag name is the dedupe key; tags with the same name across different Brevo lists are merged in Odoo. Tags with no contact assignments are still created but flagged in the reconciliation report.

Brevo dynamic segments defined by filter conditions (e.g., 'contacts with city = London AND opened email in last 30 days') do not have a direct Odoo equivalent because Odoo segments are static groups updated manually or via a scheduled action. We export the segment filter logic as a written definition and recommend recreating it as an Odoo Automated Action that runs a search on the same criteria on a daily schedule. The segment name becomes an Odoo crm.tag group label.

Brevo transactional email event logs (delivered, bounced, complaint, deferred) are exported as a CSV with contact reference. In Odoo, these events are stored as mail.message records linked to the Contact partner record, with the event type in the message body and the timestamp preserved. We do not migrate webhook event data into Odoo's native tracking tables because Odoo does not expose a transactional email event API equivalent; the CSV is the system of record for delivery metrics post-migration.

Brevo user records (name, email, role) export for administrative reference. User provisioning in Odoo is a separate step — the customer creates Odoo users with matching email addresses before migration, and we match Brevo owner assignments by email. Any Brevo user without a matching Odoo User is flagged in the reconciliation report. Brevo marketing seat billing ($9/month) does not map to Odoo user records; Odoo CRM users are provisioned based on the customer's Odoo subscription tier.