CRM migration

Migrate from Brevo Marketing Platform to Nutshell

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 logo

Brevo Marketing Platform

Source

Nutshell

Destination

Nutshell logo

Compatibility

60%

6 of 10

objects map 1:1 between Brevo Marketing Platform and Nutshell.

Complexity

BStandard

Timeline

1-2 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Brevo Marketing Platform logo

Brevo Marketing Platform

What's pushing teams away

  • Advanced analytics and attribution reporting are described as limited compared to enterprise tools, frustrating data-driven marketers.
  • Template customization is minimal; users wanting highly branded or complex email layouts frequently outgrow what Brevo offers.
  • Customer support response times are cited as slow by multiple reviewers, particularly on lower tiers.
  • The learning curve for complex automation workflows is steep, and in-app guidance for advanced setups is minimal.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Brevo Marketing Platform objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Brevo 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

maps to

Nutshell

Company

1:1
Fully supported

Brevo 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

maps to

Nutshell

Deal

1:1
Fully supported

Brevo 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

maps to

Nutshell

Stage (configuration)

lossy
Fully supported

Brevo 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

maps to

Nutshell

Tag

1:1
Fully supported

Brevo 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)

maps to

Nutshell

Written inventory (no code migration)

lossy
Fully supported

Brevo 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

maps to

Nutshell

Email Template

1:1
Fully supported

Brevo 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

maps to

Nutshell

Not migrated

lossy
Fully supported

Brevo 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

maps to

Nutshell

Related record or custom field

lossy
Fully supported

Brevo 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)

maps to

Nutshell

Team Member

1:1
Fully supported

Brevo 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.

Gotchas + challenges

What specifically takes care here

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 logo

Brevo Marketing Platform gotchas

High

Daily exports deprecated since May 30th, 2025

High

Contact storage limits tied to email volume tier, not plan name

High

Custom Objects only available on Enterprise or Pro plans

Medium

Automation workflow migration marks unsupported steps inactive

Medium

List IDs can change unexpectedly on Brevo's side

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Daily exports deprecated May 30, 2025

    Brevo removed the daily export feature in May 2025. Any integration relying on daily exports will stop working silently. We use the Contacts API (GET /contacts) with cursor-based pagination for contact extraction rather than the deprecated export path. The API limit for contact endpoints is 36,000 requests per hour, which requires pagination handling and batch chunking for large lists. We confirm the export method during scoping based on account tier — Enterprise accounts retain the Customer Data Platform as an alternative export path.

  • Contact storage limits tied to email volume tier, not plan name

    Brevo's maximum storable contacts depend on the email volume tier within the plan, not the plan name alone. Starter at 5K emails/month caps at 500 contacts; Starter at 20K emails/month allows unlimited contacts. When migrating a large contact list out of Brevo, we verify the exported count against the source tier's storage limit. Contacts that Brevo did not store (queued beyond the limit) are not in the export and therefore do not appear in Nutshell. We surface this discrepancy in the scoping report before migration begins.

  • Custom Objects only on Enterprise or Pro plans

    Brevo Custom Object schemas can only be defined and populated via API on Enterprise or Pro accounts. Starter and Standard accounts cannot create or receive custom object data. If the source account is on a lower tier, any custom object migration scope is excluded. We confirm the source account tier during scoping and map any custom object records to Nutshell custom fields or related records as a configuration step rather than a native custom object import.

  • Brevo automation editor migration deactivates unsupported steps

    Brevo's new automation editor (2024) has a separate migration path where partially migratable workflows mark unsupported steps as inactive rather than failing outright. Workflows that appear migrated in Brevo's own migration tool may have steps that do not fire after the migration completes. We audit every Brevo automation pre-migration and document the full sequence logic (trigger, conditions, delays, actions) as a written inventory for the customer to rebuild manually in Nutshell. We do not auto-recreate Brevo automation logic in Nutshell.

  • Brevo API rate limits affect export speed for large datasets

    Brevo's API enforces rate limits including 36,000 requests per hour for contact endpoints (/v3/contacts/{...}) and 300 requests per hour for SMTP endpoints. For migrations exceeding 50,000 contacts, we paginate through the API in batches with exponential backoff on 429 responses. The daily export deprecation means large exports cannot be parallelized via the deprecated path, increasing reliance on API pagination and extending the export timeline proportionally for very large contact databases.

Migration approach

Six steps for a successful Brevo Marketing Platform to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Brevo Marketing Platform logo

Brevo Marketing Platform

Source

Strengths

  • Free plan with 300 emails/day and full transactional API access — best-in-class for low-volume use cases.
  • Per-email-volume pricing model instead of per-contact, protecting costs for large lists.
  • Includes CRM (Contacts, Companies, Deals) in all paid tiers at no extra charge.
  • Multi-channel delivery (email, SMS, WhatsApp, chat) from a single platform with shared contact records.
  • Bulk upsert API for Contacts and Custom Objects supports asynchronous batch processing.

Weaknesses

  • Daily export feature deprecated as of May 2025, limiting programmatic data pull options for non-Enterprise accounts.
  • Custom Objects require Enterprise or Pro plan — a common blocker for teams that outgrow Starter/Standard but have custom data.
  • Automation workflows have a separate migration path with potential for unsupported steps to become inactive.
  • Contact storage limits are tied to email volume tier, not plan name — easy to hit limits unexpectedly when importing large lists.
  • Limited email template variety and advanced template customization compared to dedicated email design tools.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Brevo Marketing Platform and Nutshell.

  • Object compatibility

    B

    3 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Brevo Marketing Platform: Documented per-endpoint quotas; general rate limits apply per org.

  • Data volume sensitivity

    A

    Brevo Marketing Platform exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Brevo Marketing Platform to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Brevo Marketing Platform to Nutshell data migrations

Answers to the questions buyers ask most during Brevo Marketing Platform to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Migrations under 10,000 contacts and 2,000 deals with no custom objects land between one and two weeks. Migrations with custom object schemas (Enterprise/Pro source accounts), multi-pipeline deal structures, or large tag sets requiring manual mapping extend to three to four weeks because of schema design time and custom field configuration. Brevo API pagination for large contact lists (over 50,000 contacts) also extends the extraction phase proportionally. Nutshell's complimentary migration assistance (24-48 business hours for CSV uploads) runs in parallel for basic record ingestion and does not replace the pre-migration discovery and schema design work.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Brevo Marketing Platform.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day