Migrate from Salesforce Field Service to Odoo CRM

Salesforce Account maps directly to Odoo res.partner in company mode. The primary address, phone, website, and industry fields transfer directly. Parent-account hierarchies map to Odoo's commercial_partner_id field for hierarchical reporting. Multi-site accounts (Salesforce child locations) become separate res.partner records linked via parent_id to preserve site-level detail.

Salesforce Contact maps to res.partner in individual mode. First name, last name, email, phone, mobile, title, and mailing address fields transfer directly. The Salesforce contact-account relationship maps to Odoo's partner_id field on the individual res.partner record. If a Salesforce Contact has no associated Account, the individual partner record is created without a parent link.

Salesforce Lead maps to Odoo crm.lead with the Lead radio button selected. Standard fields — Name, Company, Email, Phone, Status, Rating, Source, Annual Revenue, Number of Employees — transfer directly. The Salesforce IsConverted flag determines whether the Odoo crm.lead lands as a new opportunity or merges with an existing partner record. Unconverted leads map as open crm.lead records.

Salesforce Opportunity maps to an Odoo crm.lead with the Opportunity radio button selected, using the Sales tab. Stage, Amount, Close Date, Probability, and Description transfer directly. The Opportunity's AccountId lookup resolves to the corresponding res.partner id already migrated from the Accounts step. Stage probability percentages are recalculated to Odoo's default scale during the mapping phase, with the original Salesforce probability preserved in a custom field for reporting continuity.

Salesforce WorkOrder is the primary field-service record and maps to Odoo project.task linked to a dedicated project. Subject, Description, Status, Priority, and Scheduled Start/End dates transfer directly. AccountId resolves to the migrated res.partner record. The work order's address maps to the task's Planned Date range. Custom fields on WorkOrder (e.g., WorkOrderType__c, ResolutionCode__c) migrate as Odoo custom fields on project.task. The original WorkOrderNumber is preserved in a custom field for audit traceability.

Salesforce ServiceAppointment maps to Odoo calendar.event linked to the project.task created from the parent WorkOrder. Subject, Status, EarliestStartTime, DueDate, and actual travel time fields transfer to the calendar event's start_datetime, stop_datetime, and duration. The assigned ServiceResource resolves to the Odoo user who owns the calendar event. Status mapping: Scheduled → Open, In Progress → Confirmed, Completed → Held, Cancelled → Cancelled.

Salesforce ServiceResource maps to Odoo res.users by email matching — each service technician's Salesforce UserId email resolves to an Odoo user account created before migration. The resource type (technician vs. dispatcher) maps to Odoo's access rights group membership. Salesforce ResourceAbsence records (vacation/availability windows) transfer to Odoo's resource.calendar.leaves table so vacation schedules carry over.

Salesforce OperatingHours define availability windows and timezone settings for service territories. These map to Odoo resource.calendar records with time slots converted from Salesforce's weekly-hour structure to Odoo's hour-line model. The timezone field on OperatingHours sets the resource.calendar's timezone. If multiple operating hours exist per territory, each creates a separate calendar linked to the corresponding service resource group.

Salesforce WorkOrderLineItem records (line items for parts, labor, and services on a work order) map to Odoo sale.order.line records generated from the Odoo Sale Orders app linked to the project.task. Product lookup resolves by SKU matching to Odoo product.product. Quantity, unit price, and description transfer directly. If the source line item has no Odoo product match, a placeholder product is created with the original description and a zero price for post-migration review.

Salesforce Tasks attached to WorkOrders, Accounts, or Contacts map to Odoo mail.activity records linked to the corresponding migrated record (project.task, res.partner, or crm.lead). Subject, Status, Activity Date, Priority, and Description transfer directly. The task owner resolves by email match to the Odoo user. Completed tasks appear as closed activities in Odoo's chatter thread.

Salesforce Events linked to field records map to Odoo calendar.event. Subject, StartDateTime, EndDateTime, Location, and Description transfer directly. The WhoId (Contact/Lead) resolves to the migrated res.partner or crm.lead. The WhatId (WorkOrder or Account) resolves to the migrated project.task or res.partner. Recurring events are not migrated as recurring Odoo events — each occurrence becomes a separate calendar.event record.

Salesforce ContentDocuments and Notes attached to WorkOrders, ServiceAppointments, or Accounts migrate as ir.attachment records in Odoo linked to the corresponding model (project.task, res.partner, crm.lead). Files are downloaded from Salesforce and re-uploaded to Odoo's filestore. File size limits: Odoo allows attachments up to the file system limit; Salesforce's 25MB per-file limit is preserved as a hard boundary during export. Rich-text note bodies migrate as ir.attachment records of type binary with a text_description field populated from the source body.

Any Salesforce custom objects used to extend WorkOrder (e.g., InspectionResult__c, SafetyCheck__c) map to Odoo custom models created in developer mode. Each custom object becomes a new Odoo model inheriting from mail.thread, with fields defined using Odoo's field type system. Relationships to WorkOrder (now project.task) are preserved as many2one fields pointing to project.task. Your Odoo administrator creates these models in the Odoo Settings > Technical > Models panel before the migration run.