Migrate from Odoo Marketing Automation to Pipedrive

Odoo Contacts (where is_company = False and type = 'contact') map to Pipedrive Person. We extract name, email, phone, mobile, street, city, state, country, and website from the partner record. The Odoo partner ID is preserved in a custom field odoo_partner_id__c for reconciliation and audit. Active status maps to a Pipedrive custom field since Pipedrive People do not have a soft-delete equivalent.

Odoo Contacts where is_company = True map to Pipedrive Organization. Company name, website, street, city, state, country, and phone migrate directly. The Organization is created before any related Person records so that the Organization ID lookup is satisfied at Person import time. Odoo partner commercial fields (commercial_partner_id) collapse to a single Organization per corporate entity.

Odoo Leads with type = 'lead' map to Pipedrive's native Lead inbox object. We map title, contact_name, email_from, phone, mobile, source (odoo crm.lead.source), lost_reason, priority, and stage_name. The Odoo lead ID is preserved in a custom field odoo_lead_id__c. Leads without an email address are flagged during scoping because Pipedrive Lead requires an email or phone for deduplication.

Odoo Opportunities (type = 'opportunity') map to Pipedrive Deal. We map name, planned_revenue, stage_name, probability, date_deadline, partner_id (resolved to Organization ID), user_id (resolved to Pipedrive User ID), and lost_reason. Stage names vary by Odoo database and require a mapping table to Pipedrive pipeline stages that we configure before migration.

Odoo Campaign records have no direct Pipedrive equivalent. We migrate the campaign name, target model (Contact or Lead), audience domain filter criteria, and campaign state as custom fields on the relevant Person or Organization records. The campaign association is computed by evaluating the audience domain filter against the migrated partner records. A separate written campaign inventory document lists every Odoo Campaign with its enrollment rules for the customer to rebuild in Pipedrive Workflows or a connected marketing tool.

Automation Rules migrate as a written inventory, not as executable Pipedrive Workflows. Each rule's name, trigger type (time-based, email event, server action), filter domain, action chain, and active state are documented. Any rule containing a Python Code server-action activity is flagged separately as a non-replayable block that requires manual rebuild. The inventory includes the email template reference and child activity links for each rule.

Workflow Activities (Send Email, Update Record, Create Task) within each Automation Rule are documented by activity type, timing, template reference, and child activity hierarchy. Email template references are resolved to the Odoo email.template records that are migrated separately. Activities with Update Record or Create Task actions are mapped to Pipedrive Workflow actions in the automation inventory.

Odoo Mass Mailings (subject, HTML body, scheduled_date, recipient_count) map to Pipedrive email templates under the Campaigns product. We extract the HTML body and inline images, resolving image URLs to hosted assets where possible. Recipient lists are resolved via Contact or Lead domain against the migrated People records rather than as stored recipient sets. Subject line and preview text migrate as template metadata.

Odoo Email Templates (shared between Email Marketing and Marketing Automation) migrate as Pipedrive email templates. Template name, subject, body HTML, and attachment references transfer. Inline images are resolved as hosted URLs. Variable placeholders (Odoo's {{object.field}} syntax) are preserved as plain text in the Pipedrive template with a note flagging which dynamic fields require manual reconfiguration in Pipedrive's template editor.

Odoo stores tags in a separate ir.model.data entry set, referenced as many2manytags on Contact and Lead. We flatten tags to a simple string list and map them to a Pipedrive Person or Organization custom field of type multiselect. The customer chooses during scoping whether tags become a single multiselect custom field or multiple single-select custom fields, depending on tag volume and reporting needs.

Odoo custom fields added via Odoo Studio or ir.model.fields are migrated as key-value pairs on the parent record. Field type (char, integer, float, many2one, many2many, date, datetime) is preserved from the ir.model.fields metadata and mapped to the equivalent Pipedrive custom field type. Many2one references to other models (e.g., custom category lookups) are resolved to ID strings in Pipedrive custom fields; the customer resolves the actual reference during deal review.

Odoo user accounts are referenced as create_uid, write_uid, and assignees on CRM records and Automation Rules. We map user login email and active status. Owner assignment on Deals and Leads resolves by email match against the Pipedrive User table. Any Odoo user without a matching Pipedrive User goes to a reconciliation queue for the customer admin to provision before record import resumes.