Migrate from Salesforce Sales Cloud to Odoo CRM

Salesforce Account maps to Odoo res.partner with contact_type = company. 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.

Salesforce Contact maps to Odoo res.partner with contact_type = contact. 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.

Salesforce Lead maps to Odoo crm.lead (in pipeline mode, not the merged lead/opportunity model). 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).

Salesforce Opportunity maps to Odoo crm.lead for pipeline tracking and sale.order for active quotes and orders. 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.

Salesforce Products (Product2) map to Odoo product.product with a product_tmpl_id link. 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.

Salesforce Case maps to Odoo helpdesk.ticket (a module within the Odoo suite). 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.

Salesforce Campaign maps to Odoo marketing.campaign. Campaign Name, Budget, Status, Type, and StartDate/EndDate migrate directly. Campaign Members (Contacts and Leads who responded) map to marketing.utm.mixin records linked to the campaign, preserving Member Status (Sent, Responded, Handled). Campaign Member custom fields migrate to custom fields on marketing.utm.mixin.

Salesforce Contract maps to Odoo account.move (for posted invoices) or contract.contract (for recurring billing if the customer activates Odoo's Contract module). Contract Start Date, End Date, Term, Status, and the linked AccountId map directly. Contract Line Items map to account.move.line records. If the customer uses Odoo Subscription Management, Contracts map to sale.subscription instead, preserving recurring_price and recurring_rule_type.

Salesforce Order maps to Odoo sale.order. Order Status, Effective Date, and the linked AccountId and ContractId migrate directly. Order Products map to sale.order.line. If the Salesforce org uses Advanced Order Management or Revenue Cloud, order lineage is more complex — we scope this during the pre-migration audit and flag any non-standard Order-to-Opportunity linkage as a configuration item.

Salesforce Asset maps to Odoo stock.production.lot (serialized inventory tracking) or maintenance.equipment (for equipment under service contracts). Asset Name, SerialNumber, Status, InstallDate, Quantity, and the linked AccountId and ContactId migrate. If the asset links to a Product, we resolve the product.product reference. Assets created automatically from Contracts or Orders require those parent records in Odoo first.

Salesforce Task maps to Odoo mail.message (as a log note on the related record) or project.task (if the task is tracked work). Task Subject, Status, Priority, ActivityDate, and Description migrate. WhoId (Lead or Contact) resolves to the migrated res.partner record; WhatId (Account, Opportunity, Case) resolves to the migrated parent record. Open tasks with completed = false in Salesforce map to project.task with kanban_state = blocked; completed tasks map as mail.message records on the timeline.

Salesforce Event maps to Odoo calendar.event. Event Subject, StartDateTime, EndDateTime, Duration, Location, and Description migrate directly. Event attendees map to calendar.attendee records linked to the event, with each attendee resolved to a res.partner (User or Contact). Recurring Events in Salesforce map to Odoo calendar.recurrence records with the same recurrence rule.

Salesforce Custom Objects (API name ending in __c) map to Odoo custom models defined via the Settings > Technical > Models interface or as Python classes in a custom module. We create the Odoo model with all custom fields (Char, Float, Date, Many2one, etc.) before any data import. Custom Object relationships (lookup fields) map to Odoo Many2one fields pointing to the correct res.partner, crm.lead, or custom model. Validation rules and required-field constraints are replicated as Odoo Python constraints.

Salesforce Account Team Members (AccountTeamMember) assign a UserId to an AccountId with a TeamRole. We import these after both Account and User records exist in Odoo. Each team member maps to res.users (for Odoo internal users) or res.partner (for external collaborators) added to crm.team with the TeamRole mapped to a custom field or a group assignment in Odoo's access control system.

Salesforce Opportunity Team Members assign a UserId to an OpportunityId with a TeamMemberRole. We import these after the crm.lead record exists. Each team member maps to a record in crm.team.member linked to the crm.lead, with the TeamMemberRole preserved as a custom selection field on the membership record.

Salesforce User records map to Odoo res.users. We resolve by email match. Active status, Username, FirstName, LastName, Title, and the Salesforce profile name (mapped to Odoo groups) migrate. A Salesforce User without a matching Odoo res.users is held in a reconciliation queue for the customer's Odoo admin to provision before record migration continues, because OwnerId references on Opportunities and Leads require a valid res.users.