Migrate from ServiceNow Field Service Management to Odoo CRM

ServiceNow work order headers map to Odoo crm.lead records when used as service requests, or to OCA fsm.order records when full FSM task management is required. Work order number, state, priority, and description fields transfer to crm.lead name and description fields. The OCA Field Service module must be installed before fsm.order records can be created.

Task records attached to ServiceNow work orders map to project.task records linked to the OCA fsm.order. Each task's short description, state, assigned technician, and skill requirements transfer. Parent-child task hierarchies in ServiceNow map to project.task dependency chains in Odoo, and ensure that skill requirements are correctly transferred and linked to the appropriate technician records.

Work order assignment records map to project.task owner fields in Odoo. Technician resolution happens by email match against res.users — any assignments without a matching Odoo user are flagged pre-migration so your team can decide between inviting them as users or reassigning.

ServiceNow skill records map to Odoo hr.skill type records. Skill levels and proficiency ratings on technician assignments transfer as hr.skill.level values. Odoo employee skills are configured under Settings > HR > Skills — we deliver a skill creation plan alongside the migration.

ServiceNow territories map to a custom field on project.task (e.g., x_fsm_territory) or to a dedicated OCA fsm.territory record if the OCA FSM Territory Management module is installed. We surface this decision in the pre-migration schema plan, and includes a validation step to confirm territory names match OCA fsm.territory naming conventions before final mapping.

ServiceNow cmdb_ci records linked to work orders map to Odoo maintenance.equipment records. Serial numbers, model information, and install locations transfer as equipment fields. If Odoo maintenance module is not active, equipment data migrates as custom fields on the linked res.partner or project.task.

Customer location records from ServiceNow FSM map to res.partner records with address fields (street, city, state, zip, country). Latitude/longitude from ServiceNow location records transfer to Odoo's partner geo-localization fields for map-based task planning. These fields are used by Odoo's map widget to display task locations on the geography view, improving dispatch efficiency.

ServiceNow state flow stages (Open, Assigned, In Progress, On Hold, Resolved, Closed) map to Odoo project.task.stage records. Each ServiceNow state maps to a named stage in Odoo — the mapping plan is delivered before migration runs so your admin can customize stage names and sequence order.

ServiceNow priority values (P1 Critical through P5 Planning) map to Odoo task priority integer values (1 = urgent, 5 = low). We preserve the original ServiceNow priority label in a custom field (x_servicenow_priority) so your team retains the original severity context.

Files attached to ServiceNow work orders (photos, signatures, documents) download and re-upload to Odoo's ir.attachment model linked to the corresponding project.task or crm.lead record. Inline images in ServiceNow work order notes are extracted and stored as Odoo attachments. All attachments are processed in bulk to preserve metadata such as creation date and author, ensuring a complete audit trail.

ServiceNow's Dynamic Scheduling workspace and pre-assignment rules have no direct Odoo equivalent in standard Odoo CRM. We preserve dispatcher assignments and scheduling notes as custom fields on project.task (x_scheduler_notes) and deliver a rebuild plan for OCA FSM scheduling rules and skill-based routing.

ServiceNow Flow Designer flows, Orchestrator flows, and state flow automation rules do not migrate. We export your ServiceNow flow definitions as JSON documentation and deliver a mapping guide for Odoo Studio Server Actions and Automated Actions so your admin can rebuild each flow.