Skip to content
Get a quote

Salesforce to Odoo CRM migration

We migrate Accounts, Contacts, Leads, Opportunities, Cases, and historical Activities from Salesforce Sales Cloud into Odoo CRM with dependency-ordered inserts, custom field equivalence mapping, and a written inventory of every Workflow Rule and Apex trigger that must be rebuilt as Odoo automated actions or Python modules before go-live.

Short answer

FlitStack AI migrates res.partners, crm.leads, crm.lead or sale.orders, product.product / product.pricelists and helpdesk.tickets from Salesforce to Odoo CRM, 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: 4-6 weeks.

By

Source Salesforce
DestinationOdoo CRM
res.partnercrm.leadcrm.lead or sale.orderproduct.product / product.pricelisthelpdesk.ticket
Mapped field by field · sample run · one-click rollback

What moves from Salesforce to Odoo CRM?

Moving from Salesforce Sales Cloud to Odoo CRM is an ERP-first migration, not a like-for-like CRM replacement.

Read the full summary

Salesforce stores data in a relational object graph with REST, Bulk, and Composite APIs; Odoo uses a Python/PostgreSQL model where CRM (crm.lead), Contacts (res.partner), and Accounts (res.partner in company mode) share the same partner table under different contexts. We resolve the Account-Contact distinction explicitly — Salesforce keeps Accounts and Contacts as separate objects with a junction table; Odoo models the same entity as a res.partner record with a contact_type flag. We extract Salesforce data via the Bulk API with batch pacing against the 15,000-batch daily quota, clean and transform records in staging, and load them into Odoo through its native XML/CSV import or the XML-RPC API. Apex triggers, Visualforce pages, and Salesforce Flow automations do not migrate as code — we deliver a written map of every active trigger and workflow with an Odoo automated action or Python module equivalent for the customer's functional team to rebuild post-migration.

1:1

Account → res.partner (contact_type = company)

Salesforce Account maps to Odoo res.partner with contact_type = company.

How it maps

The Account Name becomes the partner's name, Industry maps to industry_id, Type maps to customer_rank (1 for customer, 0 otherwise), and Annual Revenue maps to a custom float field. Parent-Account hierarchies in Salesforce become parent_id on res.partner — we import top-level Accounts first, then resolve parent_id for child Accounts in a second pass. Account Team Members are handled as a separate pass against crm.team membership.

1:1

Contact → res.partner (contact_type = contact)

Salesforce Contact maps to Odoo res.partner with contact_type = contact.

How it maps

The contact's Name, Email, Phone, Title, and Department migrate directly. AccountId maps to parent_id on the res.partner, establishing the company-contact hierarchy in Odoo. The AccountContactRelation junction (many-to-many) maps to a separate pass creating additional parent_id records or child contacts under each related Account — we import all Contacts after parent Accounts are committed.

1:1

Lead → crm.lead

Salesforce Lead maps to Odoo crm.lead (in pipeline mode, not the merged lead/opportunity model).

How it maps

LeadSource, Status, Rating, and AnnualRevenue map directly to crm.lead source_id, stage_id, priority, and planned_revenue. Any custom Lead fields migrate to custom Char, Float, or Selection fields on crm.lead. Converted Leads in Salesforce create Account + Contact + Opportunity — in Odoo, the same lifecycle maps to a single crm.lead that moves through stages to won/lost with a linked partner_id (from the Account) and an optional sale_order_id (from the converted Opportunity).

1:N split

Opportunity → crm.lead (won/lost stage) or sale.order

Salesforce Opportunity maps to Odoo crm.lead for pipeline tracking and sale.order for active quotes and orders.

How it maps

StageName maps to crm.lead stage_id with probability percentages preserved. Amount maps to planned_revenue. Close Date maps to date_deadline. When an Opportunity reaches Closed-Won in Salesforce, we create an Odoo sale.order carrying the same account, partner, amount, and line items. When it reaches Closed-Lost, we set the stage to Odoo's lost stage with a lost_reason field populated from Salesforce's Loss Reason.

1:1

Opportunity Product / Price Book Entry → product.product / product.pricelist

Salesforce Products (Product2) map to Odoo product.product with a product_tmpl_id link.

How it maps

Standard Price Book maps to Odoo product.pricelist with price list items migrated as product.pricelist.item records. Opportunity Line Items map to sale.order.line with price, quantity, and discount preserved. Pricebook2Id on the Opportunity resolves to the correct product.pricelist on the sale.order.

1:1

Case → helpdesk.ticket

Salesforce Case maps to Odoo helpdesk.ticket (a module within the Odoo suite).

How it maps

Case Status maps to ticket stage_id, Priority maps to priority, Origin maps to category_id or a custom selection field, and the ContactId maps to the res.partner created from the original Contact. Cases with open Tasks or Events have those Activities migrated separately as Odoo mail.message or project.task records linked to the ticket. If the customer does not activate the helpdesk module, Cases map to project.task as an alternative.

What moves16 objects
SalesforceOdoo CRM
  • Accountres.partner1:1
  • Contactres.partner1:1
  • Leadcrm.lead1:1
  • Opportunitycrm.lead or sale.ordersplit
  • Opportunity Productproduct.product1:1
  • Casehelpdesk.ticket1:1

+ 10 more in the mapping below

How Salesforce and Odoo CRM 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.

DimensionSalesforceOdoo CRM
Core identityCRM-first platform with 5,000+ AppExchange appsERP-first suite with 50+ native modules sharing one database
Account-Contact modelSeparate Account and Contact objects with AccountContactRelation junctionSingle res.partner table with contact_type (contact/company) and address hierarchy
Lead-Opportunity modelSeparate Lead and Opportunity objects with explicit Convert actionSingle crm.lead object with stage-based pipeline and won/lost stages acting as Opportunity
DeploymentCloud only (no on-premise option)Cloud, on-premise, or self-hosted (Community, Enterprise, Online editions)
Customization modelApex, Visualforce, Flow, and Metadata API — requires Salesforce-specific developmentPython server-side modules and JavaScript QWeb views — standard programming languages
Pricing modelPer-user tiers ($25-$550/seat/mo) plus storage overages, add-ons, and 8-10% annual upliftPer-user tiers ($31-$100/seat/mo) for CRM; Community edition free for core ERP modules
Workflow automationSalesforce Flow (record-triggered, scheduled, screen) with Process Builder retiredOdoo Automated Actions (ir.actions.server) with server-side Python logic

What to watch for in a Salesforce to Odoo CRM migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Apex triggers and Visualforce pages have no Odoo equivalent and require full rewrite

Salesforce custom logic written in Apex (triggers, classes, REST endpoints) and Visualforce pages cannot be imported into Odoo.

How we handle it

Odoo runs Python server-side and uses QWeb for web views — a fundamentally different architecture. We document every active Apex trigger, its object, its conditions, and its side effects as a written handoff item. The customer's Odoo developer or functional consultant rebuilds each trigger as an Odoo ir.actions.server automated action or a custom Python method on the relevant model. Custom REST endpoints in Apex have no Odoo equivalent without custom development on the Odoo XML-RPC or JSON-RPC API layer. This rewrite work falls outside our standard migration scope.

high

Salesforce Workflow Rules and Process Builder require redesign, not translation

Salesforce Workflow Rules and Process Builder automations (field updates, email alerts, outbound messages, task creation, approval processes) do not map to Odoo automated actions on a field-to-field basis.

How we handle it

Odoo's Automated Actions (ir.actions.server) handle record-triggered and time-based logic but use a different event model, action set, and delay syntax. We audit every active Workflow Rule and Process Builder process during scoping, document each automation's trigger object, conditions, and actions, and deliver a written inventory with an Odoo equivalent recommendation. The customer's functional team or Odoo partner rebuilds each automation in Odoo's Automation app post-migration. We do not implement Odoo workflows as part of the data migration scope.

medium

The Salesforce Account-Contact model diverges from Odoo's res.partner hierarchy

Salesforce keeps Accounts (companies) and Contacts (people) as separate objects with a many-to-many AccountContactRelation junction table.

How we handle it

Odoo uses a single res.partner table where contact_type = company represents an organization and contact_type = contact represents a person linked via parent_id. A Contact with multiple Account relationships in Salesforce maps to one primary res.partner (the person) plus additional child res.partner records under each related company partner, or to a res.partner with multiple parent_id records if Odoo's contacts_multi_company setting is enabled. We handle this as a two-pass import after Accounts are committed.

medium

Odoo reporting uses a different paradigm from Salesforce reports and Einstein

Salesforce reports offer cross-object reporting, joined reports, matrix reports, and bucket fields — plus Einstein Analytics for predictive dashboards.

How we handle it

Odoo uses its own reporting engine (based on PostgreSQL queries exposed through the web interface) and Odoo BI for more advanced analytics. Historical Salesforce reports do not migrate. We deliver a written inventory of every active Salesforce Report and Dashboard with its object joins, filters, and chart type so the customer's Odoo functional consultant can rebuild equivalent reports in Odoo or Odoo BI. Einstein AI scoring models do not migrate — lead scoring in Odoo must be rebuilt using Odoo's Scoring System or a custom Python rule.

medium

User permissions model has different granularity between platforms

Salesforce profiles and permission sets map to Odoo groups (access rights on the Settings > Users > Access Rights panel).

How we handle it

Salesforce field-level security has no direct Odoo equivalent — Odoo uses group-level read/write/create/unlink rights per model. A Salesforce profile with read-only access on a field grants visibility only to permitted users; Odoo would grant the same access through a group with field-level access restrictions set on the form view. We document the Salesforce profile-permission set matrix during scoping and provide a written group-permission mapping for the customer's Odoo admin to configure before user onboarding.

How the migration runs

  1. Discovery and Odoo edition selection

    We audit the source Salesforce org across edition (Starter through Agentforce 1 Sales), active Custom Objects, active Workflow Rules and Process Builder processes, Apex triggers, installed packages, API usage volume, and record counts per object.

    What this step covers

    We pair this with an Odoo edition decision: Community (free, self-hosted or Odoo Online free tier) covers core CRM and Sales; Enterprise ($31-$100 per user per month) is required for the Studio interface, automated actions, and the full helpdesk, project, and accounting modules; Online ($100 per user per month) provides Odoo-hosted infrastructure. The discovery output is a written migration scope with object inventory, a complexity assessment, and an Odoo edition recommendation.

  2. Schema design and Odoo model provisioning

    We design the destination schema in Odoo.

    What this step covers

    This includes activating the relevant modules (CRM, Contacts, Sales, Helpdesk, Project, Inventory, Accounting depending on scope), creating custom fields on res.partner and crm.lead to receive migrated Salesforce custom fields, configuring pipeline stages to match the source Opportunity stages, setting up sale teams to map to Salesforce Territories, and defining the res.partner contact_type hierarchy (company vs. contact) with parent_id linkage. We deploy to a staging Odoo database first. Any Salesforce Custom Object gets a corresponding Odoo model created via Settings > Technical > Models before any data import begins.

  3. Data extraction from Salesforce

    We extract Salesforce data using the Bulk API 2.0 with batch pacing against the 15,000-batch daily quota and exponential backoff on concurrent-request limits.

    What this step covers

    Data extraction runs in dependency order: Users first (by email), then Accounts, then Contacts (with AccountId resolved), then Leads, then Opportunities, then Products and Price Book Entries, then Cases, then Campaigns, then Activity history. Custom Objects extract last because they often contain lookups to standard objects. We run a pre-extraction data audit to identify duplicates, missing required fields, and inactive OwnerId references, and we address these before extraction begins rather than during import.

  4. Data cleansing, transformation, and staging import

    We transform Salesforce data into Odoo's import format (CSV with XML-RPC load or direct database injection for large volumes).

    What this step covers

    Key transformations include: splitting Salesforce Account and Contact into res.partner records with contact_type differentiation; converting Salesforce Lead to crm.lead in pipeline mode; mapping Opportunity Stage to crm.lead stage_id; resolving Owner email to res.users id; converting Salesforce dates to Odoo's datetime format; and mapping picklist values to Odoo selection fields or many2one relationships. We run a staging import into the staging Odoo database and deliver a reconciliation report (record counts per object, field coverage percentage, null rate on required fields) before proceeding.

  5. Production migration in dependency order with parallel testing

    We run production migration in the same dependency order used for extraction: Users (manually provisioned in Odoo, validated), Accounts (res.partner, contact_type=company), Contacts (res.partner, contact_type=contact with parent_id to Account), Leads (crm.lead), Opportunities (crm.lead with won/lost stage handling), Price Book Entries and Products, Cases (helpdesk.ticket), Campaigns and Campaign Members, Activity history (mail.message, calendar.event), and Custom Objects.

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. We do not import Attachments as binary blobs — we deliver a written inventory of ContentDocument records with their links for the customer's admin to re-attach post-migration.

  6. Cutover, validation, and automation rebuild handoff

    We freeze Salesforce writes during cutover, run a final delta migration of any records modified during the migration window, then enable Odoo as the system of record.

    What this step covers

    We deliver the Apex trigger and Workflow Rule inventory document with Odoo automated action equivalents to the customer's functional team. We do not rebuild Apex triggers as Python modules, Workflow Rules as Odoo automated actions, or Visualforce pages as QWeb views within the migration scope — these are separate engagements. We support a one-week hypercare window where we resolve any record-reconciliation issues raised by the customer's team.

Salesforce Odoo CRM
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Odoo CRMRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

4-6 weeksTypical, smaller accounts
10-16 weeksLarge or heavily customised accounts

A quote scales with record volume, custom object count, and the scope of custom code requiring documentation for rebuild. We do not include Odoo module activation, workflow rebuild, or post-launch support in the standard migration scope — these are separate engagements. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Salesforce to Odoo CRM →

Why teams move from Salesforce to Odoo CRM

  • Salesforce's per-seat pricing plus mandatory add-ons (Sales Engagement, Sales Programs, Salesforce Maps) compounds to 30-40% above the sticker price for mid-market teams. Odoo Enterprise at $31 per user per month covers CRM, sales orders, and core reporting without per-feature add-ons.
  • Salesforce is purpose-built for CRM but requires separate paid Clouds for accounting, inventory, manufacturing, and HR — each adding cost and creating data silos. Odoo unifies CRM, Sales, Accounting, Inventory, Manufacturing, and HR under one PostgreSQL database on one login. When a deal closes in Odoo CRM, a delivery order triggers in Inventory and an invoice generates in Accounting automatically, without middleware or third-party integration.
  • Salesforce custom logic (Apex triggers, Visualforce pages, custom REST endpoints) requires Salesforce-certified developers at $150-250 per hour. Odoo's server-side modules use Python, and its web views use JavaScript with QWeb templating — standard programming languages with a much larger talent pool and lower day-rate costs. Reviewers who left Salesforce on Reddit and G2 cited the cost of Apex developer time as a forcing function for the switch.
  • Workflow Rules and Process Builder are retired in Salesforce and all orgs must migrate to Salesforce Flow — a project many teams have deferred. When the org moves to Odoo instead, the forced Flow rework becomes unnecessary: Odoo's Automated Actions (ir.actions.server) handle record-triggered and scheduled automation natively without requiring a separate automation designer or a migration from deprecated tooling.
  • Salesforce requires a dedicated admin or consultant for meaningful configuration. Odoo's modular Studio interface allows functional users to add fields, configure views, and set up basic automated actions without developer involvement. Companies with fewer than 50 users and no dedicated Salesforce admin consistently cite the administrative overhead of Salesforce as the reason they moved to Odoo.

Questions, answered

Salesforce to Odoo CRM migration questions

How long does a Salesforce Sales Cloud to Odoo CRM migration take?

Most migrations land between four and six weeks for organizations under 25,000 Accounts, 50,000 Contacts, and 5,000 Opportunities with no Custom Objects and no active Apex triggers. Migrations with Custom Objects, large Activity histories (over 200,000 Task and Event records), active Workflow Rules requiring documentation, or multiple Salesforce Clouds (Sales Cloud + Service Cloud) move to ten to sixteen weeks because of the data volume, transformation complexity, and the additional Odoo configuration scope.

Do my Salesforce Workflow Rules, Process Builder flows, and Apex triggers migrate to Odoo?

No. Workflow Rules, Process Builder, and Apex triggers are Salesforce-specific code artifacts. We do not migrate them as functional equivalents in Odoo. We deliver a written inventory of every active Workflow Rule, Process Builder process, and Apex trigger with its trigger object, conditions, and actions, plus a written recommendation for the equivalent Odoo Automated Action or Python module. The customer's Odoo developer or functional consultant rebuilds these post-migration. Odoo automated actions use a different event model and action syntax from Salesforce Flow — they must be redesigned, not translated mechanically.

Can we keep Salesforce for one department while moving sales to Odoo?

Yes. A hybrid migration is one of the most common patterns for this pair, typically when the service or support team wants to stay in Salesforce while the sales team moves to Odoo. We migrate the sales-relevant objects (Accounts, Contacts, Leads, Opportunities) into Odoo, and we configure Odoo's external database sync or a middleware connector (such as the Salesforce-Odoo connector available on the Odoo Apps store) to maintain a read-only or bidirectional sync for shared contact records. The customer continues paying for their Salesforce Service Cloud or Enterprise license for the non-migrated team.

Do historical Activity records (Tasks, Events, Emails) migrate into Odoo?

Yes. We migrate Salesforce Task and Event records as Odoo mail.message records (for log notes) and calendar.event records (for scheduled events) linked to the migrated res.partner and crm.lead records. Emails in Salesforce (EmailMessage objects) migrate as mail.message records with the email body preserved. Attachments (ContentDocument) do not migrate as binary files — we deliver a written inventory of every ContentDocument with its linked object and a recommended re-upload path for the customer's admin. Open Tasks in Salesforce map to Odoo project.task records if the customer activates the Project module.

What happens to our Salesforce Reports and Dashboards?

Salesforce Reports and Einstein Analytics dashboards do not migrate to Odoo because they use a fundamentally different reporting engine. We deliver a written inventory of every active Salesforce Report and Dashboard with its object joins, filters, groupings, and chart type so the customer's Odoo functional consultant can rebuild equivalent reports in Odoo (using the built-in reporting module) or in Odoo BI (for more complex cross-module analysis). This inventory work is included in the migration scope; the rebuild itself is a separate engagement.

Is Odoo self-hosted or cloud-hosted, and does it affect the migration?

Odoo offers three deployment options: Community (free, self-hosted on the customer's own infrastructure), Enterprise (Odoo-hosted cloud or on-premise, $31-$100 per user per month), and Online ($100 per user per month, fully managed cloud). The migration process is identical regardless of deployment — we load data into the Odoo database via XML-RPC API or direct CSV import. If the customer chooses the self-hosted Community edition, they are responsible for their own PostgreSQL hosting, SSL, and maintenance. We do not manage the customer's Odoo hosting environment; we deliver data into the database they provision.

Can FlitStack AI migrate from Salesforce to both Odoo CRM and a separate Odoo Accounting module?

Yes. We scope Odoo migrations that include multiple modules as a single project. If the customer moves both CRM and Accounting, we map Salesforce Accounts and Contacts to res.partner, Salesforce Contracts to account.move or sale.subscription, and Salesforce Orders to sale.order with invoice generation in the accounting module. The Accounting module activation and chart of accounts configuration happens during Odoo setup (before data migration) and is scoped as a separate workstream. We coordinate the data migration to run after the Odoo module configuration is complete so that records arrive into a correctly structured database.

Get a quote

Moving from Salesforce to Odoo CRM?

Tell us roughly how many records and objects you have. We scope the mapping and the Odoo CRM setup with you, then send a quote.

Get a quote