Migrate your Mautic data

Contacts are the primary object in Mautic, with a standard schema of built-in fields plus user-defined custom contact fields. We map all standard fields (email, name, company, title, phone, location) and iterate through custom field definitions to preserve values during import. Contacts support tags, segments, and lifecycle stage tracking.

Mautic's Company object stores organizational records with address, industry, revenue, and website fields. Contacts can be associated with multiple companies. We preserve the many-to-one contact-to-company relationship by matching on company name or external ID during migration.

Campaigns in Mautic are automation workflows that trigger on contact actions or time intervals. We export campaign definitions, step sequences, and contact membership. Because destination CRMs model campaigns differently, we preserve campaign logic as a structured mapping rather than a direct object copy.

Segments (dynamic contact lists filtered by field values, tags, or behaviors) are exported as filter definitions. The segment membership itself is recalculated at the destination based on the same filter logic, ensuring contacts land in the correct groups without duplicating membership records.

Forms collect contact data and trigger actions on submission. We export form definitions, field configurations, and associated campaign actions. Mapping is required because field types and validation rules differ across platforms.

Custom Objects extend the data model beyond standard contacts and companies. Relationships between custom objects are supported in the UI but the Relationships API remains incomplete (2022 forum reports the create-relationship endpoint does not function). We handle custom objects via direct database mapping where API access is blocked.

Assets are downloadable files managed within Mautic (PDFs, guides, media). We export the asset metadata and replicate the file storage structure. The files themselves are migrated as binary blobs via the filesystem rather than the API.

Landing pages are standalone web pages built in Mautic's builder. We export page content, theme assignments, and tracking configuration. Full page recreation depends on destination page builder capabilities.

Stages define contact lifecycle positions (e.g., Lead, MQL, Customer). We map stage names directly between systems where the destination uses a comparable lifecycle model.

Mautic uses a points system to score contacts based on actions. We export point values and the point group configurations. Point-based scoring logic is translated to the destination's equivalent lead scoring model.

Tags are flat string labels applied to contacts and other objects. We export all tags and reapply them during migration, preserving tag-based segmentation logic.

Categories group assets, campaigns, emails, and contacts into hierarchical folders. We export the category hierarchy and reassign all related objects to matching category structures.

Users are Mautic's internal accounts with granular role-based permissions. We export user records, role definitions, and permission sets. Permissions are mapped to the destination's access control model because role structures vary across platforms.

Mautic's Reports module stores saved report configurations tied to its internal database schema and PHP-based reporting engine. These configurations are not portable across platforms and are not migrated.