Migrate from Mautic to Odoo CRM

Mautic Contacts migrate to Odoo CRM Lead. We use Mautic's lifecycle stage, point value, and lead status properties to determine the initial Odoo Lead stage. The email address serves as the primary key for deduplication. If the Mautic contact has an associated Company with a revenue or industry field, those values map to corresponding Lead fields. We preserve the original Mautic contact ID in a custom field mautic_id__c on the Lead for audit and reconciliation.

Mautic Contacts that represent existing customers (lifecycle stage = customer or evangelist) can optionally map to Odoo CRM Contact records attached to a Company rather than to Lead. The customer chooses during scoping based on whether they want to maintain a distinction between prospect Leads and active customer Contacts in Odoo. We create a custom field mautic_lifecycle_stage__c on both Lead and Contact to preserve the original classification.

Mautic Company records map directly to Odoo CRM Company. The company domain field maps to the Website field in Odoo, and domain-based deduplication is applied during import. Odoo Company supports address, industry classification, annual revenue, and number of employees fields that map from their Mautic equivalents. We create the Company record first in each batch so that the Contact import can satisfy any contact-to-company association by name or domain lookup.

Mautic Deals migrate to Odoo CRM Opportunity. The deal stage maps to an Odoo Stage within the configured pipeline. The associated contact and company resolve to the migrated Lead/Contact and Company records. Deal amount, expected close date, and probability migrate to Opportunity amount, date_closed, and probability fields. We configure the Odoo CRM pipeline stages before migration so that stage names and probabilities align with the customer's existing Mautic deal workflow.

Mautic pipeline stages map to Odoo CRM Stage configurations within the Opportunity pipeline. Each Mautic pipeline becomes a separate Odoo team or sales channel with its own stage sequence. Stage probabilities migrate from Mautic to Odoo with rounding to Odoo's percentage format. Stage color coding and sequence order transfer to Odoo's Kanban view configuration.

Mautic Segments (dynamic contact lists filtered by field values, tags, or behavioral criteria) are not replicated as static lists in Odoo. We export the segment filter definition and recreate it in Odoo as saved filter groups on the Lead and Contact list views. The segment membership itself is recalculated at the destination based on the same criteria. We deliver a filter specification document listing each segment's conditions, operators, and field references for manual Odoo filter recreation.

Mautic Campaigns are marketing automation workflows with triggers, conditions, actions, and delays. Odoo CRM has no native campaign automation equivalent. We export campaign definitions, step sequences, and contact membership counts. The customer receives a written campaign specification document describing each campaign's trigger logic, step actions, timing, and associated assets. Odoo CRM sales teams are expected to replicate campaign logic manually or via Odoo Studio automations post-migration.

Mautic Forms collect contact data and trigger campaign actions on submission. We export form field configurations, field types, validation rules, and submission mappings. Odoo Website and Contact modules have a form builder but no native campaign-triggered follow-up logic. We deliver a form field mapping document and recommend rebuilding forms in Odoo Website or a compatible form app. Webhook-based post-submission actions do not migrate and must be reconstructed in Odoo Studio or via a third-party automation app.

Mautic Stages define contact lifecycle positions (Lead, MQL, SQL, Customer). We map stage names directly to Odoo CRM Lead stages and, where applicable, to Contact tags. If the customer uses Mautic stages as a lead scoring mechanism, we combine stage information with point values to assign initial Odoo Lead status and create a custom field for the original stage name.

Mautic's point system scores contacts based on actions. Point values migrate as a custom integer field mautic_points__c on Lead and Contact. If the customer uses point thresholds for routing or prioritization, we recommend converting those thresholds into Odoo Lead stage assignments or automated stage-update actions built in Odoo Studio. Point-based scoring logic does not have a native Odoo equivalent and requires manual reconstruction.

Mautic Tags are flat string labels applied to contacts and other objects. All tags export and reapply during migration as Odoo CRM tags on the corresponding Lead or Contact record. Tag-based segmentation is preserved through the segment-to-filter translation described above. Tag counts per contact are maintained as the number of applied tags in Odoo.

Mautic Categories group assets, campaigns, emails, and contacts into hierarchical folders. We export the category hierarchy and reassign related objects to Odoo tags or CRM teams depending on whether the category represents a functional grouping (marketing vs sales) or a content classification. The customer chooses the category-to-tag or category-to-team mapping during scoping.

Mautic Assets are downloadable files (PDFs, guides, media) with metadata. We export asset metadata (name, URL path, MIME type, download count) and replicate the file storage structure in Odoo Documents or as attachments on the related Lead, Contact, or Company record. Large binary files migrate via the Odoo XML-RPC file upload API. Asset download counts and related campaign associations are preserved in custom fields or notes.

Mautic Custom Objects extend the data model beyond standard contacts and companies. We export custom object definitions and data, then recreate equivalent record types in Odoo using Odoo Studio, including all custom fields, field types, and lookup relationships to standard objects (Lead, Contact, Company, Opportunity). Relationship data between custom objects in Mautic is accessed via the junction tables in MySQL/MariaDB because the Mautic Relationships API is non-functional, and the relationship records are mapped to Odoo's many2many or one2many fields through the XML-RPC API.

Mautic email engagements (sent, opened, clicked, bounced) migrate to Odoo CRM Message records attached to the target Lead or Contact. The WhoId links the message to the Lead; Subject, Body, and Date transfer to corresponding Message fields. We preserve the engagement type (sent, opened, clicked) as a custom field because Odoo Message does not natively track open and click events. Activity timeline ordering is preserved by setting Message Date to the original Mautic timestamp.

Mautic call engagements map to Odoo CRM call logs attached to the target Lead or Contact. Call duration, disposition, and recording URL (if stored in Mautic) transfer to custom fields on the activity record. The WhoId on the activity points to the migrated Lead. Call timestamp migrates as the activity date, preserving the chronological activity timeline.

Mautic meeting engagements map to Odoo Calendar Event records. Start time, end time, location, and attendee information transfer to the corresponding Event fields. Attendee mapping links to EventPartner records pointing to the migrated Lead or Contact. Meeting subject and body migrate as the event description.

Mautic Notes migrate to Odoo CRM Notes attached to the relevant Lead, Contact, Company, or Opportunity. Note body transfers as plain text. Mautic Task engagements (internal tasks with owners and due dates) migrate to Odoo CRM Tasks linked to the owner by email resolution. Task status and priority migrate to the corresponding Odoo fields.