Migrate from Odoo CRM to Salesforce Sales Cloud

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. 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.

Odoo crm.lead records with type='lead' (not yet converted to an Opportunity) map directly to Salesforce Lead. 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.

Odoo crm.lead records with type='opportunity' map to Salesforce Opportunity. 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.

Odoo crm.stage values migrate as Salesforce Opportunity StageName entries with probability percentages preserved from Odoo's stage probability. 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.

Odoo crm.team groups Opportunities and assigns Leads via user_id and member_ids. 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.

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). 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.

Odoo custom fields defined via Studio or in custom addon modules are stored as columns in crm.lead or res.partner. We export field definitions (name, type, selection options, relational target) and pre-create matching Salesforce custom fields before the data migration phase. Field types are mapped: Odoo selection fields become Salesforce picklists or multi-select picklists; many2one becomes a lookup; many2many becomes a multi-select picklist or junction object; char and text become text or textarea. If the custom field is defined in an addon module not deployed in the target, we document it and flag it as data-only (present in database, no UI definition).

Odoo ir.attachment records linked to crm.lead are stored in the Odoo filestore as binary files. We export the filestore contents, chunking by subdirectory and record reference. Files are uploaded to Salesforce via the Connect API (Chunks for large files) and linked via ContentDocumentLink to the migrated Lead, Contact, Account, or Opportunity. ir.attachment.res_model and res_id are mapped to the corresponding Salesforce object and record ID. Large attachment volumes (over 50,000 files) require staged migration with the customer's storage allocation confirmed before the upload phase begins.

Odoo crm.tag records applied to crm.lead via many2many are exported as a flat tag list. Tags used for lead categorization migrate to a Salesforce custom multi-select picklist field on Lead (lead_tags__c) or Opportunity (opp_tags__c), or to Salesforce Topics if the customer uses topic-based classification. Tag names are normalized (trimmed, de-duplicated) before import. The customer selects the tagging strategy during scoping.

Odoo sale.order records linked to crm.lead migrate as Salesforce Opportunity records if the destination is Sales Cloud only, or as Salesforce Quote records if the destination includes the Salesforce CPQ bundle or Sales Cloud Quote management. Odoo sale.order.line records migrate as OpportunityLineItems (if mapping to Opportunity) or QuoteLineItems (if mapping to Quote). Product2 and PricebookEntry are created from Odoo product.product before line item migration. Tax and discount fields map to Salesforce equivalents where available; custom fiscal or tax logic is documented separately.

Odoo AI lead scoring (crm.scoring.rule) is an Enterprise-only feature with a proprietary scoring algorithm trained on Odoo's behavioral data. It has no direct Salesforce equivalent. We do not migrate scoring rules. If the customer licenses Salesforce Einstein Lead Scoring (available from Sales Cloud Professional), we document the top Odoo scoring fields and their relative weights as a reference for manual Einstein configuration. The scoring rule inventory is included in the delivered documentation.

Odoo CRM automation rules scoped to crm.lead (base.action.rule, ir.actions.server) are Enterprise-exclusive and tightly coupled to Odoo's action framework. They do not migrate to Salesforce Flow because the trigger conditions, action types, and delay models differ. We deliver a written inventory of every active automation rule with its trigger object, conditions, actions, and recommended Salesforce Flow alternative, including whether the automation maps to a record-triggered Flow, scheduled Flow, or Platform Event pattern. The customer's admin or a Salesforce partner rebuilds them post-migration.