Odoo CRM to Pipedrive migration
We migrate Contacts, Companies, Leads, Opportunities, Activities, and Tags from Odoo CRM into Pipedrive with the Lead-versus-Opportunity type split resolved before any records load, pipeline stages configured to match Odoo's stage probability model, and every Odoo custom field type mapped to a Pipedrive-equivalent field or documented as a manual step.
FlitStack AI migrates persons, organizations, leads, deals and pipeline stages from Odoo CRM to Pipedrive, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Odoo CRM to Pipedrive?
Moving from Odoo CRM to Pipedrive means restructuring a relational ERP data model (crm.lead, res.partner, crm.stage, crm.team) into Pipedrive's two-object People-and-Organizations schema with Deals as the pipeline unit.
Read the full summary
Odoo's dual Lead and Opportunity types both map into Pipedrive, but only Deals carry expected revenue and probability. We split Odoo type=lead records into Pipedrive Leads (Advanced+ tier) and type=opportunity records into Deals, with Odoo's stage_id mapped to Pipedrive stage_order and stage_name. Contacts (res.partner) map to Pipedrive People, with the company_id relation resolved against the Organizations import. Activities (mail.activity) migrate as Pipedrive Activities with user assignment and date preservation. Automation rules, lead scoring rules, Enterprise-only modules, and quotation/order data do not migrate; we deliver structured data exports and rebuild guides for each so the customer's admin can reconstruct them in Pipedrive.
Contacts / Partners (res.partner) → Person
Odoo res.partner records with partner_type not equal to 'company' map to Pipedrive Person.
How it maps
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.
Companies (res.partner with partner_type='company') → Organization
Odoo res.partner records with partner_type='company' map to Pipedrive Organization.
How it maps
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.
Leads (crm.lead, type='lead') → Lead (Leads Inbox)
Odoo Leads with type='lead' map to Pipedrive Lead Inbox.
How it maps
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.
Opportunities (crm.lead, type='opportunity') → Deal
Odoo Opportunities (crm.lead with type='opportunity') map to Pipedrive Deals.
How it maps
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.
Pipeline Stages (crm.stage) → Pipeline Stage
Odoo crm.stage records per team map to Pipedrive pipeline stages.
How it maps
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.
Sales Teams (crm.team) → Team
Odoo crm.team records map to Pipedrive Teams.
How it maps
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.
- ContactsPerson1:1
- CompaniesOrganization1:1
- LeadsLeadsplit
- OpportunitiesDeal1:1
- Pipeline StagesPipeline Stagetransformed
- Sales TeamsTeamtransformed
+ 5 more in the mapping below
How Odoo CRM and Pipedrive differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Odoo CRM | Pipedrive |
|---|---|---|
| Lead vs Deal model | Separate crm.lead objects with type='lead' and type='opportunity' | Pipedrive Lead Inbox (Advanced+) and Deals as separate pipeline units |
| Contact model | Single res.partner model for contacts and companies | Separate Person and Organization objects with a required Organization link |
| Platform type | Full ERP suite with CRM as one module among 40+ apps | Sales-focused CRM with pipeline management as the primary workflow |
| Custom field support | Studio and custom addon XML columns, full relational types | Basic field types (text, number, date, select, multiselect, numeric); relational types need configuration |
| Automation | Studio automation rules, server actions (Enterprise-exclusive) | Visual Workflow Automation builder, no Python-level actions |
| Pricing model | Per-user per app stack with Enterprise all-in tier | Per-seat tiers from $24 to $129/user/month with add-on marketplace |
| Source edition dependency | Community (free), Online, Odoo.sh, Enterprise — each with different API access | Cloud-only with API available on all tiers |
What to watch for in a Odoo CRM to Pipedrive migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Lead versus Opportunity type split requires tier-aware mapping
Odoo stores Leads and Opportunities in the same crm.lead table with a type field distinguishing them.
How we handle it
Pipedrive separates Leads (Leads Inbox) from Deals. The Leads Inbox feature is available only on Advanced tier and above. If the destination Pipedrive account is on Essential or Lite, Odoo type='lead' records must be reclassified as Deals with a placeholder stage rather than flowing into the Lead Inbox. We check the destination tier during discovery and configure the split accordingly before any records load.
Organization link requirement on Pipedrive Deals
Pipedrive Deals require a linked Organization (or both Person and Organization).
How we handle it
Odoo crm.lead records with company_id set must resolve that foreign key to a Pipedrive Organization after the Organizations batch completes. If the company_id is null in Odoo, we create a placeholder Organization or flag the Deal for manual Organization assignment during reconciliation. Records without any linked organization cannot be imported as Deals in Pipedrive without violating the schema requirement.
Automation rules and lead scoring do not migrate between platforms
Odoo CRM automation rules (base.action.rule, ir.actions.server scoped to CRM) are Enterprise-exclusive and architecturally incompatible with Pipedrive Workflow Automation.
How we handle it
Lead scoring rules (crm.scoring.rule) are Odoo Enterprise AI features with no Pipedrive equivalent. We do not migrate these as code. We deliver a written inventory of every active automation rule and lead scoring model, with the trigger conditions, actions, and a recommended Pipedrive Workflow Automation equivalent. The customer's admin rebuilds automations post-migration. Enterprise-only module indicators are stripped from any data exports.
Odoo custom fields may reference relational models without Pipedrive equivalents
Odoo custom fields defined via Studio or custom addon XML can reference other Odoo models via many2one (e.g., product_id, industry classification, custom project lookup).
How we handle it
Pipedrive custom fields support basic types but not relational cross-object links. We extract the field definition and pre-create Pipedrive fields, but Odoo many2one values referencing models with no Pipedrive equivalent (e.g., Odoo-specific product variants) are exported as structured label text and flagged for manual relinking post-migration.
Pipedrive API rate limits constrain bulk activity migration
Pipedrive's API enforces rate limits on the /activities endpoint that vary by tier.
How we handle it
Large mail.activity migrations (over 50,000 records) require chunking and backoff handling. We use Pipedrive's bulk insert endpoint (/bulkActivities) where available and paginate individual activity inserts on remaining records. Without chunking, API responses return 429 status and records are silently dropped.
How the migration runs
Discovery and source audit
We connect to the Odoo PostgreSQL database (direct read-only connection for self-hosted or Community; XML-RPC for Odoo Online or Odoo.sh on Enterprise Custom plan) and audit crm.lead, res.partner, crm.stage, crm.team, crm.tag, mail.activity, and ir.attachment record counts.
What this step covers
We extract the Odoo version (Community vs Online vs Odoo.sh), identify Enterprise-only modules installed, and enumerate custom fields via ir.model.fields. The output is a written discovery report with record counts, field inventory, and a Lead-versus-Opportunity split plan.
Pipedrive account configuration and field pre-creation
We configure the destination Pipedrive account: create pipelines and stages matching the Odoo crm.stage model, set stage probabilities, create Teams matching crm.team membership, and pre-create all custom fields (from the custom field audit) before any data loads.
What this step covers
Custom fields are created via Pipedrive's field API using the mapped field types. Labels corresponding to Odoo crm.tag values are created in Pipedrive during this phase.
Test migration into Pipedrive sandbox
We run a full test migration into a Pipedrive trial account or a dedicated migration sandbox using representative data volume.
What this step covers
We validate the Lead-versus-Opportunity split logic, verify Organization assignment on Deals, confirm activity timelines are linked to the correct parent records, and reconcile record counts against the Odoo source. The customer reviews 25-50 randomly sampled records and approves the mapping before production migration begins.
Record migration in dependency order
We migrate records in strict dependency order: Organizations first (from Odoo res.partner companies), then Persons (with OrganizationId resolved after Organizations complete), then Leads and Deals (with OrganizationId and PersonId resolved), then Activities, then Attachments, then Tags.
What this step covers
The crm.lead type field is evaluated at migration time to route each record to the correct Pipedrive object (Lead or Deal). Owner resolution maps Odoo user_id to Pipedrive user by email. Each batch emits a row-count reconciliation report before the next batch starts.
Cutover and production validation
We coordinate a cutover window with the customer.
What this step covers
Odoo CRM write access is suspended during the window. A final delta migration captures any records modified during the migration window. We validate record counts (Organizations, Persons, Leads, Deals, Activities) against the source audit totals and spot-check field mappings on 20-30 random records. Any failed records are reviewed, corrected, and retried within the cutover window.
Post-migration handoff and automation rebuild guide
We deliver the post-migration inventory document containing the quotation CSV export, automation rule inventory, custom field mapping notes, and Pipedrive Workflow Automation rebuild recommendations.
What this step covers
We support a five-business-day hypercare window for reconciliation issues raised by the customer's team. We do not rebuild Odoo automation rules or quotation templates inside the migration scope; those are separate tasks for the customer's Pipedrive admin or a Pipedrive implementation partner.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Pricing reflects the technical complexity of extracting from Odoo's PostgreSQL database, resolving the crm.lead type split, mapping custom fields, and loading through Pipedrive's REST API. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Odoo CRM to Pipedrive →Why teams move from Odoo CRM to Pipedrive
- Odoo CRM is an ERP module built into a full business suite; Pipedrive is purpose-built for sales pipeline management. Reviews on Reddit and G2 consistently cite Odoo's CRM as underdeveloped relative to dedicated sales CRMs, noting that the Kanban pipeline, activity tracking, and deal forecasting feel like secondary features rather than primary design concerns. Teams that choose Pipedrive do so because every screen, report, and action is oriented around moving deals through a pipeline rather than managing a broader business operation.
- Odoo's modular pricing stacks rapidly. A team using CRM plus one additional module (Accounting, Inventory, or Sales) quickly reaches $31-47 per user per month before implementation costs of $4,500-$10,000. Pipedrive's entry Essential tier at $24 per user per month covers core CRM functionality without requiring additional modules, and the Advanced tier ($49) includes the Lead Inbox, giving teams a cleaner migration path from Odoo's lead management without paying for an ERP framework they no longer need.
- Odoo's email and Gmail integration is repeatedly cited as unreliable across G2 reviews, Reddit threads, and comparison articles — threads drop, conversations scatter across inboxes, and the sync breaks under common configurations. Pipedrive's Smart Email BCC and native Gmail/Outlook integrations are described as more reliable for keeping the activity timeline connected to the right deal without manual re-linking or lost correspondence.
- Odoo.sh version gating and Enterprise-only module restrictions create migration blockers that compound over time. Teams running Odoo.sh Enterprise who want to reduce cost by moving to Odoo Community face a known incompatibility: the PostgreSQL dump marks Enterprise-only modules as installed but they cannot install on Community, causing UI crashes on restore. Moving to Pipedrive avoids the Odoo edition boundary entirely and gives teams a clean cloud-native destination with no infrastructure management overhead.
- Setup complexity and version upgrade risk increase with every Odoo release. Between major Odoo versions, custom module XML view definitions frequently break, custom field ORM definitions can lose their application context, and Odoo.sh trial databases run on non-deployable versions (e.g., 18.3) that Odoo.sh cannot accept directly. Teams with active custom development cite this as a recurring maintenance burden that Pipedrive's SaaS model eliminates entirely.
Questions, answered
Odoo CRM to Pipedrive migration questions
How long does an Odoo CRM to Pipedrive migration take?
Most Odoo CRM to Pipedrive migrations complete in three to five weeks for accounts with fewer than 15,000 Contacts and 5,000 Opportunities and no complex custom field schemas. Migrations with large activity histories (over 200,000 mail.activity records), multiple Odoo sales teams, or extensive custom field definitions requiring type-by-type mapping move to six to eight weeks. The Lead-versus-Opportunity split and parent-record lookup resolution are the primary timeline drivers in either case.
Do Odoo automation rules and lead scoring migrate to Pipedrive Workflow Automation?
No. Odoo automation rules and server actions are Enterprise-exclusive and architecturally incompatible with Pipedrive's visual Workflow Automation builder. Lead scoring rules depend on Odoo's proprietary AI infrastructure and have no equivalent in Pipedrive. We do not migrate automation logic as executable code. We deliver a written inventory of every active Odoo automation rule and lead scoring model, with trigger conditions, action chains, and a recommended Pipedrive Workflow Automation equivalent. The customer's Pipedrive admin rebuilds these post-migration. Enterprise-only module indicators are stripped from data exports to avoid schema conflicts.
How does the Odoo Lead versus Opportunity split work in Pipedrive?
Odoo stores both Lead and Opportunity records in crm.lead with a type field. Pipedrive uses separate objects: Deals for Opportunities and Leads for unqualified prospects (Leads Inbox). We evaluate the crm.lead type field at migration time and route each record accordingly. Odoo Leads with type='lead' go to Pipedrive Leads (Advanced+ tier only); Odoo Opportunities with type='opportunity' go to Pipedrive Deals with stage, expected revenue, and probability preserved. If the destination Pipedrive account is on Essential or Lite, Odoo Leads are reclassified as Deals with a placeholder stage and flagged for manual review.
Can we migrate Odoo quotations and sale orders to Pipedrive?
Odoo sale.order and sale.order.line records do not have a native Pipedrive equivalent. Pipedrive Smart Docs (Professional+ tier) provides quote templates but is not seeded with external quotation data. We export sale.order and sale.order.line records as a structured CSV with product names, quantities, unit prices, taxes, and terms, and deliver a Pipedrive Smart Docs rebuild guide. The quotation rebuild is a separate manual step for the customer's Pipedrive admin or an implementation partner; it is not included in the standard migration scope.
What happens to Odoo custom fields during migration?
Odoo custom fields on crm.lead defined via Studio or custom addon XML are fully exportable from PostgreSQL. We create equivalent Pipedrive custom fields during pre-migration setup and map field types accordingly: selection fields become Pipedrive select or multiselect fields, many2one fields require a corresponding Pipedrive label or pre-created Organization, and many2many fields become label or multiselect. Custom fields referencing Odoo-specific relational models with no Pipedrive equivalent are exported as structured text and flagged as a manual relinking step. The custom field mapping plan is validated during the sandbox migration before production cutover.
How are Odoo email conversations and activity history handled?
Odoo email threads (mail.message records linked to crm.lead) and activity logs (mail.activity) are migrated to Pipedrive Activities. Emails become Pipedrive Activities with the email body and metadata preserved; calls become Task activities with duration; meetings become Event activities with attendee list. We resolve the Odoo user_id responsible for each activity to a Pipedrive user by email match. Activity timelines are ordered by the original Odoo create_date to preserve sequence. Pipedrive's API rate limits on the activities endpoint require chunking for migrations over 50,000 records.
Related migrations
Pipedrive implementation
Set up Pipedrive and migrate into it as one engagement.
See the service → Pipedrive to Odoo CRMThe same pair in reverse Rocket Matter to PipedriveMapping · history · rollbackAttio to PipedriveMapping · history · rollbackSmartDesk to PipedriveMapping · history · rollbackEntera to PipedriveMapping · history · rollbackJobber to PipedriveMapping · history · rollbackCivicrm to PipedriveMapping · history · rollback Odoo CRM to Dynamics 365Mapping · history · rollbackOdoo CRM to Zoho CRMMapping · history · rollbackOdoo CRM to HubSpotMapping · history · rollbackSources: official documentation
- Importing data into Pipedrive with spreadsheets — Knowledge Base
- Updating Pipedrive data with a spreadsheet — Knowledge Base
- 5 Simple CRM Data Migration Methods — Pipedrive Blog
- Option fields and label-vs-ID matching — Pipedrive Knowledge Base
- Export and import data — Odoo 19.0 documentation
- Import products — Odoo 19.0 documentation
- Odoo Online programmatic throughput limits — Odoo Forum
Get a quote
Moving from Odoo CRM to Pipedrive?
Tell us roughly how many records and objects you have. We scope the mapping and the Pipedrive setup with you, then send a quote.
Get a quote