Migrate from Mautic to Salesforce Sales Cloud

Mautic Contacts with lifecycle stage of subscriber, lead, or marketing qualified lead map to Salesforce Lead. 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.

Mautic Company records map directly to Salesforce Account. 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.

Mautic Campaign definitions (name, description, start and end dates, campaign type) map to Salesforce Campaign records. 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.

Mautic Segments are dynamic contact lists filtered by field values, tags, and behavioral conditions. 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.

Mautic Stages define contact lifecycle positions (Lead, MQL, Customer, etc.) and are stored in the Mautic lead stages table. 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.

Mautic's Points system scores contacts based on actions (page visits, form submissions, email opens, manual adjustments). 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.

Mautic Tags are flat string labels applied to contacts and other objects. Tags with fewer than 150 unique values migrate to a Salesforce multi-select picklist on Contact or Lead. Tags exceeding 150 unique values migrate to a custom text field tag_list__c storing comma-separated values, or to Salesforce Topics with TopicAssignment records if the customer licenses the Topic model. Tag-based segmentation logic is preserved as a filter definition attached to the relevant Campaign or Report.

Mautic Custom Objects extend the data model beyond standard contacts and companies. Relationships between custom objects use junction tables in Mautic's MySQL schema (the Relationships API is documented as broken). We access the junction table records directly from the database, pre-create the destination Salesforce custom object schema with all custom fields and lookup relationships, then import the custom object records with foreign key references resolved to Salesforce record IDs at migration time. Custom object naming uses the __c suffix per Salesforce convention.

Mautic Assets are downloadable files (PDFs, guides, media) stored as binary blobs in the Mautic database or filesystem. We export asset metadata (filename, title, description, download count, storage path) and create Salesforce ContentDocument records with the file stored as ContentVersion. The asset's download URL is preserved as an external link on the ContentDocument if the Mautic instance remains accessible post-migration.

Mautic Landing Pages are standalone web pages with theme assignments and tracking configuration. We export page content, URL slugs, theme names, and form embedding configurations as a structured reference document. Landing pages do not migrate as functional pages because Salesforce does not have a native landing page builder in Sales Cloud. We recommend Salesforce Experience Cloud, Marketing Cloud Landing Pages, or a CMS partner (Contentful, Webflow) as the replacement, and we provide the content export in a format suitable for re-import.

Mautic Users map to Salesforce User records by email address match. We extract all Mautic user records including role names, role permissions, and ownership assignments during scoping. User provisioning in the destination Salesforce org is a separate manual step the customer's admin completes before record migration, because active Salesforce Users must exist before OwnerId references can be resolved on Contacts, Leads, Accounts, and Opportunities.

Mautic Categories group assets, campaigns, emails, and contacts into a hierarchical folder structure. We export the full category hierarchy as a JSON tree and reassign it to Salesforce Topics (Topic model) or to a custom text field category_path__c on each migrated record, depending on the destination org's data model complexity.

Mautic email engagement records (sends, opens, clicks, bounces) map to Salesforce EmailMessage records linked to a Task record on the contact or lead timeline. The email content, send timestamp, and engagement metrics (open count, click count) preserve as Salesforce fields. For Mautic emails linked to a Mautic Campaign, we create a Salesforce CampaignMember record if the contact maps to a Lead or Contact with a corresponding Salesforce Campaign.