CRM migration
Field-level mapping, validation, and rollback between Mautic and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Mautic
Source
Nutshell
Destination
Compatibility
4 of 9
objects map 1:1 between Mautic and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Mautic to Nutshell is a migration from a self-hosted marketing automation platform built around campaigns and segments to a SaaS CRM built around pipelines and engagement tracking. Mautic organizes data around Contacts, Companies, Campaigns, Segments, Stages, Points, Tags, and Custom Objects; Nutshell uses Leads, Contacts, Accounts, Opportunities, Activities, and custom fields. We extract contact and company data directly from the Mautic database or API rather than relying on Mautic's built-in CSV export, which silently fails in v6.0.0. We map Mautic Stages to Nutshell lifecycle or pipeline positions, Mautic Tags to Nutshell custom fields, and Mautic Companies to Nutshell Accounts with multi-contact relationship preservation. Campaign and segment definitions export as written documentation for your admin to rebuild in Nutshell's automation tools. We do not migrate Workflows, Forms, Landing Pages, Assets, or Custom Objects as code; these require post-migration rebuild in Nutshell or a separate implementation engagement.
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 Mautic 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.
Mautic
Contact
Nutshell
Lead or Contact
1:manyMautic Contacts with no associated Company map to Nutshell Lead. Mautic Contacts with an associated Company map to Nutshell Contact tied to an Account. We use Mautic's stage and lifecycle_status properties to determine qualification, and preserve the original Mautic stage in a custom field mautic_stage__c for audit. Tag membership migrates to custom multi-select fields or list membership based on customer preference.
Mautic
Company
Nutshell
Account
1:1Mautic Company records map directly to Nutshell Account. The company name becomes the Account name, and address, industry, revenue, and website fields map to their Nutshell equivalents. Mautic's many-to-one contact-to-company relationship becomes Nutshell's one-to-many Account-to-Contact relationship, with multiple Contact records linked to the same Account after migration.
Mautic
Campaign
Nutshell
Automation (written documentation)
lossyMautic Campaigns are automation workflows with trigger conditions, action steps, and contact membership. Nutshell's automation model is scoped to CRM records and pipeline events rather than campaign-based contact journeys. We export campaign definitions including trigger types, step sequences, and membership criteria as a written document for the customer's admin to rebuild in Nutshell Automation or email sequences. The campaign membership itself is preserved as tag and segment membership on the contact records.
Mautic
Segment
Nutshell
List or Saved Filter
lossyMautic Segments are dynamic contact lists filtered by field values, tags, behaviors, or combinations. We export the segment filter logic as a written definition specifying each filter condition, operator, and value. The customer recreates the segment in Nutshell as a List or Saved Filter using the same logic. Segment membership contact IDs are preserved as tag assignments so the admin can validate the rebuilt segment against the original membership.
Mautic
Stage
Nutshell
Lifecycle Stage or Pipeline Position
lossyMautic Stages define contact lifecycle positions (Lead, MQL, SQL, Customer). We map stage names directly to Nutshell lifecycle stages if the destination uses a comparable model, or to pipeline stage positions on the Account/Contact records. Stage sequence order is preserved in the mapping documentation.
Mautic
Tag
Nutshell
Custom Field (multi-select)
1:1Mautic Tags are flat string labels applied to contacts and other objects. We export all unique tag strings and map them to Nutshell custom multi-select fields. Tag-based segmentation logic transfers as tag assignments on each contact record. Tags that represent categorical data (industry, product interest, account type) are mapped to dedicated custom fields rather than a catch-all tag field.
Mautic
Custom Contact Field
Nutshell
Custom Field
1:1Mautic custom contact fields (user-defined properties beyond the standard schema) map to Nutshell custom fields with type matching: text to text, number to number, date to date, boolean to checkbox, and picklist to dropdown. Field alias from Mautic becomes the field name in Nutshell. We flag any fields approaching Mautic's ~150 field ceiling so the customer knows which fields were constrained before migration.
Mautic
User
Nutshell
User
1:1Mautic User records (internal user accounts with roles and permissions) map to Nutshell User records. We extract user email, first name, last name, and role. Password hashes do not transfer; we document the user list so the customer's admin provisions new Nutshell login credentials. Role and permission configurations map to Nutshell team roles as documented in the migration output.
Mautic
Category
Nutshell
List or Tag Group
lossyMautic Categories group assets, campaigns, emails, and contacts into hierarchical folders. We export the category hierarchy and map top-level categories to Nutshell Lists or tag groups for the admin to assign during post-migration cleanup.
| Mautic | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Lead or Contact1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Campaign | Automation (written documentation)lossy | Fully supported | |
| Segment | List or Saved Filterlossy | Fully supported | |
| Stage | Lifecycle Stage or Pipeline Positionlossy | Fully supported | |
| Tag | Custom Field (multi-select)1:1 | Fully supported | |
| Custom Contact Field | Custom Field1:1 | Fully supported | |
| User | User1:1 | Fully supported | |
| Category | List or Tag Grouplossy | 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.
Mautic gotchas
Mautic v6 CSV export silently fails to deliver files
Mautic 4 to 5 upgrade breaks plugins without warning
MySQL/MariaDB index limits throttle large contact databases
Custom Object Relationships API is non-functional
Mautic 5 to 6 migration logs no errors on failure
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
Source audit and extraction method selection
We audit the source Mautic instance across version (v4, v5, or v6), database engine (MySQL or MariaDB), custom field count, segment definitions, campaign definitions, tag inventory, and installed plugin list. If the instance is v6 or exhibits the CSV export failure, we select direct database extraction as the primary method. If the instance is v4 or v5 with a working export, we use the REST API with batched pagination. We flag any plugins with known compatibility issues before proceeding.
Destination schema preparation
We configure the Nutshell destination before data extraction begins. This includes creating custom fields mapped to Mautic custom contact field names and types, configuring lifecycle stages or pipeline positions to match the Mautic stage hierarchy, and setting up lists or saved filters for segment reconstruction. Nutshell's API supports custom field creation; we use the Nutshell REST API to provision the schema in a pre-migration validation pass.
Data extraction from Mautic
For v6 instances or instances with CSV export failures, we extract contact and company records directly from the Mautic MySQL/MariaDB database using authenticated read access with batched queries to avoid locking. We extract standard fields, custom contact fields, company associations, tag assignments, and stage values in parallel passes. For v4/v5 instances with working exports, we use the REST API with offset pagination (500 records per page) and rate-limit handling to extract the same dataset.
Transform and load into Nutshell
We transform the extracted data in the migration staging layer. Mautic Contacts without an associated Company map to Nutshell Lead; contacts with an associated Company map to Nutshell Contact with AccountId resolved. We compute the Account record first so that Contact inserts succeed with the lookup. Custom field values map by name match; tag assignments map to the designated custom multi-select field. We use the Nutshell REST API for record inserts with batched requests and error logging per record.
Campaign and segment documentation
We export the Mautic campaign definitions (trigger types, step sequences, action configurations) and segment filter logic (field conditions, operators, values) as written JSON and structured text documents. Tag membership is preserved on contact records as tag values that reference the original segment names. The admin receives the campaign documentation and segment membership data as a handoff package for rebuild in Nutshell Automation.
Cutover and validation
We freeze Mautic writes during the final cutover window, run a delta extraction for any records modified since the initial extraction, and load the delta into Nutshell. We deliver a row-count reconciliation report comparing Mautic record counts against Nutshell record counts by type. We provide the campaign and segment documentation package. We do not rebuild Mautic workflows or automations in Nutshell; that work falls to the customer's admin or a Nutshell implementation partner.
Platform deep dives
Mautic
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Mautic and Nutshell.
Object compatibility
2 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
Mautic: Not publicly documented — enforced at the server level, not within Mautic software.
Data volume sensitivity
Mautic doesn't expose a bulk API — REST + parallelization used for high-volume runs.
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 Mautic to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Mautic 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 Mautic
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.