Migrate from Odoo Marketing Automation to monday CRM

Odoo Contacts map to Monday.com CRM People records. We migrate name, email, phone, company (as a linked Company entity), tags, and custom fields. The Odoo partner model is unified for Contacts and Leads; we preserve the distinction by migrating records tagged as contact_type=contact to People with a Contact type label and records tagged as contact_type=lead to People with a Lead type label. Email addresses serve as the dedupe key during import.

Odoo Leads map to Monday.com CRM People with a Lead type label to preserve the source distinction. We migrate lead name, email, stage, priority, expected closing date, and source. The Odoo contact_type field determines whether a record lands as a People item with Contact or Lead designation. Stage names vary by Odoo database and require a mapping table; we document the stage mapping during scoping.

Odoo Opportunities map to Monday.com CRM Deals. We migrate opportunity name, stage (mapped to Deal Status column), expected revenue (mapped to Deal Value column), partner (linked to People or Company), and lost reason. Odoo's domain-filtered opportunity targets migrate as pre-filtered Deal board views. Stage probabilities from Odoo become informational notes on Deal records since Monday.com Deals do not have native probability fields.

Odoo Marketing Automation Campaigns map to Monday.com Boards as the top-level container. Campaign name, target model (Contact, Lead, Sales Order), and audience domain filter are preserved as board metadata. Campaign state (draft, running, stopped) migrates as a Status column on the board. Traces and activity logs from Odoo are stored as Items on the board to preserve the campaign enrollment history.

Odoo Automation Rules (the workflow definition that triggers actions) are documented but not migrated as code because Monday.com's automation model differs structurally. We produce a written inventory of every automation rule with its trigger type (time-based, email event, server action), filter domain, action chain, and recommended Monday.com automation equivalent. Python Code activity blocks within rules are flagged as manual-rebuild items with no Monday.com equivalent noted.

Individual workflow activities within Odoo automation rules (Send Email, Update Record, Create Task, SMS) are documented as steps in the automation inventory. Email activities map to a recommended Monday.com Email integration or manual email workflow step. Update Record and Create Task activities map to recommended Monday.com automation recipes. The parent-child activity linkage is preserved in the documentation so the customer's team can reconstruct the workflow logic.

Odoo Mass Mailings (subject, body HTML, scheduled date, recipient count) are migrated as Items on the relevant Campaign board with template content stored in a text or rich text column. Recipient lists are resolved via Contact and Lead deduplication before import. Monday.com does not have a native mass mailing engine; we recommend pairing the migrated mailing history with a third-party email platform (Brevo, Mailchimp) for ongoing sends.

Odoo Email Templates (HTML body, subject, inline images, variable placeholders) are migrated as text or rich text content stored in a dedicated Template board. Variable placeholders are preserved as literal text strings for the customer to reconfigure in their chosen email platform post-migration. Monday.com does not maintain a native email template library; this mapping delivers the template content for manual recreation in an integrated email tool.

Odoo Companies map to Monday.com CRM Company entities. We migrate company name, website, address, phone, and tags. Companies are linked to People records to preserve the contact-to-account relationship. The Odoo ir.partner with company_type=company maps directly to the Monday.com Company object. Website domain is preserved for potential data enrichment integration.

Odoo custom fields added via Odoo Studio or ir.model.fields migrate as custom columns on the corresponding Monday.com board. Field type (char, integer, many2one, date, etc.) is mapped to the nearest Monday.com column type. Many2one references require pre-migration resolution: the referenced record must exist in Monday.com before the custom column value can be populated. Complex relational fields (many2many, one2many) are stored as text arrays or multi-select columns with a note in the migration inventory explaining the simplification.

Tags on Odoo Contacts, Leads, and Opportunities migrate as tag values in a Monday.com Tags or Labels column. Odoo stores tags in a separate ir.attachment model; we flatten them to a simple string list per record. Tag deduplication is applied during migration to normalize variations in casing and spacing.