Migrate from Field Services Workflow and Logistics to Odoo CRM

Field Services Workflow and Logistics stores both customer contacts and technician records in its Contact object. In Odoo, all contacts land in res.partner regardless of role. A custom partner_tag ('Customer' vs 'Technician') distinguishes the two populations post-migration, applied via a computed field or a manual tag assignment step.

When the FSM Company object has a company_type flag set to true, Odoo res.partner records are created with company_type = 'company'. Child Contact records link via the parent_id field in Odoo, mirroring the FSM company-contact hierarchy. FSM parent-child company relationships map to Odoo's parent_id on res.partner.

FSM service requests map directly to Odoo crm.lead records. The type field on crm.lead is set to 'lead' for FSM cases that are pre-sale service requests and 'opportunity' for cases linked to an existing sale. FSM case priority, SLA tier, and FSM case type become custom fields on crm.lead.

FSM pipeline stage names (Open, Dispatched, In Progress, On Hold, Resolved, Closed) map to Odoo CRM stage records via value-by-value mapping. Odoo's stage_id is a Many2one to crm.stage. Each mapped stage preserves the FSM sequence order so the Kanban column order matches the source. Stage-entered timestamps are stored as custom datetime fields on crm.lead.

FSM work orders without a Project module destination become a set of custom fields on crm.lead: work_order_number, scheduled_date, assigned_technician_id, estimated_duration_hours, work_order_status, and completion_notes. If the Odoo Project module is present, work orders map to project.task records with the crm.lead as the parent, preserving the FSM work-order hierarchy.

FSM customer asset records (serial number, model, warranty expiry, install date) map to Odoo stock.production.lot if the Inventory module is active and the assets are serialised products. For non-serialised assets, the data migrates as a custom Char field on res.partner storing the asset name, model, and serial number as a reference string.

FSM custom fields with pick-list values become Odoo Selection fields on the target model. We create the field via Odoo's Technical Settings with the same label, store the FSM pick-list values as key-value pairs in the selection options, and run a value-mapping pass so the exact FSM option labels appear in Odoo.

FSM custom fields with free-text or numeric values become Odoo Char or Number fields on crm.lead or res.partner depending on which object the field belongs to in the FSM schema. Text-area fields with long content migrate as Char fields with a 500-character limit or as Text fields if the target Odoo version supports long text.

FSM activities logged on service requests (call logs, site visit notes, internal comments) map to Odoo crm.lead activities stored via the mail.message model linked to the crm.lead record. Original timestamps, authors, and subject lines are preserved. Odoo's activity scheduling (Next Action Date, Summary) is left blank for manual assignment post-migration.

FSM file attachments (photos, signed forms, PDF reports) are downloaded and re-uploaded to Odoo as ir.attachment records linked to the parent crm.lead or res.partner record by name. Inline images embedded in FSM notes are extracted and saved as separate ir.attachment files. File size limits for Odoo Online apply (25MB per file).

FSM owner or assigned technician IDs are resolved by email match against Odoo res.users records. Unmatched owners are flagged before migration; the team either creates Odoo user accounts first or assigns records to a fallback user. This prevents records landing in Odoo without a valid user_id owner.

The FSM record's internal ID is stored as a custom Char field (e.g., fsm_original_id__c) on the target Odoo record for traceability and deduplication across delta runs. This field is indexed in Odoo to support fast lookups during the delta-pickup phase.