Migrate from Sales ERP to Odoo ERP

Salesforce Account maps to Odoo res.partner with partner_type set to 'company'. The Salesforce Account Name maps to res.partner.name, BillingAddress and ShippingAddress map to partner addresses via res.partner.address fields. Parent Account hierarchy (Salesforce parentId) maps to Odoo's commercial_partner_id field, which Odoo uses to maintain company-group relationships in its partner database. We store the original Salesforce Account ID in a custom field for cross-reference.

Salesforce Contact records map to Odoo res.partner with partner_type set to 'contact', linked to the parent company via parent_id pointing to the Partner record created from the Contact's Account. Each Contact produces one res.partner contact record. Salesforce's Account Contact Relation (ACR) object, which allows a Contact to link to multiple Accounts, maps to Odoo res.partner multiple address roles; we create one Partner contact record per Account-Contact relationship in the ACR.

Salesforce Opportunity maps to Odoo crm.lead with type='opportunity'. The Opportunity Name maps to crm.lead.name, Amount maps to planned_revenue, CloseDate maps to date_deadline, Stage maps to stage_id via a pre-configured Odoo stage mapping, and Probability maps to probability. Opportunity Team Members do not have a direct Odoo equivalent; we assign the primary Salesforce Opportunity owner to the crm.lead user_id and document additional team member roles in a custom text field for manual Odoo team assignment.

Each Salesforce Opportunity StageName maps to an Odoo crm.stage record. We pre-create the stages in Odoo CRM during schema design, preserving the stage probability percentages as Odoo stage probabilities. Closed-Won and Closed-Lost map to Odoo's won and lost stage states.

Salesforce Lead maps to Odoo crm.lead with type='lead' (separate from opportunities). Lead_Status maps to crm.lead.activity_state, Lead_Source maps to source_id via an Odoo source mapping, and any custom lead scoring fields migrate to crm.lead.priority or a custom float field. We create Odoo CRM stages for the Lead lifecycle before migration.

Salesforce Order maps to Odoo sale.order. OrderNumber maps to name, AccountId resolves to the Partner record (from Account mapping), OrderStatus maps to state, TotalAmount maps to amount_total, and EffectiveDate maps to date_order. We pre-create the corresponding Odoo sale.order records after Partners are loaded so that Partner references are satisfied at insert time.

Salesforce OrderItems map to Odoo sale.order.line records. Product2Id resolves to the mapped Odoo product.product record via SKU lookup, Quantity resolves to product_uom_qty, and UnitPrice resolves to price_unit. We create the product catalog in Odoo before OrderItems ingest so that product_id references are valid.

Salesforce Product2 maps to Odoo product.product. ProductName maps to name, ProductCode maps to default_code (SKU), IsActive maps to sale_ok and purchase_ok flags, and Description maps to description_sale. Standard Price Book entries map to Odoo product.pricelist.item records linked to the product.

Salesforce Contract maps to Odoo account.analytic.account for recurring contract tracking. ContractNumber maps to name, AccountId resolves to the Partner, StartDate and EndDate map to date_start and date, and Status maps to recurring_invoice and active flags. If the customer uses Odoo Subscription management (sale_subscription app), Contracts map to subscription.model instead.

Salesforce User records map to Odoo res.users for active licensed users. We resolve by matching Email on User to login on res.users. Inactive Salesforce Users do not migrate to avoid inflating Odoo seat count. Any User without a matching Odoo login is held in a reconciliation queue for the customer's admin to provision before record ingestion.

Salesforce Notes migrate to Odoo ir.attachment records linked to the parent record (Partner, Sale Order, CRM Lead) via res_model and res_id. Attachments with Base64-encoded content (standard for Salesforce REST API) are decoded and stored in Odoo's attachment storage. We migrate Notes as ir.attachment with internal notes content; email attachments migrate as separate ir.attachment records.

Salesforce custom objects (API name ending in __c) require pre-provisioning as Odoo custom models via Python inheritance of models.Model before any data moves. We pre-create the destination Odoo model with the same field names and types as the Salesforce custom object fields, then ingest the custom object records using Odoo's XML-RPC or CSV import API. Salesforce custom object relationships (lookup, master-detail) map to Odoo many2one and one2many fields on the custom model.