Migrate from Odoo Field Service to Salesforce Sales Cloud

Odoo res.partner records where is_company=True map to Salesforce Account. The Account.Name pulls from partner.name; Account.Website from partner.website; Account.Industry from a value-mapped partner.industry field. Industry mapping uses a lookup table to reconcile Odoo's configurable industry selections against Salesforce's standard Industry pick-list values. Records with unmapped industry values default to 'Other' with the original value preserved in a custom Industry_Source__c field for post-migration cleanup.

Odoo res.partner records where is_company=False map to Salesforce Contact, linked via AccountId to the parent Account. partner.email maps to Contact.Email; partner.phone to Contact.Phone; partner.mobile to Contact.MobilePhone. Contacts without an email address are flagged for manual review since Salesforce requires Email on standard Lead conversion paths. The partner.function field populates Contact.Title, and partner.lang maps to Contact.Languages__c if your org uses the multilingual configuration.

Odoo partners with partner_type='lead' or that have never been converted to opportunities map to Salesforce Lead rather than Contact. The partner.name becomes Lead.Company; partner.email becomes Lead.Email; partner.function becomes Lead.Title. Leads retain the original Odoo create_date in Lead.CreatedDate__c for historical tracking. If the partner has any fsm.order history, the Lead stores a reference to the migrated WorkOrder count in a custom Lead.Work_Orders_Pre_Conversion__c field to preserve service context.

Odoo fsm.order maps directly to Salesforce WorkOrder. WorkOrder.Subject pulls from fsm.order.name; WorkOrder.ServiceAddress from fsm.location; WorkOrder.AssetId from the mapped equipment-to-Asset lookup; WorkOrder.AccountId from the partner on the order. The Odoo fsm.order priority integer (1–4) maps to WorkOrder.Priority through the configured value-mapping table. Order description text from fsm.order.note populates WorkOrder.Description for full work-order context.

Odoo fsm.order line items (product lines on a work order) map to Salesforce WorkOrderLineItem, linked by WorkOrderId. product_id resolves to the Salesforce Product2 reference; product_uom_qty and price_unit translate to Quantity and UnitPrice. Product matching prioritizes exact SKU alignment, then falls back to product name fuzzy-match against active Product2 records. Products with no Salesforce match are held in a staging table for product creation before the migration run commits.

Odoo tasks linked to fsm.order map to Salesforce ServiceAppointment child records under the WorkOrder. scheduled_date_start/end from fsm.task.date_begin/date_end; user_id resolved by email match to Salesforce users for assignment. If no matching ServiceResource exists for the technician, FlitStack creates one using the Odoo user record as the source, enabling the ServiceAppointment to link natively. Task tags (fsm.tag) translate to ServiceAppointment custom fields or Skills records if your org uses the Skills Management feature.

Odoo fsm.equipment maps to Salesforce Asset. Asset.Name from equipment.name; Asset.SerialNumber from equipment.serial_no; Asset.AccountId from the partner to whom the equipment is assigned; Asset.InstallDate from equipment.date_put_in_service. Equipment.model reference populates Asset.Model__c; equipment.notes map to Asset.Description. The Asset Status field defaults based on equipment.active — active equipment becomes 'Active', inactive records become 'Retired'.

Odoo fsm.location records (service sites) map to Account address fields on the linked partner account. street, city, zip, country map to BillingAddress/ShippingAddress on Account. If the location has custom fields, those translate to custom fields on Account. Locations without a linked partner become standalone Account records with the location name as Account.Name and a Location_Type__c flag set to 'Service Site'. Geographic coordinates (lat/long) from fsm.location map to Account.GPS_Location__c for dispatch map rendering.

Odoo ir.attachment records linked to fsm.order or res.partner re-upload to Salesforce Files (ContentDocument/ContentVersion). The original file name and MIME type are preserved. Files are linked to the parent Salesforce object by ContentDocumentLink. Attachments exceeding Salesforce's 25MB per-file limit are split into multi-part uploads with a manifest linking the fragments. Image attachments (MIME image/*) set ContentDocument.FileType to match the source format.

Odoo's ir.model.fields custom fields on fsm.order and res.partner are inventoried per model, translated to Salesforce custom field definitions (type, label, pick-list values), and deployed to Salesforce Setup before the migration run. Each field requires a manual __c field creation step or an API-based metadata deployment.

Odoo project.project records linked to Field Service map to a Salesforce custom Project__c object if your org has the Salesforce Field Service managed package installed. project.name becomes Project__c.Name; project.user_id resolves by email match to a Salesforce user. Project dates (date_start, date_end) map to Project__c.Start_Date__c and Project__c.End_Date__c. The project.linked_task_count is stored in Project__c.Task_Count__c to preserve the scope scale of each migrated project.

Odoo sale.order records associated with fsm.order merge into Salesforce Opportunity for the sales side and Salesforce Order for fulfillment tracking. The opportunity amount and stage reflect the linked sale.order state; order records capture line items and delivery status. sale.order.client_order_ref maps to Order.PoNumber for invoice matching. The order's incoterms field populates Order.ShippingMethod__c when available, otherwise defaults to the standard carrier configuration.