How to Migrate from Salesforce to Odoo Without Losing Deal History
Migration projects fail on things that looked trivial in the planning meeting. Odoo’s field model differs from Salesforce’s in ways that only surface during the actual import.
Direct answer: Migrating Salesforce into Odoo means mapping Accounts to partners, Opportunities to crm.lead records with type=opportunity, and importing in the order partner → product → opportunity. Attachments and activities need separate handling and are where most history is lost.
What are the object mappings?
The obvious ones are obvious. The edge cases are not.
| Salesforce | Odoo | Notes |
|---|---|---|
| Account | res.partner | Needs a flag: company vs individual |
| Contact | res.partner (child) | Parent relation must be set explicitly |
| Lead | crm.lead (type=lead) | Different model flag, same table |
| Opportunity | crm.lead (type=opportunity) | Lost if you do not set the flag |
| Opportunity Product | sale.order.line | Needs a product record first |
| Task | project.task | Or mail.activity — decide early |
| Note | mail.message | Body HTML imports, attachments do not |
The single most common mistake: importing opportunities without setting type to opportunity. They land as leads, disappear from the pipeline view, and someone spends a day thinking the import failed.
What is the right import order?
Odoo will not accept a record that references a missing parent. Order is not optional.
- Partners (accounts and contacts, parents before children).
- Products — required before any opportunity line item.
- Users / salespeople — owners must exist before records claim them.
- Opportunities, with
type=opportunityand a partner reference. - Quotations / sale orders, linked to opportunities.
- Attachments and notes last, matched on your external ID.
Use Odoo’s import tool with an External ID column on every file so records can reference each other across imports. Salesforce IDs work fine as external IDs — they are 15 or 18 characters and stable forever.
What does not translate cleanly?
Four things, reliably.
Validation rules. Salesforce validation rules have no direct equivalent. Some become Odoo Python constraints, some become required fields, some just vanish. Budget a review pass or expect garbage data within a month.
Formula fields. Odoo has computed fields, but they are defined in code, not by an admin in a UI. Every formula field becomes a development task.
Activities and tasks. Salesforce’s activity timeline maps partly to Odoo’s chatter. Emails logged as activities become messages, which is not the same thing and loses the task/event distinction.
Report definitions. Nothing transfers. Every report gets rebuilt in Odoo Studio or as a pivot view. This is usually the largest single chunk of work in a migration.
How long does it actually take?
For a 10-user org with about 20,000 records: 3-5 weeks if you have someone who knows both systems, longer otherwise.
Breakdown from typical projects:
- Data export and cleanup: 3-5 days
- Mapping and trial imports: 3-5 days
- Attachments and history: 1 week
- Reports rebuild: 1-2 weeks
- Parallel running and cutover: 1 week
The phase everyone underestimates is parallel running. Keep Salesforce read-only for 30 days after cutover. Someone will need to look up a closed deal from 2023, and if you have deleted the source, that is gone.
What does it cost, both ways?
Odoo Custom runs about $38 per user per month, Standard about $25. At 10 users, Custom is roughly $4,560 a year. Salesforce at similar scale runs $6,000-15,000 depending on tier and add-ons.
So the saving is real but modest, and it evaporates if the migration takes three months of someone’s time. Do not migrate to save money. Migrate because you need the single-database chain between sales, delivery, and invoicing.
If you genuinely only need to save money on CRM, moving to Zoho CRM at $14 per user is a far cheaper exercise with a fraction of the migration risk.
When should you not migrate?
When Salesforce is messy, not the wrong tool. Teams often decide to migrate because the current org is dirty — and move the dirt to a new platform. Clean first. If that fixes things, you saved a project.
Also do not migrate if you rely on AppExchange apps for core functionality. Those apps have no Odoo equivalents, and rebuilding them is a software project of its own.
For teams that just need contact data feeding the new system, bring it in from Hunter.io or Seamless.AI with a clean CSV rather than migrating a dirty Salesforce export.
Quick Summary
- Import order: partners → products → users → opportunities → quotations → attachments.
- Always set
type=opportunityon opportunity imports or they vanish into leads. - Validation rules, formula fields, and reports do not transfer — budget rebuild time.
- A 10-user, 20k-record migration takes 3-5 weeks, not a weekend.
- Keep the old system read-only for 30 days after cutover.
