Migrate from Odoo Marketing Automation to Salesforce Sales Cloud

Odoo Contacts (res.partner model) map to Salesforce Lead if they represent unqualified prospects or to Salesforce Contact attached to an Account if they are sales-qualified. We apply a split rule based on Odoo's contact_type (contact vs address) and any lifecycle or stage tags present. The original Odoo partner ID is preserved in a custom field odoo_partner_id__c for audit and cross-reference. Account (company) data is resolved first so that the AccountId lookup is available at Contact insert time.

Odoo CRM Leads map directly to Salesforce Lead. Lead name, email, phone, company name, source, priority, and expected closing date transfer to the equivalent Salesforce Lead fields. Stage names vary by Odoo database and require a mapping table. Any custom Lead fields created via Odoo Studio are migrated as Salesforce custom fields with preserved field types from ir.model.fields metadata.

Odoo CRM Opportunities map to Salesforce Opportunity. The opportunity name, stage, expected revenue, partner (account), and lost reason transfer directly. Odoo stage names require explicit mapping to Salesforce StageName values, and probability percentages are rounded to the nearest integer. The AccountId and OwnerId are resolved via parent-record lookup before Opportunity insert.

Odoo Marketing Automation Campaigns are the top-level container for automation rules. We migrate campaign name, target model (Contact, Lead, Sales Order), audience domain filter, and campaign state. On Salesforce, each Odoo Campaign becomes a Salesforce Campaign with Type set to the Odoo campaign_type or a default of Marketing Automation Migration. Active participants from Odoo trace logs become Campaign Members on Salesforce with Status = Responded.

Odoo Automation Rules are the workflow definitions with trigger type (time-based, email event, server action), filter domain, and action chain. We migrate the rule name, trigger type, condition domain, and full activity sequence as structured metadata. Python Code activity blocks and Server Action blocks (which reference Odoo-specific models) are flagged individually and excluded from import. We deliver a written inventory of every rule with its trigger, conditions, timing, activity chain, and a recommended Salesforce Flow equivalent for the customer's admin to rebuild. Automation rules cannot execute in Salesforce without a complete manual rebuild in Flow.

Individual steps within an Odoo Automation Rule (Send Email, Update Record, Create Task, Python Code, Server Action) are mapped to Salesforce Flow elements. Send Email maps to a Send Email action in Flow or Salesforce email templates. Update Record maps to Update Records. Create Task maps to Create Records on the Task object. Python Code and Server Action are flagged with no Salesforce equivalent. The activity timing (trigger, delay in days/hours) and child activity links are preserved in the written inventory for rebuild context.

Odoo Mass Mailings (tracked email send records from the Email Marketing app) migrate as Salesforce Campaign records with a linked Task activity for each send event. Subject, body HTML, scheduled date, recipient count, and trace data (opens, clicks, bounces) migrate as Salesforce Campaign fields and custom tracking fields. Recipient lists are resolved via Contact or Lead ID lookup against the migrated record set. Note that Odoo's mass mailing tracking is not real-time; the trace data reflects the state at export time.

Odoo Email Templates (stored in the Email Marketing app) are used by both Email Marketing and Marketing Automation. We migrate template name, subject, body HTML (with inline images and variables preserved as string placeholders), and attachment references. Variable placeholders in Odoo syntax (${object.field}) are documented separately for the customer's admin to convert to Salesforce merge field syntax ({{!Contact.Field}}) during the template rebuild phase.

Odoo user accounts are referenced as create_uid, write_uid, and assignees on CRM records and automation rules. We map user login, name, and active status. Owners without a matching Salesforce User record go to a reconciliation queue for the customer's admin to provision before record import proceeds. Active Salesforce Users are required for OwnerId resolution on Opportunity and Task records.

Tags on Contacts, Leads, and Opportunities are stored in Odoo's ir.model.data as a separate related table. We flatten the tag list per record to a string array and map to Salesforce multi-select picklist fields on the target object. The customer chooses whether to consolidate tags into a single multi-select or split into multiple boolean fields during scoping.

Custom fields added via Odoo Studio or ir.model.fields are migrated as key-value pairs on the parent record. The field type (char, integer, many2one, date, boolean, etc.) is preserved from ir.model.fields metadata and mapped to the equivalent Salesforce field type. Many2one relations are resolved via parent-record ID lookup if the referenced object is in scope, or stored as a text ID reference if the target object is out of migration scope.

SMS Templates from the Odoo SMS Marketing app are migrated as a documented SMS template inventory with content, variable placeholders, and usage context. Salesforce does not have a native SMS template object in Sales Cloud; SMS actions are handled via Flow with third-party SMS integrations (Twilio, Peltexx) or Marketing Cloud Mobile Connect. We deliver the SMS template content for the customer's admin to configure in their chosen SMS integration.