Migrate from Mautic to Pipedrive

Mautic Contact records map directly to Pipedrive Person. The Contact email becomes the Person email address used as the dedupe key. Mautic custom contact fields map to Pipedrive custom Person fields of the matching type (text, number, date, dropdown). We extract contacts from MySQL/MariaDB directly rather than relying on Mautic v6's broken CSV export, or via the REST API in batched GET requests at 300 records per call. The Person must be created before any Deal import because Pipedrive Deals require a Person link.

Mautic Company records map to Pipedrive Organization. The Company domain becomes the Organization's Website field and is used as the dedupe key. Multiple Mautic Contacts linked to one Company create multiple Pipedrive Person records, each linked to the same Organization via the Organization ID resolved at import time. Organization is created before Person import so the relationship is satisfied on insert.

Mautic Deals map to Pipedrive Deals. The Deal title, value, stage, owner, expected close date, and custom fields migrate directly. Mautic deal stage names map to Pipedrive Pipeline stage names that we configure before migration. Pipedrive requires a linked Person and Organization on every Deal; we resolve these from the Contact and Company lookups before Deal import begins.

Mautic Campaigns are automation workflows with trigger conditions and action sequences. Pipedrive has no native campaign builder. We export the campaign name, definition, step sequence, and member list as a written specification document that your admin uses to rebuild the logic in Pipedrive Workflows or a third-party automation tool. Campaign membership itself is preserved as a custom Person field or as Pipedrive Activity records for audit trail purposes.

Mautic Segments are dynamic contact lists filtered by field values, tags, or behavioral criteria. Pipedrive has no dynamic segment equivalent; static lists and saved filter Views serve as the closest analog. We export the segment filter definition (field conditions, operators, and logic) as a written specification document and map the segment membership to a corresponding Pipedrive static list or filter-based View. The segment logic itself must be recreated by your admin using Pipedrive's filter builder.

Mautic Stages (contact lifecycle positions such as Lead, MQL, SQL, Customer) map to Pipedrive Pipeline stages. We create a Pipedrive Pipeline named after the Mautic lifecycle model, populate the stages with the matching Mautic stage names, and set stage probabilities. Stages with no direct pipeline analog are documented as custom Person fields or as a separate lifecycle field that your admin configures in Pipedrive.

Mautic's Points system assigns numeric scores to contacts based on actions. Pipedrive has no native lead scoring. We migrate the point value as a custom numeric field on Person named mauntic_points__c. Any Mautic Point Groups are documented as score-range tiers (e.g., 0-50 = Cold, 51-100 = Warm) for your admin to recreate as filter conditions in Pipedrive.

Mautic tags are flat string labels applied to contacts, companies, and other objects. We export all unique tag strings and recreate them as a multi-select custom field on Person (and optionally Organization) named mautic_tags__c. Tags used for Mautic segment membership logic are preserved as individual tag records and the segment filter definition is documented separately.

Mautic Forms collect contact data and trigger campaign actions. Pipedrive has no native form builder. We export form field configurations and associated campaign actions as a written specification document. Form submissions themselves (the contact records with form source attribution) migrate as Person records with a custom field capturing the original form name. Your admin rebuilds the form in a tool like Typeform, HubSpot Forms, or Pipedrive's native webform.

Mautic Custom Objects extend the data model beyond standard Contacts and Companies. Pipedrive supports custom fields on Person, Organization, and Deal but not standalone custom object records. We migrate each Custom Object as a set of custom fields on the related Person or Deal, and we document the original Custom Object schema and relationship definitions as a written handoff so your admin can decide whether to implement the data as additional custom fields, related Deal activities, or a separate database linked via the Pipedrive API.

Mautic email engagements (sent, open, click, bounce events) map to Pipedrive Activity records of type email. The email subject, body, and timestamp migrate to the Activity fields. Engagement metadata (open count, click count) is preserved as custom Activity fields. We resolve the linked Person by email address match before inserting each Activity record.

Mautic call engagements map to Pipedrive Activity records of type call. Call duration, disposition, and outcome migrate to the Activity's duration, result, and notes fields. The linked Person is resolved by email match. Activity timestamp preserves the original Mautic engagement timestamp for timeline ordering.

Mautic meeting engagements map to Pipedrive Activity records of type meeting. Title, start time, end time, location, and attendees migrate directly. The primary attendee Person is resolved by email match and linked to the Activity.

Mautic note engagements map to Pipedrive Activity records of type note. Note content migrates as the Activity's subject and content fields. The linked Person or Organization is resolved by the Mautic engagement's associated contact or company record.