Migrate from Odoo Marketing Automation to Zoho CRM

Odoo Contacts map to Zoho CRM Contacts. Both platforms store name, email, phone, company, and tags on the Contact record. The key difference is that Odoo uses a unified partner model where Contact and Lead share the same res.partner table with a type field distinguishing company contacts from individual leads. We resolve the type=contact versus type=person split at migration time and import accordingly. Custom fields on Contact (added via Odoo Studio or ir.model.fields) migrate as key-value pairs into Zoho custom fields of equivalent type.

Odoo Leads (res.partner records with type=person and not assigned to a company) map to Zoho CRM Leads. Lead name, email, phone, source, stage, priority, and expected closing date transfer directly. Odoo Lead stage names are database-specific and require a mapping table we build during discovery. Zoho's Lead Status picklist values are configured in the destination org and mapped from Odoo's stage labels.

Odoo CRM Opportunities map to Zoho CRM Deals. Deal name, stage, expected revenue, partner (account), lost reason, and priority migrate directly. Odoo stage names map to Zoho Deal Stage values via a configuration mapping we create during discovery. Owner assignment migrates by resolving Odoo create_uid and user_id to Zoho Users by email match.

Odoo Marketing Automation Campaigns map to Zoho CRM Campaigns as the top-level container. Campaign name, target model (Contact, Lead, Sales Order), audience domain filter, and state transfer. Campaign traces and activity logs are reviewed individually—Zoho Campaign records store Member Status and Response fields that partially cover trace data, but detailed activity timing logs require manual review or a Zoho Analytics extension.

Odoo Automation Rules (the workflow definitions with triggers, conditions, and action chains) do not migrate as code to Zoho Workflow Rules because the trigger types, condition syntax, and action models differ structurally. We deliver a written inventory of every Automation Rule including its trigger type (time-based, email event, server action), filter domain, action chain, and activity count. Python Code activity blocks are flagged explicitly as manual-rebuild items. Email-event triggers map conceptually to Zoho Workflow Rule triggers but require manual reconstruction in Zoho's workflow builder.

Odoo Workflow Activities (individual steps within an Automation Rule: Send Email, Update Record, Create Task, Server Action) are documented as part of the automation inventory. Send Email activities map to Zoho email template references; Update Record activities map to field-update workflow actions; Create Task activities map to Zoho task creation actions. Activities containing Python Code or SMS steps are flagged for manual rebuild in Zoho's Deluge scripting environment.

Odoo Mass Mailings (the email-sending records from the Email Marketing app) map to Zoho CRM Campaign records with an Email Campaign subtype. Subject, body HTML, scheduled date, and recipient count transfer. Recipient lists are resolved via Contact or Lead domain queries against the imported Contact and Lead records. Inline images in HTML bodies are flagged as attachment references that require re-upload in Zoho's email template editor.

Odoo Email Templates (stored in the Email Marketing app and referenced by Automation Rules) map to Zoho CRM Email Templates. Template name, subject, and body HTML transfer. Merge fields use Odoo's ${field.name} syntax and require conversion to Zoho's ${Contact.FieldName} or ${Lead.FieldName} syntax during transformation. Inline images and attachments are flagged as separate assets requiring manual re-insertion in Zoho's template editor.

Custom fields added via Odoo Studio or ir.model.fields migrate as key-value pairs on their parent record. We preserve the field type (char, integer, many2one, date, etc.) from the ir.model.fields metadata and map to the closest Zoho field type during schema design. Many2one fields (foreign key references to other Odoo models) require pre-import of the referenced records so that the Zoho lookup can be resolved at migration time.

Odoo user accounts referenced as create_uid, write_uid, and assignees on CRM records and automation rules map to Zoho CRM Users. We match by email address. Any Odoo user without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active and inactive status transfers to the Zoho User record.

Tags on Odoo Contacts, Leads, and Opportunities are stored in a separate ir.attachment model and flattened to a simple string list per record. We migrate the tag names as a multi-select field on the corresponding Zoho record. Tag collision handling uses a name-based merge: if the same tag name already exists in Zoho, we reference the existing tag rather than creating a duplicate.