Migrate from Mautic to Freshsales

Mautic Contacts map to Freshsales Lead or Contact based on the contact's lifecycle stage and activity profile. Contacts with Mautic lifecycle stages below marketing qualified lead (subscriber, lead, marketing qualified) map to Freshsales Lead. Active, sales-qualified, customer, or evangelist stages map to Freshsales Contact attached to an Account. The original Mautic lifecycle stage and point score migrate as custom fields on both Lead and Contact for audit. This split is the single most important design decision in the migration and must be confirmed with the customer's RevOps lead before any records are written.

Mautic Company records map directly to Freshsales Account. Address, industry, annual revenue, website, and phone fields map to their Freshsales equivalents. Mautic's many-to-one Contact-to-Company relationship (one contact can associate with multiple companies) requires resolution: the primary company becomes the AccountId on the Contact record, and secondary company associations are preserved in a custom text field listing additional account IDs or names for reference.

Mautic Campaigns are automation workflows with trigger events, conditions, and action sequences. Freshsales Campaigns are grouping labels for marketing attribution with no automation logic. We export campaign names, statuses, dates, and contact membership counts as a Campaign reference record in Freshsales. The automation logic is captured in a written campaign inventory document describing each campaign's trigger (contact action or time interval), filter conditions, and action sequence for the customer's admin to rebuild in Freshsales Workflows. This document is the primary handoff artifact for the automation rebuild scope.

Mautic Segments are dynamic contact lists filtered by field values, tags, and behavioral conditions. Freshsales does not replicate dynamic segment logic natively. We export segment definitions (filter criteria, tag membership, date ranges) as a written segment inventory. Where segments are small and stable, we can pre-filter and migrate the resulting contact list as a Freshsales Static List. Complex or dynamic segments require rebuilding as Freshsales Filters or Automation Rules post-migration.

Mautic Custom Objects extend the data model with user-defined schemas and relationship records. Freshsales supports custom fields on standard objects but Custom Object API coverage and bulk import support varies by Freshsales plan tier. We profile the source Custom Object schemas and their relationship junction tables (accessed directly from MySQL/MariaDB because the Mautic Relationships API is documented as non-functional) and map them to Freshsales custom field structures. If the destination Freshsales plan limits custom object support, we restructure the data as custom fields on the Contact or Account object and flag the constraint during scoping.

Mautic Stages define contact lifecycle positions (e.g., Lead, MQL, Customer, Evangelist). Freshsales does not have a native equivalent across all tiers. We create a custom Lifecycle_Stage__c picklist field on Contact and Lead with the same stage values, and migrate the original Mautic stage name for each record. If the customer uses Freddy AI, the custom stage field supplements the built-in predictive scoring model.

Mautic's points system assigns numeric scores to contacts based on actions (page visits, form submissions, email opens). Freshsales does not replicate Mautic's points engine natively. We migrate the point value as a custom numeric field lead_score__c on the Contact and Lead records. The customer can use this field in Freshsales Filters to replicate segment logic, or map it to Freddy AI scoring inputs if they configure a custom scoring model.

Mautic tags are flat string labels applied to contacts and other objects. We export all tags and reapply them during migration as tags on the Freshsales Contact or Lead record. Tag-based segmentation logic is preserved as a tag reference, with the segment inventory document capturing which tags were used in segment filter rules for rebuild in Freshsales Filters.

Mautic Assets are downloadable files (PDFs, guides, media) managed within the platform. We export asset metadata (filename, description, upload date, download count) as a reference record in Freshsales. The actual file binary is exported as a ZIP archive and delivered alongside the migration for manual re-upload to Freshsales Documents, Dropbox, or a CDN-based storage solution of the customer's choice.

Mautic engagement records (calls, emails, meetings, tasks, notes) are stored in activity tables linked to contact IDs. Freshsales surfaces these as activity timeline entries on the Contact or Lead record. We export engagement type, subject, body, timestamp, and disposition (for calls) and write them as Freshsales Activity records. The engagement history timeline is preserved by setting the activity date to the original Mautic timestamp. Note that Freshsales has a limit on how far back activity history is displayed in the UI timeline; very large activity histories are written as records and are queryable via reports even if UI display is paginated.