Migrate from Mautic to Twenty CRM

Mautic Contacts map directly to Twenty People. Standard fields (email, firstname, lastname, phone, title, city, country) migrate to their Twenty equivalents. Mautic custom contact fields migrate to Twenty custom fields on People — but the Twenty custom field must be created in Settings → Data Model BEFORE the CSV import runs, per Twenty's documentation. We create all custom fields in the destination schema first, then map Mautic field values during import. Mautic's point score migrates to a numeric custom field on People, and Mautic's stage value migrates to either a custom picklist field or a tag-based indicator in Twenty.

Mautic Company records map directly to Twenty Company. Domain name from Mautic becomes the Company website field and serves as the dedupe key during import. Mautic's industry, annual_revenue, and number_of_employees fields migrate to their Twenty equivalents. Company is imported before People so that the company link on People is satisfied at insert time. Multi-company associations from Mautic (a Contact can belong to multiple Companies) are handled as a 1:N People-to-Company relationship in Twenty, with the primary company designated first.

Mautic Campaigns with associated financial records (campaign revenue fields or linked deals) map to Twenty Opportunities where the campaign name becomes the Opportunity name and the campaign type becomes a custom picklist. Campaigns without deal associations are exported as written configuration documentation: campaign logic, step sequences, and contact membership criteria. Twenty does not have a native Campaign object equivalent; the campaign is represented as an Opportunity if it had a revenue target, or as a written handoff note for the customer's admin to rebuild inside Twenty's workflow builder.

Mautic Segments (dynamic contact lists filtered by field values, tags, or behaviors) have no direct Twenty equivalent. We export the segment filter definitions — the field names, operators, and values that define each segment — as a written inventory document. The customer's admin rebuilds these inside Twenty as filtered views or custom objects. Segment membership itself is not migrated because Twenty recalculates list membership based on its own data.

Mautic Stages (contact lifecycle positions such as Lead, MQL, Customer) map to Twenty Opportunity Stage values if they apply to the sales pipeline, or to a custom picklist field on People if they track contact lifecycle. We work with the customer during scoping to determine which Stages represent deal progression (mapped to Opportunity Stage) and which represent contact status (mapped to a custom People field). Stage transition timestamps from Mautic migrate as custom date fields on the target object.

Mautic's points-based lead scoring system migrates as a numeric custom field on Twenty People. Point groups (named score buckets) migrate as named value pairs or tags on the People record. The scoring logic itself — the rules that assign points for behaviors — does not migrate and is documented as a written handoff for the customer's admin to implement inside Twenty's workflow builder.

Mautic tags (flat string labels) migrate to Twenty as a multi-select picklist on People if the tag count is under 100, or as tag values stored in a custom text field if the tag vocabulary is larger. Tags are preserved exactly as strings from Mautic; no tag consolidation or synonym mapping is applied unless the customer requests it during scoping.

Mautic Custom Objects migrate to Twenty Custom Objects with the same API-name-style naming convention. The destination schema (custom object name, custom fields, field types, picklist values) must be created in Twenty Settings → Data Model before data import begins. Mautic's Custom Object Relationships are accessed via the MySQL database junction tables because the Mautic REST API endpoint for relationship creation is documented as non-functional (2022 community report). We map junction table records to Twenty's native lookup relationships between custom objects, preserving the parent-child structure. Relationship cardinality is preserved as documented in the source schema.

Mautic engagement records (calls, emails, meetings, notes) migrate to Twenty Task and Note objects. The engagement timestamp migrates as the ActivityDate on Task; engagement body and subject migrate as fields on Note. The primary contact lookup on each engagement migrates to the linked People record in Twenty. Note: Twenty's Timeline Events API does not support standalone timeline entries without an attached note or task — a known limitation documented in Twenty's GitHub discussions (discussion #8948). We work around this by migrating engagements as Note records with the original Mautic engagement type stored as a custom field, preserving the full activity history in a queryable format.

Mautic Users map to Twenty workspace Members. We match by email address. Critical constraint: Twenty requires users to be invited and to accept their invitation BEFORE any data import that references an Owner or assignee. We extract all owner and assignee references from Mautic records, resolve them against the Twenty Member list, and flag any owner without a matching Twenty user as a reconciliation item. The customer's admin provisions missing users before the record import phase begins.