Migrate from Mautic to HighLevel

Mautic Contacts map directly to GoHighLevel Contacts. We extract from the MySQL/MariaDB leads table to bypass Mautic v6's broken CSV export. Standard fields (email, firstname, lastname, phone, city, state, country, company) map to their GoHighLevel equivalents. All Mautic custom contact fields (user-defined fields stored in lead_fields) are pre-created in GoHighLevel as contact custom fields before import. UTF-8 encoding and date format (YYYY-MM-DD) are validated during extraction to match GoHighLevel import requirements.

Mautic Companies map to GoHighLevel Companies. The company ID from Mautic's companies table becomes the dedupe key during GoHighLevel import. Address fields (street, city, state, zip, country) map directly. Industry, annual_revenue, and website map to GoHighLevel Company custom fields or standard fields depending on the customer's field configuration. The contact-to-company association in Mautic (many-to-one, contacts can belong to multiple companies) maps to GoHighLevel's primary company association on the contact record.

Mautic Segments (dynamic filter-based contact lists) cannot be imported as Segments into GoHighLevel because GoHighLevel uses Tags as its primary segmentation mechanism. We export the segment definition and membership, then apply all segment tags to each contact during import. For example, if a Mautic contact belongs to segments 'High-Value' and 'SMS-Opted-In', we create GoHighLevel tags with those names and apply them during the contact import. This preserves segment membership logic in a form GoHighLevel's Smart List filters can reference.

Mautic Campaigns (automation workflows with trigger conditions and action steps) are documented and exported as JSON definitions but do not migrate as code. GoHighLevel's Workflows use a different trigger-action model (event-based triggers with visual canvas branching) that cannot be programmatically translated from Mautic's campaign structure. We deliver a written inventory of every Mautic Campaign with its trigger type, conditions, and action sequence, plus a GoHighLevel Workflow recommendation for each. The customer's admin rebuilds the automations in GoHighLevel's workflow builder using our inventory as the specification.

Mautic Stages define lifecycle positions (e.g., Lead, MQL, SQL, Customer). If the customer uses GoHighLevel Pipelines and Opportunities for deal tracking, Mautic Stages map to Pipeline stage names. If the customer does not use Opportunities and tracks lifecycle only on contacts, Mautic Stages migrate as a contact custom field (mautic_stage__c) with the original stage value preserved for segmentation and reporting.

Mautic's Points system (numeric lead scoring based on actions) migrates to a GoHighLevel contact custom field (mautic_points__c) holding the raw point integer. Point Groups (thresholds like 'Lead at 100 points') are documented as written specifications for the customer to recreate as GoHighLevel automation triggers. Mautic's point-change history (chronological log of score changes) does not migrate because GoHighLevel's activity model does not support a native point-change audit log.

Mautic 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. Mautic tag names are preserved verbatim in GoHighLevel. Tags used to denote import source (e.g., 'imported_from_mautic') are added during migration for reconciliation.

Mautic Custom Objects extend the data model beyond standard contacts and companies. We map each Custom Object to a GoHighLevel Custom Object with equivalent fields. Mautic Custom Object Relationships (the junction table records connecting object types) are extracted directly from MySQL/MariaDB because the Mautic Relationships API is documented as broken in community reports. We create the corresponding GoHighLevel Custom Object relationship records via the API after both parent objects are imported. Schema is pre-provisioned in GoHighLevel before any data moves.

Mautic Forms (data collection forms with field configurations and campaign triggers) are exported as field-level definitions but do not migrate as functional forms. GoHighLevel's Form builder uses a different field type system and submission handling. We deliver a form inventory document listing every Mautic Form with its field names, types, validation rules, and associated campaign actions, which the customer's admin uses to recreate forms in GoHighLevel's form builder.

Mautic Assets (downloadable files like PDFs and guides) are stored as binary blobs with metadata in the Mautic database. We export the asset metadata (file name, size, download URL) and include it in the migration inventory. The actual file blobs are extracted separately and uploaded to GoHighLevel's file storage or the customer's designated storage. If the customer uses a CDN or file hosting service, we map the asset URLs accordingly. Landing page content and theme assignments are documented separately for manual recreation.