CRM migration
Field-level mapping, validation, and rollback between Brevo Marketing Platform and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Brevo Marketing Platform
Source
Nutshell
Destination
Compatibility
6 of 10
objects map 1:1 between Brevo Marketing Platform and Nutshell.
Complexity
BStandard
Timeline
1-2 weeks
Overview
Moving from Brevo Marketing Platform to Nutshell is a CRM-first migration that requires extracting Brevo's contact records via API rather than the deprecated daily export, mapping Brevo's contact storage tier to Nutshell's unlimited contact model, and documenting Brevo automation workflows as a written inventory for manual rebuild. Brevo's multi-channel breadth (SMS, WhatsApp, chat) does not migrate; Nutshell's CRM plus email marketing stack replaces it on a per-seat pricing model that favors frequent senders over high-volume list owners. We do not migrate Brevo automation workflows, forms, landing pages, SMS credits, or email campaign statistics as reports. We extract campaign HTML content and recreate it as Nutshell email templates so the visual copy is preserved even if performance metrics do not transfer.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Brevo Marketing Platform object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Brevo Marketing Platform
Contact
Nutshell
Person
1:1Brevo Contacts map directly to Nutshell People. The contact email address serves as the dedupe key during import. Standard Brevo attributes (first name, last name, phone, city, country, date of birth) map to equivalent Nutshell Person fields. Custom attributes stored as Brevo contact properties migrate to Nutshell custom fields on Person. We extract via GET /contacts with cursor-based pagination (36,000 requests per hour limit applies); we do not use daily exports since that feature was deprecated May 30, 2025.
Brevo Marketing Platform
Company
Nutshell
Company
1:1Brevo Companies map to Nutshell Companies with a 1:1 relationship. The Brevo company domain becomes the Company Website field and is used as a secondary dedupe signal alongside email domain matching. We export Companies first so that the Nutshell Person-Company link (the 'Works at' relationship) is satisfied at the moment of Person insert, avoiding orphaned person records.
Brevo Marketing Platform
Deal
Nutshell
Deal
1:1Brevo Deals map to Nutshell Deals with pipeline and stage preserved. The Brevo dealstage property maps to a Nutshell Stage that we configure in the destination account before migration. Closed-Lost and Closed-Won reasons from Brevo custom properties map to Nutshell custom fields on Deal. We export Deals via the CRM Deals API or CSV from the Brevo UI.
Brevo Marketing Platform
Pipeline and Stage
Nutshell
Stage (configuration)
lossyBrevo pipelines (up to multiple per account on Standard/Professional/Enterprise) map to Nutshell Stage definitions. Each Brevo pipeline becomes a separate Nutshell Stage set. Custom stage names, stage order, and stage probabilities migrate as Nutshell stage configuration before Deal import begins. We use the CRM API to export pipeline configuration.
Brevo Marketing Platform
Tag
Nutshell
Tag
1:1Brevo tags (flat key-value labels on Contacts) map to Nutshell CRM tags. Tags are exported as a list per contact and inserted as tag values on the corresponding Nutshell Person record. Tag names with spaces or special characters are normalized to Nutshell's tag format during transform.
Brevo Marketing Platform
Automation Workflow (Journey)
Nutshell
Written inventory (no code migration)
lossyBrevo automation workflows (Journeys) are documented as a written inventory capturing the trigger event, condition branches, delay steps, and action types (send email, update property, assign owner, etc.). Brevo's new automation editor (2024) has a separate migration path where partially migratable workflows mark unsupported steps as inactive rather than failing outright. We audit every workflow post-transfer and flag any inactive steps so the customer can rebuild manually in Nutshell or document for a workflow implementation partner. We do not migrate workflow logic as executable code to Nutshell.
Brevo Marketing Platform
Email Campaign
Nutshell
Email Template
1:1Brevo email campaign content (subject, sender, HTML content blocks) exports as HTML and recreates as Nutshell email templates. Campaign statistics (open rate, click rate, bounce rate) do not migrate as reports — we preserve them in a written campaign performance summary document. Nutshell's email template model supports the HTML content and merge field structure from Brevo campaigns.
Brevo Marketing Platform
SMS Campaign
Nutshell
Not migrated
lossyBrevo SMS campaigns export with the same logic as email campaigns, but Nutshell does not include native SMS delivery. SMS campaigns are documented in the campaign inventory with sender ID and credit consumption noted. The customer must provision a separate SMS account (Brevo SMS credits do not transfer) and recreate SMS campaigns in a dedicated SMS platform if SMS continues to be required.
Brevo Marketing Platform
Custom Object
Nutshell
Related record or custom field
lossyBrevo Custom Objects are only available on Enterprise or Pro plans and can only be created via API. If the source account has Custom Objects, we map them to Nutshell in one of three ways depending on data structure: (1) as custom fields on the related Person or Company record, (2) as a separate Nutshell custom object equivalent (via third-party integration or related record table), or (3) as a JSON blob in a notes field with a schema reference. The customer selects the strategy during scoping.
Brevo Marketing Platform
User (Owner)
Nutshell
Team Member
1:1Brevo Owners map to Nutshell Team Members by email address match. Brevo seat assignments ($9/month per marketing seat) are a billing configuration rather than a data migration artifact. We export all Owner records referenced on Contacts, Companies, and Deals, resolve them to Nutshell Team Members, and flag any Owners without a matching Nutshell account for the customer's admin to provision before Deal import begins.
| Brevo Marketing Platform | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline and Stage | Stage (configuration)lossy | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Automation Workflow (Journey) | Written inventory (no code migration)lossy | Fully supported | |
| Email Campaign | Email Template1:1 | Fully supported | |
| SMS Campaign | Not migratedlossy | Fully supported | |
| Custom Object | Related record or custom fieldlossy | Fully supported | |
| User (Owner) | Team Member1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Brevo Marketing Platform gotchas
Daily exports deprecated since May 30th, 2025
Contact storage limits tied to email volume tier, not plan name
Custom Objects only available on Enterprise or Pro plans
Automation workflow migration marks unsupported steps inactive
List IDs can change unexpectedly on Brevo's side
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and scoping
We audit the source Brevo account across tier (Free/Starter/Standard/Professional/Enterprise), contact count, company count, deal count and pipeline structure, active automation count, custom object schemas (if Enterprise/Pro), email volume tier (which determines storage limits), and any webhook or integration footprint relying on daily exports. We confirm the export method (Contacts API vs Customer Data Platform) based on account tier. The discovery output is a written migration scope and a Nutshell plan recommendation based on team size and feature requirements.
Nutshell destination schema setup
We configure the Nutshell destination account before data import begins. This includes creating any custom fields on Person, Company, and Deal that correspond to Brevo custom attributes; configuring deal stages and pipeline structure to match the Brevo pipeline model; setting tag taxonomy to accommodate Brevo tag values; and verifying the team member roster against Brevo Owner records. Custom fields and stage configuration are validated in the Nutshell UI before import begins.
Brevo data extraction via API
We extract Brevo data using the Contacts API with cursor-based pagination for contacts (avoiding the deprecated daily export), the Companies API for company records, and the CRM Deals API or UI CSV export for deal records. We extract tag assignments per contact and automation workflow definitions as structured text. For each extraction, we validate record counts against the source account's tier storage limits and flag any discrepancy between the exported count and the expected contact count based on the email volume tier. Brevo's API rate limits (36,000 requests per hour on contact endpoints) govern the extraction pacing for large datasets.
CRM record migration in dependency order
We import into Nutshell in record-dependency order: Companies first (the foundational org records), then People with the Company link resolved, then Deals with the Person link and Stage configuration satisfied. Each phase emits a row-count reconciliation report showing records attempted, records imported, and records rejected with error reasons. Tag assignments insert in a follow-on pass using Nutshell's tag API once Person records have stable IDs. Owner references resolve via email match against the Nutshell team member roster; any unresolved owners go to a reconciliation queue for the customer's admin to provision before deal import resumes.
Automation inventory and campaign template handoff
We document every Brevo automation workflow as a written inventory capturing the trigger event, condition logic, delay steps, and action sequence. This document is delivered to the customer's admin team as the basis for manual rebuild in Nutshell's workflow builder or for engagement with a Nutshell implementation partner. Email campaign HTML content exports from Brevo and recreates as Nutshell email templates. SMS campaigns and multi-channel automations (WhatsApp, chat) are excluded from migration scope and noted in the handoff document with the recommendation to provision separate SMS capability if needed.
Sandbox migration and production cutover
For migrations exceeding 5,000 records, we run a sandbox migration into a Nutshell test environment first. The customer's team spot-checks 25-50 records across Person, Company, and Deal objects for field-level accuracy and signs off before production migration begins. At cutover, we freeze Brevo write access, run a final delta extraction of any records modified during the migration window, import the delta into Nutshell, and mark Nutshell as the system of record. We deliver the automation inventory and campaign template summary, then support a three-day hypercare window for reconciliation issues. Nutshell's complimentary migration assistance (CSV upload, 24-48 business hours) operates in parallel for basic record imports and can supplement our migration for customers who want Nutshell's team to handle the CSV ingestion directly.
Platform deep dives
Brevo Marketing Platform
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Brevo Marketing Platform and Nutshell.
Object compatibility
3 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Brevo Marketing Platform: Documented per-endpoint quotas; general rate limits apply per org.
Data volume sensitivity
Brevo Marketing Platform exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Brevo Marketing Platform to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Brevo Marketing Platform to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Brevo Marketing Platform
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.