Migrate from Pipedrive to Odoo CRM

Pipedrive Persons map to Odoo Contacts (res.partner with customer_rank > 0). The Person's name, email, phone, and address fields map to Odoo's name, email, phone, and address fields. We extract the Organization linked to the Person and resolve it to the Contact's parent partner (commercial partner_id) before insert so that company-level data is linked correctly. If the Person has no linked Organization, the Contact is created without a parent and the partner_id is set to the Contact's own ID.

Pipedrive Organizations map to Odoo Company records (res.partner with is_company=True). The Organization's name, address, phone, and custom fields map to the Company record. We create all Organizations before Persons so that the parent partner lookup succeeds when processing Person-to-Contact records. Organization-linked Persons receive the Company as their commercial partner_id after the Company exists in the destination.

Pipedrive Leads are a separate pool that repoint into the deal flow on qualification. In Odoo, unqualified prospects map to CRM Lead records. We merge all Pipedrive Leads into crm.lead with type='lead' before Deal migration. The Lead's status, custom fields, owner, and tags migrate. Pipeline assignment from Pipedrive is preserved in Odoo's crm.lead team_id and tag_ids. If Odoo is configured with only Opportunities (no separate Lead stage), we migrate Leads as Opportunities with type='opportunity' and flag the customer for Odoo Studio configuration.

Pipedrive Deals map to Odoo Opportunities. The deal title becomes the Opportunity name, monetary value maps to planned_revenue, and stage maps to stage_id with the stage name matched to the destination Odoo pipeline stage. The linked Person resolves to the Opportunity's contact_id; the linked Organization resolves to partner_id. Lost reasons and close dates migrate to lost_reason and date_closed. Pipeline-specific custom fields carry over via the Odoo custom field mapping.

Each Pipedrive pipeline becomes an Odoo Sales Team (crm.team) with its own stage sequence. Stage names, order, and probability percentages migrate to crm.stage records under the corresponding team. If the destination has fewer stages than the source, we collapse stages by probability grouping and document the mapping in the pre-flight report.

Pipedrive Activities (calls, meetings, tasks, notes) map to Odoo's mail.message records linked to the corresponding crm.lead. Activity type maps to a custom field activity_type__c on mail.message; the body field carries note text or call/meeting metadata. For task-type activities with due dates, we create project.task records under the CRM project's task pipeline if the Odoo installation has the Project module enabled.

Pipedrive Products map to Odoo Product Templates. Product name, SKU (hs_sku equivalent), list_price, and standard_cost migrate. Product categories map to Odoo's product.category. If the destination Odoo instance has the Inventory module enabled, we also create product.product variants where applicable.

Pipedrive Deal-Product associations (line items with quantity and price) map to Odoo Sale Order Lines attached to the migrated Opportunity. We create a draft Sale Order (sale.order) linked to the Opportunity's partner and map each Deal product line to a sale.order.line with the correct product, quantity, and price. If Odoo Sales is not installed, we preserve the association as Opportunity Line records in custom fields.

Pipedrive assigns each custom field a 40-character account-specific hash key. We resolve each hash to its human-readable label from the source account's field metadata, match by label and data type to an existing Odoo field or create a new ir.model.fields record in the destination. Text fields map to char/text, date fields to date, numeric fields to float or monetary, and dropdown fields to selection fields. We do not preserve the hash key itself; only the label and values migrate.

Pipedrive tags on Persons, Organizations, and Deals map to Odoo CRM Tags. We extract all unique tag names from the source, create the corresponding crm.tag records, and apply tag_ids to the migrated crm.lead and res.partner records. Tags are matched by name string; Odoo creates any missing tags at migration time.

Pipedrive Owners map to Odoo Users by email address match. We extract every distinct owner_id referenced on Persons, Organizations, Deals, Leads, and Activities, resolve by email against the destination Odoo User list, and re-assign the responsible_user_id on migrated records. Owners without a matching Odoo User are placed in a reconciliation queue for the customer's admin to provision before record import completes.

Pipedrive Notes (standalone content entries) map to Odoo mail.message records with subtype='mt_note'. The note body migrates as message_body. If the note is linked to a Person, Organization, or Deal, we re-attach the message to the migrated crm.lead or res.partner record using the external_id mapping established during earlier phases.