Mautic to Salesforce migration
We migrate Contacts, Companies, Campaigns, Segments, Stages, Tags, and Custom Objects from Mautic into Salesforce with the v6 export failure worked around via direct database access, lifecycle stage split applied against the Lead or Contact model, and every Mautic Points value preserved as a custom Salesforce lead score field.
FlitStack AI migrates lead or contacts, accounts, campaign + campaignmembers, campaigns and lead status or custom fields from Mautic to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 5-7 weeks.

What moves from Mautic to Salesforce?
Moving from Mautic to Salesforce is a migration from a standalone marketing-first platform to a CRM-first ecosystem.
Read the full summary
Mautic organizes data around Contacts with a built-in CRM layer; Salesforce separates Leads and Contacts and expects Accounts as the organizational parent. We resolve that structural difference during scoping by defining the lifecycle-stage-to-Lead-or-Contact split rule before any data moves. We bypass Mautic v6's broken CSV export by reading contact and company data directly from the MySQL/MariaDB database, work around the index-per-table limits that throttle large contact databases, and resolve the Custom Object relationship gaps by accessing junction tables directly. Campaigns and Segments migrate as Salesforce Campaigns with membership history preserved; Stages and Points map to Salesforce Lead Status and a custom lead score field. Workflows, Sequences, landing pages, and Reports do not migrate; we deliver a written inventory of every active automation and page that requires rebuild in Salesforce Flow, Experience Cloud, or a dedicated marketing implementation partner.
Contact → Lead or Contact (split required)
Mautic Contacts with lifecycle stage of subscriber, lead, or marketing qualified lead map to Salesforce Lead.
How it maps
Lifecycle stage of sales qualified lead, opportunity, customer, evangelist, or other maps to Salesforce Contact tied to an Account. We compute the split using Mautic's stage and lead_status properties at migration time, preserve the original Mautic lifecycle stage in a custom field stage__c on both Lead and Contact for audit, and set the Salesforce Lead Status picklist to a value derived from the Mautic stage name. All custom contact fields migrate as typed Salesforce fields with __c suffixes.
Company → Account
Mautic Company records map directly to Salesforce Account.
How it maps
The company domain maps to the Account Website field and serves as the dedupe key during import. We resolve Mautic's many-to-one contact-to-company relationship by creating Account first, then setting AccountId on each Contact at insert time. Any company phone, industry, revenue, and address fields map to the equivalent Account fields.
Campaign → Campaign + CampaignMember
Mautic Campaign definitions (name, description, start and end dates, campaign type) map to Salesforce Campaign records.
How it maps
Campaign membership (which Contacts entered which Campaigns and when) migrates as Salesforce CampaignMember records linked by CampaignId and ContactId or LeadId. The CampaignMember Status field maps from Mautic's campaign membership status. We resolve the Contact-to-Campaign membership through the Mautic_leads_campaign_leads junction table accessed directly from the database.
Segment → Campaign (informational)
Mautic Segments are dynamic contact lists filtered by field values, tags, and behavioral conditions.
How it maps
We export the segment filter definitions as structured JSON and attach them to a Salesforce Campaign record's description field. The segment membership itself is not re-imported as CampaignMembers because Salesforce recalculates dynamic membership differently; the filter definition serves as a rebuild reference for the customer's admin to reconstruct as a Salesforce Campaign or a filtered Report.
Stage → Lead Status or custom field
Mautic Stages define contact lifecycle positions (Lead, MQL, Customer, etc.) and are stored in the Mautic lead stages table.
How it maps
We map each Mautic stage name to a Salesforce Lead Status picklist value (for Lead records) and preserve the full stage name in a custom text field stage__c on Contact for reference. If the destination Salesforce org uses a custom stage model for Contacts, we align to that instead.
Points → Lead Score (custom field)
Mautic's Points system scores contacts based on actions (page visits, form submissions, email opens, manual adjustments).
How it maps
We map the Mautic Points integer value to a custom Number field on the Salesforce Lead or Contact record named lead_score__c. Point Groups (thresholds that trigger stage changes) are documented as Salesforce Flow entry conditions or assignment rules for the customer's admin to rebuild.
- ContactLead or Contactsplit
- CompanyAccount1:1
- CampaignCampaign1:1
- SegmentCampaigntransformed
- StageLead Status or custom field1:1
- PointsLead Scoretransformed
+ 7 more in the mapping below
How Mautic and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Mautic | Salesforce |
|---|---|---|
| Architecture model | Marketing-first standalone platform with a built-in CRM layer | CRM-first ecosystem with dedicated Marketing Cloud add-ons for automation |
| Prospect model | Single Contact object with lifecycle stage and point scoring | Separate Lead and Contact objects requiring explicit conversion |
| API access | Open REST API on all editions including Community | REST and Bulk API available on Enterprise, Unlimited, Developer, Performance editions only |
| Per-contact pricing | Zero licensing cost; infrastructure and support are the only costs | Per-user model; storage billed org-wide above 10 GB on most editions |
| Multi-channel scope | Email first, extendable via plugins and APIs for SMS and push | Email, SMS, WhatsApp, and Ads through Marketing Cloud; Sales Cloud focuses on sales workflow |
| Self-hosting | Full server ownership requiring ongoing patching, cron, and DB management | Fully managed SaaS with SLA-backed uptime on all paid editions |
| Upgrade risk | Major version upgrades frequently break third-party plugins without error logging | Salesforce releases three seasonal updates per year with pre-release validation sandboxes |
What to watch for in a Mautic to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Mautic v6 CSV export fails silently on large datasets
Mautic 6.0.0's CSV export function queues the file for processing but never delivers it via email and provides no error output in Apache or Mautic logs.
How we handle it
We handle this by bypassing the built-in export entirely: we pull contact, company, campaign membership, and custom object data directly from the MySQL/MariaDB database using authenticated read access, or we call the REST API in batched requests with pagination handling. This ensures a reliable export regardless of the export queue failure. Before accessing the database, we profile index usage to flag any tables approaching MySQL's 64-index limit and coordinate with the customer to archive or restructure fields if needed.
Lead conversion workflow has no Mautic equivalent
Mautic uses a single Contact object with a lifecycle stage property to track prospects through the funnel.
How we handle it
Salesforce separates unqualified prospects into Leads and qualified buyers into Contacts attached to Accounts, with an explicit Convert action. We define the Lead-versus-Contact split rule during scoping based on the customer's Mautic lifecycle stage matrix, apply it as the first transform during migration, and preserve the original lifecycle stage in a custom field on both Lead and Contact for audit. Migrations that skip this design step end up with Contacts that have no Account (orphaned) or Leads that should have been converted on day one.
Mautic Custom Object Relationships API is non-functional
Mautic's Custom Objects support relationships between object types, but the REST API endpoint for creating relationship records is documented as broken in community reports from 2022.
How we handle it
We handle this by accessing the relationship data through the MySQL/MariaDB database schema directly, reading the junction table records (mautic_custom_object_relationship or equivalent), and mapping them to Salesforce lookup or junction objects during the custom object migration. This requires schema profiling of the Mautic database before migration to identify the correct junction table structure.
Mautic plugin and upgrade failures leave no diagnostic trail
Mautic 5 to 5.0.2 upgrades can fail mid-process without writing any errors to the Apache error log or Mautic's internal log file, leaving no diagnostic trail.
How we handle it
Additionally, Mautic 4 to 5 upgrades break third-party plugins without pre-upgrade compatibility validation. We handle this by taking a full filesystem and database snapshot of the source instance before any migration attempt, enabling us to restore the exact pre-migration state if the source instance encounters issues during scoping. The migration itself proceeds independently of the source Mautic upgrade path by reading directly from the live database or API.
Salesforce API access requires Enterprise or higher edition
Mautic's REST API is available on all editions including Community.
How we handle it
Salesforce's REST and Bulk API access is limited to Enterprise Edition, Unlimited Edition, Developer Edition, and Performance Edition. If the destination Salesforce org is on Professional, Group, or Essentials edition, API access for data migration is not available and the customer must upgrade before migration can proceed. We confirm the destination edition during discovery and flag any edition mismatch before signing off on the migration scope.
How the migration runs
Discovery and source audit
We audit the source Mautic instance across version (v4, v5, or v6), hosting model (self-hosted or Mautic Cloud), contact volume, custom field count, custom object count and their relationship structures, campaign count and membership volumes, segment filter definitions, active user count, and any installed plugins with Salesforce sync configurations.
What this step covers
We confirm the destination Salesforce edition (must be Enterprise or higher for REST/Bulk API access) and identify any custom objects or junction tables in the Mautic MySQL schema that require direct database access. The discovery output is a written migration scope with object inventory, estimated row counts per object, and a confirmed Lead-versus-Contact split rule.
Source data extraction bypassing v6 export
We extract contact, company, campaign membership, stage, points, tag, custom object, and user data directly from the Mautic MySQL/MariaDB database using authenticated read access, or through batched REST API calls with pagination.
What this step covers
We bypass the broken Mautic v6 CSV export entirely. For custom object relationships, we read junction table records directly from the database schema and reconstruct the relationship graph for Salesforce. We profile the database for index usage and flag any tables approaching MySQL's 64-index limit before extraction. We take a full filesystem and database snapshot before any extraction to enable rollback of the source instance if needed.
Destination schema design and provisioning
We design the Salesforce destination schema in a Sandbox org before production migration.
What this step covers
This includes provisioning custom objects with __c API names, custom fields with type-mapped Salesforce field types, Record Types for any Mautic pipeline equivalents, Sales Processes for stage whitelists, and page layouts per Record Type. We create the lead_score__c numeric field for Mautic Points, the stage__c text field for original lifecycle stage preservation, and any multi-select picklists for Mautic Tags exceeding 150 unique values. Schema is deployed via Salesforce Metadata API or change set into the Sandbox first for validation.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox using production-like data volume.
What this step covers
The customer's RevOps lead reconciles record counts (Leads in, Contacts in, Accounts in, Campaigns in, CampaignMembers in, custom objects in), spot-checks 25-50 random records against the Mautic source, and validates the Lead-Contact split rule against the lifecycle stage matrix. Any field mapping corrections, custom object schema adjustments, or split rule refinements happen here in Sandbox before production migration begins. We also validate that Salesforce validation rules and field-level security do not reject records during the Sandbox run.
User provisioning and owner reconciliation
We extract every distinct Mautic user referenced on Contact, Company, Campaign, and Engagement records and match by email against the Salesforce destination org's User table.
What this step covers
Users without a matching Salesforce User go to a reconciliation queue. The customer's Salesforce admin provisions any missing Users (active or inactive depending on whether the original Mautic user is still active) before production migration. OwnerId references on Contacts, Leads, Accounts, Opportunities, and Campaigns require resolved Users before record insert can proceed.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Mautic Companies), Leads and Contacts (with the lifecycle stage split applied and AccountId resolved on Contacts), Campaigns (with campaign definitions and dates), CampaignMembers (linked by resolved LeadId and ContactId), custom objects (with lookup relationships resolved to Salesforce record IDs), engagement history via Bulk API 2.0 (Tasks, Events, EmailMessages, Notes), Assets as ContentDocument records, and Tags as multi-select picklists or custom fields.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. We use Bulk API 2.0 with batch chunking, parent-record lookup resolution, and exponential backoff on API limit responses for activity history.
Cutover, delta sync, and rebuild handoff
We freeze Mautic writes during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.
What this step covers
We deliver the automation and landing page inventory document listing every Mautic Workflow, Sequence, landing page, and report with a recommended Salesforce equivalent (Salesforce Flow, Experience Cloud, Marketing Cloud Landing Pages, or a CMS partner). We support a one-week hypercare window for reconciliation issues. We do not rebuild Mautic Workflows as Salesforce Flow inside the migration scope; that is a separate engagement.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with contact volume, custom object count, and the scope of automation rebuild documentation. Mautic's infrastructure costs stop when the self-hosted instance is decommissioned. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Mautic to Salesforce →Why teams move from Mautic to Salesforce
- Self-hosting Mautic requires dedicated server administration, security patching, and cron job management that marketing teams lack the bandwidth to sustain. As organizations grow, the infrastructure burden grows with it, and the zero-licensing-cost advantage is offset by hosting spend and opportunity cost. Salesforce Sales Cloud is fully managed SaaS with SLA-backed uptime, eliminating the server and patch management that drives Mautic teams to seek alternatives.
- Mautic's MySQL/MariaDB column-size limits and index-per-table restrictions (64 indexes) throttle performance at contact counts above 500,000. Organizations running high-volume marketing databases hit slow query times, failed inserts, and expensive database restructuring that forces the upgrade conversation. Salesforce's cloud-native data layer handles millions of records without the same schema constraints, eliminating the performance ceiling that self-hosted Mautic imposes.
- Major version upgrades in Mautic (4 to 5 to 6) break third-party plugins and custom code without pre-upgrade compatibility validation or meaningful error output when failures occur. Organizations that rely on Mautic's plugin ecosystem for CRM sync, SMS, or advanced segmentation are effectively locked out of upgrading until all plugins are audited and rewritten. Salesforce's three seasonal updates per year include pre-release sandboxes and release notes, removing the upgrade paralysis that Mautic users face.
- Mautic's built-in CRM layer lacks the pipeline depth, territory management, forecasting, and revenue intelligence features that enterprise sales teams require. Organizations that start with Mautic for marketing automation and then need a full-featured CRM often consolidate onto Salesforce because the two-system integration overhead (bidirectional sync, duplicate management, attribution gaps) exceeds the cost of a unified platform. Salesforce Sales Cloud from Professional tier includes advanced forecasting, opportunity stages, and CPQ-ready data models that Mautic's built-in CRM does not match.
- Enterprise organizations that standardize on Salesforce for sales and service need marketing automation to live inside the same ecosystem for attribution, account-based targeting, and revenue reporting. The Mautic-Salesforce bidirectional sync via Zapier or the native Mautic plugin is a point-to-point integration that breaks on Mautic upgrades, drifts on schema changes, and provides no single source of truth. Consolidating marketing automation into Salesforce Marketing Cloud or operating Mautic as a data feeder to Salesforce removes the integration fragility and gives revenue operations a unified view.
Questions, answered
Mautic to Salesforce migration questions
How long does a Mautic to Salesforce migration take?
Most migrations land between five and seven weeks for accounts under 50,000 Contacts with no custom objects, standard field mapping, and campaign membership preserved. Migrations exceeding 500,000 Contacts, hitting MySQL index limits on the source, requiring custom object schema with lookup relationships, or preserving large campaign membership histories move to ten to sixteen weeks because of database profiling, junction table extraction, Bulk API time for engagement history, and Sandbox validation cycles.
Do Mautic Workflows, Sequences, and Forms migrate to Salesforce?
No. Mautic Workflows and Salesforce Flow are structurally different automation models with different trigger types, action libraries, and state management. Sequences (sales engagement cadences) have no direct Salesforce Sales Cloud equivalent. Forms and Landing Pages do not migrate because Salesforce Sales Cloud does not have a native landing page builder; Salesforce Experience Cloud or Marketing Cloud Landing Pages are the standard replacements. We do not migrate these as code. We deliver a written inventory of every active Mautic Workflow, Sequence, form, and landing page with its trigger, conditions, actions, and a recommended Salesforce Flow or Experience Cloud equivalent. The customer's admin or a marketing implementation partner rebuilds them post-migration.
Can we keep Mautic for marketing automation while moving sales to Salesforce?
Yes. A hybrid stack is a common pattern for organizations that want to keep Mautic's marketing automation capabilities while adopting Salesforce Sales Cloud for the sales process. In this pattern, Mautic continues to handle email campaigns, segments, and lead scoring; Salesforce handles Lead management from Mautic lead import onward. We configure a Mautic-to-Salesforce data flow (via Zapier, native Mautic Salesforce plugin, or a custom API integration) during migration so that new Mautic Contacts flow into Salesforce as Leads. The customer continues operating Mautic while the sales team works in Salesforce.
Do we lose historical campaign membership and engagement data?
No for campaign membership. We preserve Mautic campaign membership history as Salesforce CampaignMember records linked by CampaignId and ContactId or LeadId, accessed via the Mautic junction tables in the database. Partial for engagement history. Mautic's built-in CRM stores engagement records (sends, opens, clicks, page visits) differently from a dedicated CRM; we export what is stored as structured records and migrate it as Salesforce Task and EmailMessage records where the data model allows. Asset metadata migrates as Salesforce ContentDocument. Landing page content exports as structured JSON for rebuild in a CMS. Reports and Forms do not migrate.
What happens to Mautic's Points and Stages during migration?
Mautic Points migrate to a custom Number field called lead_score__c on the Salesforce Lead or Contact record. Point Groups (thresholds that trigger stage changes) are documented as Salesforce Flow entry conditions or assignment rules for the customer's admin to rebuild. Mautic Stages migrate to Salesforce Lead Status (for Lead records) and a custom text field stage__c on Contact preserving the original Mautic stage name. If the destination org uses a custom lifecycle stage model, we align to that during schema design.
What Salesforce edition is required for migration?
Salesforce Enterprise Edition, Unlimited Edition, Developer Edition, or Performance Edition is required for REST and Bulk API access. Professional, Group, and Essentials editions do not expose API endpoints needed for data migration. We confirm the destination edition during discovery and flag any edition mismatch before signing off on the migration scope. If the customer needs to upgrade from a lower edition, we identify the minimum edition required based on the migration scope and recommend the upgrade path before migration begins.
Can FlitStack AI also migrate to Salesforce Marketing Cloud instead of Sales Cloud?
Yes. We handle migrations from Mautic to Salesforce Marketing Cloud as a parallel scope. Marketing Cloud uses a different data model (Data Extensions, Contacts, Journeys, Automation Studio) compared to Sales Cloud (Leads, Contacts, Accounts, Opportunities). The mapping differs significantly: Mautic Contacts map to Marketing Cloud Contacts or Data Extension records, Mautic Campaigns map to Marketing Cloud Journeys, and Mautic Segments map to Marketing Cloud Audience Builder filters. We confirm whether the destination is Sales Cloud, Marketing Cloud, or both during discovery and design the migration scope accordingly.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Podio to SalesforceMapping · history · rollbackBlinQ to SalesforceMapping · history · rollbackAdobe Campaign to SalesforceMapping · history · rollbackNimble CRM to SalesforceMapping · history · rollbackEspoCRM to SalesforceMapping · history · rollbackTeamleader to SalesforceMapping · history · rollback Mautic to HubSpotMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Mautic to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote