Odoo CRM to Salesforce migration
We migrate Contacts, Leads, Opportunities, and Activity history from Odoo CRM into Salesforce Sales Cloud, resolving the Lead-Opportunity split that Odoo conflates in a single crm.lead table, splitting the res.partner model into Account and Contact, and mapping pipeline stages and Sales Teams into the correct Salesforce objects before cutover.
FlitStack AI migrates account and contacts, leads, opportunities, opportunity stages and public group or custom territory fields from Odoo CRM to Salesforce, 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 Salesforce?
Moving from Odoo CRM to Salesforce Sales Cloud is a structural migration because Odoo stores Leads and Opportunities in a single crm.lead table differentiated only by a type field, while Salesforce separates them into distinct Lead and Opportunity objects.
Read the full summary
The more complex challenge is Odoo's res.partner model, which is polymorphic — it stores both companies and individual contacts in one table — and Salesforce requires Accounts and Contacts as separate objects with a parent lookup relationship. We resolve the Partner split during scoping by analyzing parent_id links and contact_type fields, then map company-type partners to Account and individual-type partners to Contact with AccountId resolved. We preserve the original Odoo crm.lead type field as a custom field on both Lead and Opportunity for audit. Server Actions, automation rules, and Odoo AI lead scoring do not migrate to Salesforce Flow; we deliver a written inventory for the customer's admin to rebuild. Activity history (calls, emails, meetings, tasks) migrates through the Salesforce Bulk API 2.0 with WhoId and WhatId parent-record resolution so the timeline attaches to the correct Contact and Opportunity in the destination.
Contact / Partner → Account and Contact
Odoo res.partner is polymorphic — it stores both company records (contact_type='contact' or blank) and individual contact records linked to a company via parent_id.
How it maps
We split by analyzing parent_id chains and contact_type values: partner records with no parent_id and contact_type indicating a company become Salesforce Account records. Their children with parent_id set become Salesforce Contact records with AccountId resolved. Partner records that are standalone individuals without a parent_id company create an Account with the same name and a Contact linked to it. The Odoo partner ID is preserved in a custom field odoo_partner_id__c for reconciliation.
Lead → Lead
Odoo crm.lead records with type='lead' (not yet converted to an Opportunity) map directly to Salesforce Lead.
How it maps
The Odoo partner_id is resolved to the target Account or Contact created in step 1, and if no match exists a Contact is created inline. Email, phone, company name, source, and any custom fields map to equivalent Salesforce Lead fields. The original Odoo crm.lead ID is preserved in odoo_lead_id__c.
Opportunity → Opportunity
Odoo crm.lead records with type='opportunity' map to Salesforce Opportunity.
How it maps
The partner_id (Odoo contact) is resolved to a Salesforce Contact and Account, and AccountId is set accordingly. Fields including expected_revenue, probability, date_close, name, and description map directly. Odoo's stage_id resolves to the Salesforce Opportunity StageName via the stage mapping defined in the pipeline configuration step. The Odoo crm.lead ID is preserved in odoo_lead_id__c.
Pipeline Stage → Opportunity Stage
Odoo crm.stage values migrate as Salesforce Opportunity StageName entries with probability percentages preserved from Odoo's stage probability.
How it maps
Stage sequence order is maintained. If the customer uses multiple Odoo pipelines, we create multiple Salesforce Sales Processes and assign them to Opportunity Record Types per pipeline. Stage probability maps to StageProbability in Salesforce, rounded to the nearest allowed integer value.
Sales Team → Public Group or Custom Territory Field
Odoo crm.team groups Opportunities and assigns Leads via user_id and member_ids.
How it maps
Salesforce has no direct crm.team equivalent at standard tiers — Territory Management is an add-on. We map each Odoo team to either a Salesforce Public Group (team members as members), a custom picklist field crm_team__c on Opportunity, or a queue if territory-based routing is required. The customer selects the approach during scoping. Team-level stage configurations in Odoo become Salesforce Sales Processes assigned to Record Types.
Activity (mail.activity) → Task (TaskSubtype = Call, Email, Meeting, or generic)
Odoo mail.activity records linked to crm.lead migrate to Salesforce Task records with TaskSubtype set from Odoo's activity_type_id (call, email, meeting, or other).
How it maps
Activity date_deadline and note migrate to Task ActivityDate and Description. Owner assignment maps via email from Odoo user_id to the Salesforce User lookup. High-volume activity migrations use the Salesforce Bulk API 2.0 with WhoId and WhatId resolved to the migrated Lead, Contact, or Opportunity ID. Activity records without a resolvable parent are held in a reconciliation queue.
- ContactAccount and Contactsplit
- LeadLead1:1
- OpportunityOpportunity1:1
- Pipeline StageOpportunity Stagetransformed
- Sales TeamPublic Group or Custom Territory Fieldtransformed
- ActivityTask1:1
+ 6 more in the mapping below
How Odoo CRM and Salesforce 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 | Salesforce |
|---|---|---|
| Lead and Opportunity storage | Single crm.lead table with type field ('lead' vs 'opportunity') | Separate Lead and Opportunity objects with explicit Convert action |
| Partner model | res.partner is polymorphic: companies and contacts share one table | Separate Account and Contact objects with AccountId lookup on Contact |
| Custom fields | Stored as columns in crm.lead; defined by Studio or custom addon modules | Custom fields pre-created via Setup; referenced by API name on the object |
| Sales team model | crm.team with user_ids and stage configurations per team | Territory Management (add-on), Public Groups, or custom field; no direct crm.team equivalent |
| AI lead scoring | Enterprise-only crm.scoring.rule with proprietary algorithm | Salesforce Einstein Deal Score and Lead Scoring available from Professional tier |
| Activity model | mail.activity linked to crm.lead with activity_type_id | Task (with TaskSubtype) and Event objects; EmailMessage for email history |
| Attachment storage | ir.attachment in Odoo filestore; references via res_model and res_id | ContentDocument via Salesforce Files; linked via ContentDocumentLink |
What to watch for in a Odoo CRM to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Lead and Opportunity are one table in Odoo, two objects in Salesforce
Odoo stores both Leads and Opportunities in crm.lead, differentiated by a type field ('lead' vs 'opportunity').
How we handle it
Salesforce uses separate Lead and Opportunity objects. If the crm.lead type field is not used as the split condition, Opportunities without an AccountId (because Odoo's partner_id resolved differently) create orphaned Opportunity records in Salesforce. We define the split condition during discovery by querying distinct type values in the source database, verify the split produces clean Lead and Opportunity sets in a sandbox run, and preserve the original Odoo crm.lead type as a custom field on both destination records for audit trail integrity.
res.partner is polymorphic — Odoo companies and contacts share one table
Odoo's res.partner model holds both companies (type='company') and individual contacts (type='contact') with a parent_id link that establishes the company-contact hierarchy.
How we handle it
Salesforce requires separate Account and Contact objects. We split res.partner by analyzing parent_id and contact_type: partners with no parent_id and type indicating a company become Accounts; partners with a parent_id become Contacts with AccountId set. Contacts that are individuals with no parent_id company are handled as a special case — we create a matching Account record for them inline. This split must be resolved before any Contact import so that the AccountId foreign key is satisfied at insert time. Skipping it produces Contacts without an Account, which is valid in Salesforce but breaks standard Account-related reports.
Enterprise-only Odoo modules corrupt Community or self-hosted targets
Odoo.sh Enterprise databases include modules (CRM Enterprise, Documents, WhatsApp, Social, AI) that cannot install on Community or self-hosted Community.
How we handle it
If the migration source is an Odoo.sh Enterprise database and the destination is a Community edition or self-hosted Odoo, the PostgreSQL dump marks these modules as 'installed' in ir_module_module, causing UI crashes and missing view definitions when the database is restored. We detect and strip all Enterprise-only module rows from the ir_module_module table before any restore, and document which Enterprise features (automation rules, AI scoring, Documents) are lost in the migration. Salesforce customers are unaffected by this gotcha since they are migrating away from Odoo entirely, but it is flagged for any staged Odoo-to-Odoo intermediate target.
Custom fields lose ORM definitions if the defining addon is absent
Odoo custom fields defined via Studio or in custom addon modules are stored as columns in crm.lead and res.partner.
How we handle it
If the module that declares the field is not deployed in the target environment, the column exists in the database but has no ORM field definition, so the UI shows nothing. We export field definitions alongside the data and verify the target environment has matching field declarations before loading. For Salesforce, we pre-create custom fields before the data migration phase so that custom field data lands in typed, queryable columns rather than unknown fields. The customer must confirm whether Studio-defined fields should migrate as Salesforce custom fields or be documented as unsupported.
API access for Odoo Community is gated behind the Custom Plan
The Odoo External API (XML-RPC) is free only for Odoo Enterprise customers on the Custom Plan.
How we handle it
Community edition users running on Odoo Online or self-hosted Community do not have guaranteed API access for programmatic export. We check XML-RPC availability during discovery. When the API is unavailable, we fall back to a read-only direct PostgreSQL connection to the Odoo database, which requires the customer's database credentials and a network path to the database server. If neither XML-RPC nor PostgreSQL access is available (Odoo Online with Community edition), we use Odoo's built-in CSV export for standard fields and document the limitation for any custom fields that require direct database access.
How the migration runs
Discovery and Odoo schema audit
We audit the source Odoo database via direct PostgreSQL read access or XML-RPC (depending on edition).
What this step covers
We catalog crm.lead record counts split by type (lead vs opportunity), res.partner record counts by contact_type and parent_id relationship, crm.stage pipeline stage values, crm.team membership, mail.activity volume, ir.attachment count and filestore size, crm.tag distinct values, sale.order count, and any custom fields stored in crm.lead or res.partner. We also identify Enterprise-only installed modules via ir_module_module to flag any data from those modules that requires customer acknowledgment before migration. The discovery output is a written scope document with record counts, custom field inventory, and the res.partner splitting strategy.
Salesforce destination schema design
We design the Salesforce destination schema in a Sandbox org.
What this step covers
This includes pre-creating all custom fields (odoo_partner_id__c, odoo_lead_id__c, odoo_crm_team__c, lead_tags__c, and any custom fields from Odoo custom addons), defining Opportunity Stage entries matching the Odoo crm.stage pipeline, creating Sales Processes and Record Types per Odoo pipeline, and configuring Public Groups or the crm_team__c picklist for Odoo Sales Team mapping. Schema is deployed via Salesforce Metadata API into the Sandbox. The customer reviews the schema design and confirms the res.partner splitting logic before production migration begins.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox using production-equivalent data volume.
What this step covers
The customer reconciles record counts (Accounts, Contacts, Leads, Opportunities, Activities), spot-checks 25-50 records against the Odoo source, and reviews the Partner splitting results to confirm that no contacts are orphaned without an Account. Mapping corrections identified during sandbox reconciliation are applied to the migration scripts before the production migration. The customer signs off the sandbox results in writing before we proceed to production.
Owner reconciliation and User provisioning
We extract every distinct user_id referenced on crm.lead, crm.team, and mail.activity records and match by email against the destination Salesforce org's User table.
What this step covers
Odoo users without a matching Salesforce User are held in a reconciliation queue. The customer's Salesforce admin provisions any missing Users (active for current team members, inactive for departed users) before record import resumes. OwnerId lookups on Opportunity and Lead cannot be resolved without User records, so this step gates the production migration.
Production migration in dependency order
We run production migration in strict record-dependency order: Accounts (from company-type res.partner records), Contacts (from individual-type res.partner records with parent_id resolved to AccountId), Leads (from crm.lead with type='lead'), Opportunities (from crm.lead with type='opportunity' with AccountId and OwnerId resolved), Activities (Tasks via Bulk API 2.0 with WhoId and WhatId resolved to migrated IDs), Attachments (uploaded to Salesforce Files and linked via ContentDocumentLink), Tags (as multi-select picklist values or Topics), Custom fields (loaded into pre-created custom field columns), and Quotations (as Opportunity with Products or Quote records).
What this step covers
Each phase emits a row-count reconciliation report and the customer validates before the next phase begins.
Cutover, validation, and automation inventory handoff
We freeze Odoo write access during cutover, run a final delta migration for any records modified during the cutover window, then enable Salesforce as the system of record.
What this step covers
We validate record counts, cross-reference 25 random Opportunities against their Odoo source values, and confirm the Partner split produced no orphaned Contacts. We deliver the automation inventory document listing every active Odoo automation rule with its trigger, conditions, and recommended Salesforce Flow equivalent. We do not rebuild Odoo automation as Salesforce Flow within the migration scope; that is a separate engagement. We support a one-week hypercare window for reconciliation issues raised by the customer's sales team.
- 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
A quote scales with record volume, custom field count, and the complexity of the res.partner split into Account and Contact. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Odoo CRM to Salesforce →Why teams move from Odoo CRM to Salesforce
- Odoo CRM users on G2 and Reddit report that email and Gmail integration is unreliable — threads drop, conversations scatter across inboxes, and the sync breaks under common configurations, disrupting the sales workflow that CRM is supposed to support. Salesforce email tracking, the Outlook/Gmail integration, and Sales Cloud inbox are purpose-built for sales team email workflows and cited more consistently across enterprise reviews as reliable.
- Enterprise companies outgrow Odoo's reporting and analytics. Reviews on G2 and Capterra note that while Odoo's dashboards are functional for small teams, Salesforce Einstein AI for deal forecasting, multi-dimensional pipeline analytics across territories, and the Tableau-powered reporting engine handle complex sales operations at a depth Odoo CRM cannot match without heavy custom SQL work.
- Salesforce AppExchange has over 7,000 certified apps versus Odoo's roughly 1,500 community addons. Enterprise companies needing native ERP connectors (SAP, NetSuite), CPQ (Salesforce CPQ, Apttus), revenue intelligence (Clari, Gong), or contract lifecycle management (DocuSign CLM) move to Salesforce because the integrations are AppExchange-certified and supported directly by the vendor, rather than maintained by the Odoo community on a volunteer basis.
- Odoo Enterprise pricing stacks rapidly once multiple paid apps and users are stacked together, with reported costs of €2,600+ per year for the base Custom tier and per-user rates for each installed app on Odoo.sh. Teams moving to Salesforce Sales Cloud Professional ($75 per user per month) or Enterprise ($165 per user per month) often cite predictable per-seat pricing with no per-app charges as more transparent, particularly for organizations with 50 or more sales seats requiring multiple Odoo apps.
- Mobile-first sales teams prefer Salesforce's mobile app, which is rated more highly than Odoo's for field-ready features like offline access, camera-based business card capture, and real-time pipeline updates. Reviewers on Capterra and G2 cite Salesforce mobile as a deciding factor when the sales team operates primarily outside the office.
Questions, answered
Odoo CRM to Salesforce migration questions
How long does an Odoo CRM to Salesforce migration take?
Straightforward migrations under 10,000 Leads, 5,000 Opportunities, and 5,000 Contacts with no custom addons and a clean res.partner split typically land in three to five weeks. Migrations with custom addon fields, multi-team Sales Team mapping, large engagement histories (over 200,000 activity records), or Enterprise-only Odoo modules requiring schema analysis move to eight to fourteen weeks because of the Partner splitting step, Bulk API activity chunking, and custom field pre-creation.
Do Odoo automation rules, server actions, and AI lead scoring migrate to Salesforce Flow?
No. Odoo automation rules (base.action.rule), server actions (ir.actions.server), and AI lead scoring (crm.scoring.rule) are Enterprise-exclusive features tightly coupled to Odoo's action framework and proprietary algorithm. They do not have direct Salesforce equivalents. We do not migrate them as code. We deliver a written inventory of every active automation with its trigger object, conditions, and a recommended Salesforce Flow equivalent (record-triggered, scheduled, or screen flow) and Salesforce Einstein Lead Scoring configuration if the customer licenses it. The customer's admin or a Salesforce partner rebuilds them post-migration.
How do we handle the res.partner split into Account and Contact?
Odoo's res.partner table holds both companies and individual contacts in one table. We analyze the parent_id chain and contact_type field to determine which partners are companies (no parent, type='company' or blank) and which are individuals (parent_id pointing to a company partner). Company partners become Salesforce Account records. Individual partners become Salesforce Contact records with AccountId set to the resolved company partner Account. Standalone individuals without a parent_id company create both an Account and a Contact. The customer reviews the split results in the Sandbox phase and confirms the logic before production migration.
Do we lose historical activity data (calls, emails, meetings, tasks) during migration?
No. Odoo mail.activity records migrate to Salesforce Task records (with TaskSubtype set from activity_type_id). High-volume activity migrations use the Salesforce Bulk API 2.0 with chunking, rate-limit handling, and WhoId and WhatId resolved to the migrated Lead, Contact, Account, and Opportunity IDs. Call duration, disposition, and notes map to custom Task fields. Activity date ordering is preserved via ActivityDate. We do not migrate email attachments as individual activity records; they migrate as Salesforce Files linked to the parent record.
Can we migrate from Odoo Community (no API access) to Salesforce?
Yes. Odoo Community and Odoo Online do not guarantee XML-RPC API access. We handle this by connecting directly to the PostgreSQL database with read-only credentials. This gives us access to the full schema including custom fields defined in custom addons. The customer must provide database credentials and a network path (VPN or direct IP) to the PostgreSQL server. If neither database access nor XML-RPC is available, we fall back to Odoo's built-in CSV export for standard fields and document which custom fields require manual export from the Odoo Studio interface.
How do we migrate Odoo Sales Teams to Salesforce?
Odoo crm.team groups Opportunities and assigns team members via user_ids. Salesforce has no direct equivalent at standard Sales Cloud tiers — Territory Management is an add-on product. During scoping we offer three options: map each Odoo team to a Salesforce Public Group (team members as group members), use a custom picklist field crm_team__c on Opportunity, or use queues if territory routing is needed. The customer selects the approach based on whether they plan to use Salesforce Territory Management. We document the mapping and implement it during the schema design phase.
What happens to our Odoo quotations and sale orders?
Odoo sale.order records linked to crm.lead migrate as Salesforce Opportunity records with Products (OpportunityLineItems) if the destination is standard Sales Cloud, or as Salesforce Quote records with QuoteLineItems if the customer licenses Sales Cloud Quote management or Salesforce CPQ. Odoo sale.order.line records migrate as line items with Product2, PricebookEntry, quantity, and UnitPrice preserved. Tax and discount fields map to Salesforce equivalents where the platform supports them; any Odoo-specific fiscal or tax logic that cannot map directly is documented separately for the customer's admin.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Salesforce to Odoo CRMThe same pair in reverse SendCloud to SalesforceMapping · history · rollbackAutoText to SalesforceMapping · history · rollbackSpotler CRM to SalesforceMapping · history · rollbackDubsado to SalesforceMapping · history · rollbackClio to SalesforceMapping · history · rollbackSnovio to SalesforceMapping · history · rollback Odoo CRM to Dynamics 365Mapping · history · rollbackOdoo CRM to Zoho CRMMapping · history · rollbackOdoo CRM to HubSpotMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- 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 Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote