Migrate from Odoo Marketing Automation to Twenty CRM

Odoo stores contacts in the res.partner table with a partner_type or is_company flag distinguishing individuals from organizations. We filter res.partner records where is_company is false and map them to Twenty Person records. The contact name, email, phone, and address fields transfer directly. Custom fields on the partner record carry over as key-value pairs. Tags on the Odoo contact become Twenty Person labels.

Odoo CRM Leads map to Twenty Person records in the pre-conversion state. The lead name, email, phone, source, priority, and expected closing date transfer. Stage names vary by Odoo database and require a mapping table that we build during scoping. Odoo's lead-to-opportunity conversion data (lost_reason, won_date) migrates as custom fields on the Person record for audit. The customer decides whether to convert leads to opportunities during migration or preserve them as open People records.

Odoo CRM Opportunities map directly to Twenty Opportunities. Opportunity name, stage, expected revenue, close date, lost reason, and priority transfer. The Odoo crm.lead stage field maps to Twenty Opportunity stage values, and we configure the destination stage pipeline before migration. Partner (account) lookup resolves to the target Company record via the partner_id foreign key.

Odoo organizations stored in res.partner with is_company=true map to Twenty Company records. Company name, website, address, industry, and employee count transfer. The domain field on the Odoo company record populates the Company domain. We handle the parent_company hierarchy where it exists in Odoo, linking subsidiaries to parent Companies via the parent_id relationship.

Odoo Marketing Automation Campaigns map as named containers in Twenty CRM. Twenty does not have a native Campaign object equivalent to Odoo's marketing campaign container, so we create a naming convention using a workspace prefix or a custom target label that groups related Opportunities and People by campaign origin. Campaign state (active, draft, archived) migrates as a tag on the grouped records.

Odoo Automation Rules with trigger types of time-based, email event, or server action (excluding Python Code) are documented in full. We capture the rule name, trigger type, filter domain (the domain widget conditions), action chain (send email, update record, create task), timing, and child activity links. This becomes a written automation inventory that the customer's admin uses to rebuild equivalent logic in their chosen automation tool (e.g., Zapier, Make, or a dedicated MAP). Python Code activity blocks are flagged separately as non-rebuildable without custom development.

Individual workflow steps within an Automation Rule are documented as part of the automation inventory. Email activity steps capture the template reference and timing. SMS steps capture the SMS template and recipient logic. Update Record steps capture the field and new value. Create Task steps capture the assignee, deadline, and description. Each activity step is mapped to its parent Automation Rule for complete rebuild context.

Odoo Email Marketing mass mailing records migrate as archived campaign history. Subject, scheduled date, recipient count, and sent/failed/delivered metrics transfer to a Note record or custom activity log on the relevant Campaign grouping. Email body HTML migrates as a Note attachment for reference. Delivery receipts and bounce data do not have a Twenty equivalent and are preserved in the mass mailing inventory for post-migration review.

Odoo Email Templates (mail.template model) migrate as Note records with the template name, subject, and HTML body preserved. Inline images and variable placeholders (${object.field}) are flagged as needing manual revision because Twenty does not execute template rendering. The template serves as a content reference for the customer's team to recreate in their chosen email tool.

Odoo custom fields added via Odoo Studio or ir.model.fields migrate as key-value pairs on the parent record. Field types (char, integer, many2one, date, etc.) are read from ir.model.fields metadata and mapped to the equivalent type in Twenty's schema. Many2one relations (e.g., custom fields pointing to a product or user) are resolved to the migrated record ID or flagged for manual resolution if the target record type is not in scope.

Odoo tags on Contacts, Leads, and Opportunities (stored in ir.attachment as a tagging model) migrate as string arrays and reassign by name as Twenty Labels on Person and Opportunity records. Tag color metadata from Odoo does not transfer as Twenty does not have an equivalent color-coding attribute on Labels.

Odoo user accounts referenced as create_uid, write_uid, and assignees on CRM records and automation rules map to Twenty User records by email match. Any Odoo Owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Odoo users map to inactive Twenty Users to preserve ownership history.