Mautic to HubSpot migration
Moving from Mautic to HubSpot means swapping an open-source marketing automation platform with secondary CRM capabilities for HubSpot's CRM-first ecosystem where the CRM sits at the center of marketing, sales, and service. We map every Mautic contact, company, custom field, and engagement activity into HubSpot's contact record with lifecycle stages and deal pipelines preserved so your HubSpot reporting reflects the full customer journey from Mautic.
FlitStack AI migrates contacts, companies, static list / dynamic lists, campaign + workflows and marketing emails from Mautic to HubSpot, 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: 48–72 hours for under 50,000 records with standard object mapping.

What moves from Mautic to HubSpot?
Mautic was built as a marketing automation platform with a secondary CRM layer — contacts, companies, and point-based lead scoring sit alongside email campaigns, segments, and assets.
Read the full summary
HubSpot reverses this: the CRM is the core, with marketing automation, sales pipelines, and service tools built around it. This structural difference shapes every mapping decision during migration. We migrate Mautic contacts as HubSpot contacts, preserving the original create date, point score as a custom contact property, and engagement history as HubSpot engagements. Mautic companies map directly to HubSpot companies with parent-child hierarchies preserved via the parent company association. Custom fields created in Mautic become HubSpot custom properties — the field type (text, number, date, picklist) determines the HubSpot property type, and picklist values are mapped value-by-value. Mautic segments, however, have no direct HubSpot equivalent — HubSpot uses static lists and dynamic lists instead, which must be rebuilt manually after migration. Mautic email campaigns, marketing workflows, and assets cannot migrate; these require reconstruction in HubSpot's campaign and workflow builders. Mautic's point-based lead scoring transfers as a numeric custom property, giving your team a reference baseline for rebuilding HubSpot's native contact scoring model. We extract Mautic data via the REST API (or direct database query for self-hosted instances) and load into HubSpot using HubSpot's Bulk API for large record sets or the CRM API for targeted writes. A delta-pickup window captures in-flight changes during cutover, and a sample migration with field-level diff runs before the full commit.
Contact → Contact
Mautic contacts migrate directly to HubSpot contacts on a one-to-one basis.
How it maps
The original Mautic contact ID is preserved as a custom property (mautic_contact_id) on the HubSpot record, enabling traceability back to the source system and facilitating deduplication during delta-run comparisons. The HubSpot primary company association is set from the Mautic primary company link during migration to maintain the primary company relationship.
Company → Company
Mautic companies map one-to-one to HubSpot companies, preserving all standard company fields.
How it maps
Parent-child hierarchies in Mautic are preserved in HubSpot via the parent_company_id association. For contacts with multiple associated companies in Mautic, a primary company must be designated before migration proceeds, as HubSpot supports only a single primary company association per contact.
Segment → Static List / Dynamic List
Mautic segments lack a direct HubSpot equivalent and require transformation.
How it maps
Dynamic Mautic segments built with rule-based logic (contact property filters, behavioral triggers, time-decay conditions) must be recreated as HubSpot dynamic lists using HubSpot's filter-and-trigger builder. Static Mautic segments containing fixed contact memberships map to HubSpot static lists with contact IDs imported directly from the Mautic segment roster.
Campaign → Campaign + Workflow
Mautic campaigns are comprehensive marketing automation constructs containing triggers, decision branches, action sequences, and multi-step flows stored in the campaign table.
How it maps
HubSpot campaigns function only as email-focused membership trackers with no automation logic. All marketing automation must be rebuilt using HubSpot Workflows after migration; we export campaign definitions as JSON metadata to serve as a detailed rebuild reference for your HubSpot team.
Email Asset → Marketing Email
Mautic email templates and assets reside in a separate asset table using Twig-based dynamic content rendering.
How it maps
HubSpot employs its own email template format with drag-and-drop modules incompatible with Mautic's Twig syntax. Email assets require manual recreation; we deliver a comprehensive asset inventory export listing every Mautic email name, subject line, UTM parameters, and associated assets for recreation reference.
lead_points (scoring) → Custom Property: lead_points__c
Mautic's point-based lead scoring (lead_points field) has no native HubSpot equivalent.
How it maps
We preserve the numeric point value as a custom number property (lead_points__c) on the contact record, giving your team a baseline for rebuilding HubSpot's native predictive scoring model from the historical score.
- ContactContact1:1
- CompanyCompany1:1
- SegmentStatic Listtransformed
- CampaignCampaigntransformed
- Email AssetMarketing Emailtransformed
- lead_pointsCustom Property: lead_points__ctransformed
+ 6 more in the mapping below
How Mautic and HubSpot 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 | HubSpot |
|---|---|---|
| Core orientation | Mautic is a marketing automation platform with CRM capabilities; CRM is secondary to email campaigns, segments, and automation | HubSpot is a CRM-first platform; marketing automation, sales, and service orbit the CRM record |
| Lead scoring model | Mautic uses a point-based system (lead_points) where contacts accumulate numeric values from actions | HubSpot uses predictive lead scoring with a 0-100 scale calculated from property changes and engagement patterns |
| Contact-company relationship | Mautic supports N:N contact-to-company associations natively; a contact can belong to multiple companies | HubSpot contacts have a primary company association with secondary associations via contact properties or the Company Associations API |
| Pricing model | Mautic pricing is tied to infrastructure and email volume; no per-contact billing on self-hosted instances | HubSpot Starter begins at $15/seat/month plus contact-based pricing starting at 1,000 contacts |
| Campaign logic | Mautic campaigns are full marketing automation constructs with triggers, actions, and branching; stored in the campaign table | HubSpot campaigns are email-focused with simple membership tracking; full automation lives in Workflows |
| Deployment model | Mautic is open-source and self-hosted on your infrastructure (or Acquia-managed cloud); you control the server and database | HubSpot is SaaS-only; no self-hosted option; your data lives in HubSpot's multi-tenant environment |
| Data ownership | Mautic self-hosted gives full data ownership; database is on your servers and fully exportable | HubSpot data is vendor-hosted; export available via API or CSV but governed by HubSpot's data retention policies |
Mautic to HubSpot field mapping
The 30 most-used fields of 35 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
firstnameContactfirstnameContact -
lastnameContactlastnameContact -
emailContactemailContact -
phoneContactphoneContact -
mobileContactmobilephoneContact
| Mautic field | HubSpot field | Mapping | Note |
|---|---|---|---|
Contact.firstname | Contact.firstname | direct | |
Contact.lastname | Contact.lastname | direct | |
Contact.email | Contact.email | direct | |
Contact.phone | Contact.phone | direct | |
Contact.mobile | Contact.mobilephone | direct | |
Contact.title | Contact.jobtitle | direct | |
Contact.address1 | Contact.address | direct | |
Contact.city | Contact.city | direct | |
Contact.state | Contact.state | direct | |
Contact.zipcode | Contact.zip | direct | |
Contact.country | Contact.country | direct | |
Contact.company | Contact.associatedcompanyid | transformed | Mautic stores the primary company name as a contact field; HubSpot links contacts to companies via the associatedcompanyid lookup. The company must exist in HubSpot before contact migration runs. |
Contact.lead_points | Contact.lead_points__c | custom_field_required | Mautic point scores have no native HubSpot equivalent. We preserve the numeric value as a custom number property for reference and for rebuilding HubSpot's native scoring model. |
Contact.date_added | Contact.original_create_date__c | custom_field_required | HubSpot's Createdate is set at migration time. The original Mautic date_added is preserved in a custom datetime property for reporting continuity. |
Contact.last_active_date | Contact.lastcontacted | direct | |
Contact.do_not_email | Contact.email_opt_out | direct | |
Contact.utmsource | Contact.hs_analytics_source | direct | |
Contact.utmmedium | Contact.hs_analytics_source_data_1 | direct | |
Contact.utmcampaign | Contact.hs_analytics_source_data_2 | direct | |
Company.companyname | Company.name | direct | |
Company.website | Company.domain | direct | |
Company.industry | Company.industry | value_mapping | Industry picklist values are mapped value-by-value between Mautic and HubSpot's industry taxonomy. Unmatched values are preserved as custom text properties. |
Company.number_of_employees | Company.numberofemployees | direct | |
Company.annual_revenue | Company.annualrevenue | direct | |
Company.phone | Company.phone | direct | |
Company.city | Company.city | direct | |
Company.country | Company.country | direct | |
Company.date_added | Company.original_create_date__c | custom_field_required | HubSpot's Createdate is set at migration time. Original Mautic company creation date preserved as a custom datetime for audit continuity. |
Activity (Email).open_count | Engagement.email_open_count__c | custom_field_required | Mautic email open events are aggregated per contact per email. These are stored as custom numeric properties on the engagement record for reporting parity. |
Activity (Email).click_count | Engagement.link_click_count__c | custom_field_required | Mautic link-click events are aggregated and stored as a custom property on the HubSpot engagement record linked to the contact. |
What to watch for in a Mautic to HubSpot migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Mautic segments require manual rebuild as HubSpot lists
Mautic segments are rule-based contact collections stored with complex filter logic (behavioral triggers, property conditions, time-decay rules) that do not map to any HubSpot object.
How we handle it
HubSpot distinguishes between static lists (manually added contacts) and dynamic lists (property or behavior-based). After migration, your team must recreate each Mautic segment as either a HubSpot static list or a dynamic list using HubSpot's filter builder. We provide a segment inventory export listing every Mautic segment name, rule count, and associated contact count so your HubSpot admin can prioritize the rebuild.
Mautic point scores map to a reference property, not native HubSpot scoring
Mautic's lead_points field accumulates numeric values based on contact actions (email opens, page views, form submissions, custom events).
How we handle it
HubSpot's native lead scoring uses a 0–100 predictive model driven by property changes and engagement frequency — not an additive point system. We preserve Mautic's lead_points as a custom numeric property (lead_points__c) so historical scoring is available for reference, but HubSpot's predictive scoring will produce different scores from Mautic's behavior-driven point accumulation. Your team must define the HubSpot scoring model after migration.
Mautic self-hosted API rate limits are server-dependent
Mautic self-hosted instances (running on your own infrastructure) do not have a platform-defined API rate limit — rate limiting is configured at the web server level (Apache/nginx) and may vary by installation.
How we handle it
If your Mautic instance has aggressive server-level throttling, bulk data extraction during migration may require chunked exports or direct database queries rather than REST API calls. We assess the target instance's API responsiveness during the discovery phase and adjust the extraction strategy accordingly.
Mautic N:N contact-company associations collapse to HubSpot's primary company model
Mautic allows a contact to be associated with multiple companies simultaneously using a junction table (company_leads).
How we handle it
HubSpot contacts have a single primary associatedcompanyid, with secondary company associations handled via the Company Associations API or custom properties. We migrate the most recently modified primary company as the HubSpot associatedcompanyid and store additional company associations as a comma-separated custom property (additional_companies__c). Your admin decides whether to use HubSpot's multi-association API for a cleaner implementation.
Mautic stage field may conflict with HubSpot's lifecycle_stage
Some Mautic installations use a custom stage field on contacts to track lifecycle milestones.
How we handle it
HubSpot reserves lifecycle_stage as a specific contact property with a defined picklist (subscriber, lead, MQL, SQL, opportunity, customer, evangelist). If your Mautic stage field contains values that don't match HubSpot's lifecycle_stage taxonomy, we map them to the nearest HubSpot value or preserve them as a custom stage__c property to avoid picklist conflicts. This decision is made during the mapping phase with your input.
How the migration runs
Discover Mautic instance configuration and API surface
We connect to your Mautic instance via API (or direct database for self-hosted) and audit the contact, company, custom field, segment, and activity tables.
What this step covers
We count records per object, identify custom field types, assess API rate-limit behavior, and inventory segments and campaign definitions for the rebuild reference package. This phase produces a migration scope document that defines record counts, custom field mapping, and which Mautic objects have HubSpot equivalents versus no_equivalent status.
Create HubSpot custom properties and list structures
Before any data migration begins, we create all required custom properties in HubSpot that lack native equivalents.
What this step covers
This includes lead_points__c (numeric property for Mautic point scores), original_create_date__c (datetime for preserving Mautic creation timestamps), mautic_id__c (string for source traceability), additional_companies__c (string for N:N company associations), and any Mautic custom fields mapped as HubSpot custom properties. We document each HubSpot property internal name and ID for reference in the field mapping file. Schema preparation ensures HubSpot is ready to receive records without validation failures mid-migration.
Migrate companies and contacts in dependency order
HubSpot requires a company to exist before a contact can link to it via associatedcompanyid.
What this step covers
We sequence the migration: companies first (preserving parent-company hierarchy), then contacts with their company links resolved by matching company name or domain. N:N contact-company associations from Mautic are preserved in the additional_companies__c property during this phase. Custom field values are mapped per the field mapping file, with picklist values resolved one-by-one.
Run sample migration with field-level diff
A representative slice — typically 200–500 records spanning contacts, companies, and a mix of engagement types — migrates to a HubSpot test portal.
What this step covers
We generate a field-level diff comparing source values against destination values, flagging any mismatches in custom property mapping, picklist resolution, or timestamp preservation. You review the diff and approve field mapping adjustments before the full migration commits.
Execute full migration with delta-pickup window
The full record set migrates using HubSpot's Bulk API for contacts and companies.
What this step covers
A delta-pickup window (24–48 hours) captures any Mautic records modified during the migration window. Activities, form submissions, and engagement events are written after their parent contact records exist. An audit log records every operation, and one-click rollback is available if reconciliation identifies data integrity issues. We deliver a reconciliation report comparing Mautic record counts against HubSpot imported record counts.
- 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
Mautic-to-HubSpot migration pricing reflects record count, custom field volume, and the complexity of transforming point-score history into HubSpot contact properties. Mautic instances with 50+ custom fields, multiple company hierarchies, or extensive engagement activity (email opens, page views, form submissions) land in the upper range because field-level property mapping doubles validation work. Segments requiring manual rebuild after migration add scope. The typical range covers contact and company migration with standard field mapping, point-score preservation, and a sample migration with field-level diff before the full run commits. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Mautic to HubSpot →Why teams move from Mautic to HubSpot
- Mautic's per-seat and per-contact costs on managed cloud tiers have climbed toward HubSpot's pricing, while the platform still lacks the native CRM depth that teams need as they scale — HubSpot's CRM-first model offers tighter sales-rep adoption and a unified contact record that Mautic's secondary CRM layer cannot match.
- HubSpot's native deal pipeline and lifecycle stage tracking give sales teams immediate visibility into pipeline health without the custom object configuration that Mautic requires for equivalent reporting — teams report that Mautic's CRM reporting demands significant developer time to match HubSpot's built-in dashboards.
- HubSpot's marketplace of native integrations with Salesforce, Slack, Zoom, and hundreds of other tools reduces the API customization overhead that self-hosted Mautic instances require — teams on Mautic frequently report spending engineering cycles maintaining Zapier/Make workflows that HubSpot replaces with native connectors.
- Acquia's Mautic cloud pricing and tiering have become less predictable for growing teams, and community support for self-hosted instances can lag when complex plugin or database issues arise — HubSpot's enterprise support tiers provide consistent SLA coverage that distributed open-source communities cannot guarantee.
Questions, answered
Mautic to HubSpot migration questions
How long does a Mautic to HubSpot migration take?
Most Mautic-to-HubSpot migrations complete within 48–72 hours for instances under 50,000 contacts and companies. Larger setups with 100,000+ records or 50+ custom fields extend to 5–10 days. The planning and schema-setup phase typically takes 3–5 days before migration begins. For Mautic self-hosted instances, we schedule an additional discovery day to assess API rate-limit behavior and server configuration if aggressive throttling is detected. This ensures the extraction strategy accounts for any custom rate-limiting rules before migration execution begins.
Will my Mautic campaigns and marketing workflows migrate to HubSpot?
No. Mautic campaigns and marketing automation workflows do not migrate — they require manual rebuild in HubSpot. Mautic campaign definitions (triggers, conditions, actions) use a proprietary format that has no HubSpot equivalent; HubSpot's Workflows tool must be used to recreate this logic. We provide a campaign inventory export listing every Mautic campaign name, associated emails, segment membership, and rule logic as a rebuild reference for your HubSpot team.
What happens to Mautic lead points in HubSpot?
Mautic's lead_points field migrates as a custom numeric property (lead_points__c) on the HubSpot contact record, preserving the historical score value for reference. HubSpot's native lead scoring uses a 0–100 predictive model driven by property changes and engagement patterns rather than an additive point system. The two scoring models will produce different values — the custom property serves as a baseline while your team defines a new HubSpot scoring model aligned with your current buyer journey.
Can I migrate Mautic custom fields to HubSpot custom properties?
Yes. All Mautic contact and company custom fields migrate to HubSpot as custom properties, preserving the field type: text fields become single-line text, number fields become number properties, date fields become date properties, and picklist fields become HubSpot select menus with values mapped one-by-one. Boolean fields map to HubSpot's boolean property type. We create the custom properties in HubSpot before migration begins so the schema is ready when records are written.
What happens to Mautic contact segments in HubSpot?
Mautic segments require manual rebuild as HubSpot lists. Mautic segments are rule-based collections with complex filter logic that does not map to any HubSpot object. After migration, your team must recreate each segment as either a HubSpot static list (manually populated contacts) or a dynamic list (property and behavior-based filters). We deliver a segment inventory export listing every Mautic segment name, rule count, associated contact count, and filter logic so your HubSpot admin can prioritize and execute the rebuild.
Does the migration affect my Mautic account during cutover?
No active changes are made to your Mautic instance during migration. We establish scoped read-only API access to your Mautic account, allowing your team to continue working in Mautic throughout the entire migration process without interruption. A delta-pickup window of 24–48 hours captures any contacts, companies, or engagement events modified in Mautic during the cutover window, ensuring HubSpot reflects Mautic's final state at go-live. No write operations target your Mautic instance at any point during the migration.
Why did my Mautic contacts with multiple companies show only one company in HubSpot?
HubSpot contacts support only a single primary associatedcompanyid, while Mautic natively supports N:N contact-to-company associations through a junction table. We migrate the most recently modified primary company from Mautic as the HubSpot associatedcompanyid and preserve all additional company associations in a custom property called additional_companies__c. Your HubSpot administrator can leverage HubSpot's multi-association API after migration to create cleaner secondary company links if a more normalized association structure is preferred for reporting.
Related migrations
HubSpot implementation
Set up HubSpot and migrate into it as one engagement.
See the service → SuiteDash to HubSpotMapping · history · rollbackAccelo to HubSpotMapping · history · rollbackTeamleader to HubSpotMapping · history · rollbackOntraport to HubSpotMapping · history · rollbackMoEngage to HubSpotMapping · history · rollbackBigin by Zoho CRM to HubSpotMapping · history · rollback Mautic to SalesforceMapping · history · rollbackSources: official documentation
- Format import files — HubSpot Knowledge Base
- Create and edit custom objects — HubSpot Knowledge Base
- Import objects programmatically — HubSpot Knowledge Base
- Understand property field types in HubSpot
- Associate records on CRM objects — HubSpot Knowledge Base
- Integration throughput and limits — HubSpot Knowledge Base
- HubSpot Cloud Infrastructure and Data Hosting FAQ
Get a quote
Moving from Mautic to HubSpot?
Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.
Get a quote