Migrate from Odoo CRM to Pipedrive

Odoo res.partner records with partner_type not equal to 'company' map to Pipedrive Person. The name, email, phone, mobile, website, street, city, country_id, and function fields migrate directly. The company_id foreign key is held as an Organization lookup to resolve after the Organizations batch loads. We extract the crm.lead partner_id references and remap them to Pipedrive Person IDs after the Person batch completes.

Odoo res.partner records with partner_type='company' map to Pipedrive Organization. The website domain is used as the dedupe key during import to avoid duplicate Organizations. Odoo's parent_id hierarchical company structure does not map to Pipedrive's flat Organization model; we flag multi-level company hierarchies during discovery and recommend flattening to a single Organization level for the Pipedrive migration.

Odoo Leads with type='lead' map to Pipedrive Lead Inbox. This mapping is available only on Pipedrive Advanced, Professional, Power, and Enterprise tiers. We check the destination tier during scoping and flag the Lead Inbox unavailability if the customer selects Essential or Lite. Lead fields mapped include name, contact_name, email_from, phone, source_id (as label), and description. The original Odoo lead stage (new, pending, lost) maps to a custom label field in Pipedrive.

Odoo Opportunities (crm.lead with type='opportunity') map to Pipedrive Deals. The expected_revenue field migrates to Pipedrive's numeric value field, date_deadline maps to close_time, and probability migrates to Pipedrive probability percentage. The lost_reason field from Odoo custom fields becomes a custom Pipedrive field. Deals are linked to their resolved Organization (from company_id) and Person (from partner_id) after both batches complete.

Odoo crm.stage records per team map to Pipedrive pipeline stages. We configure Pipedrive stages during setup to match Odoo's stage_name, stage sequence order, and stage probability values. Stage probability from Odoo (probability field on crm.stage) maps to Pipedrive stage probability. If the customer has multiple Odoo sales teams, we create separate Pipedrive pipelines and assign the appropriate Deals per team mapping.

Odoo crm.team records map to Pipedrive Teams. We create the Pipedrive Teams during account configuration, assign the team name and member list from Odoo user_ids, and link Deals to the appropriate Team. If Pipedrive is on a tier without Team assignments, Deals are scoped to the Account-level Owner without team-level isolation.

Odoo mail.activity records linked to crm.lead migrate to Pipedrive Activity records. Activity type (call, meeting, todo) maps to Pipedrive Activity type, date_deadline maps to due_date, and the activity note migrates to the activity subject or note field. We resolve the user_id (activity responsible) to the Pipedrive user by email match. Any HubSpot-style activity_type enumeration is validated against Pipedrive's supported activity types before insert.

Odoo ir.attachment records linked to crm.lead are stored in the Odoo filestore (binary column or file path on disk). We download attachments from the PostgreSQL blob store or filestore, base64-encode each file, and attach it as a Pipedrive Note with a file link. Large attachment volumes are chunked separately. The ir_attachment res_model and res_id fields are used to link each attachment to the correct Pipedrive Deal or Person after the parent record mapping is complete.

Odoo crm.tag records applied to crm.lead migrate to Pipedrive Labels. Labels in Pipedrive are multi-select fields on Deals and Persons. We import tag names as Label values and attach them to the corresponding Deals and Persons. Tag volume is validated against Pipedrive's label UX guidelines; we recommend fewer than 30 distinct tags in the destination to maintain a clean Pipedrive interface.

Odoo custom fields on crm.lead defined via Studio or custom addon XML are stored as columns in the PostgreSQL table. We extract the field definition (field type, selection options, relational model) and create equivalent Pipedrive custom fields during pre-migration setup. Selection fields map to Pipedrive select or multiselect. Many2one relational fields (e.g., industry, country) require pre-creating the corresponding Pipedrive Organizations or a label field. Many2many fields map to Pipedrive label or multiselect. Odoo relational field types not natively supported in Pipedrive are flagged as manual steps with a structured export of the related record IDs.

Odoo sale.order records do not have a native Pipedrive equivalent. Pipedrive Smart Docs (Professional+ tier) provides quote templates but is not seeded with Odoo quotation data. We export sale.order and sale.order.line records as a structured CSV with product names, quantities, unit prices, taxes, and terms. We deliver a Pipedrive Smart Docs rebuild guide with templates and recommended pricing table configuration. Quote data migration is not included in standard scope; it is a separate line item or customer-admin task.