Migrate from ServiceNow Field Service Management to Microsoft Dynamics 365 Sales

ServiceNow work orders map to D365 Opportunities as the primary service record. The work order number migrates to a custom field (new_workordernumber) on the Opportunity; the work order short_description becomes the Opportunity Name or a custom field. The wm_order state/status translates to Opportunity State and Stage via value mapping.

Each ServiceNow work order task (the line-item breakdown of a work order) migrates as an Opportunity Product Line Item. The task description becomes the product description; labor hours map to Quantity or a custom quantity field. Multiple tasks on one work order collapse to multiple line items on the corresponding Opportunity.

ServiceNow FSM assignments (which technician is booked to which work order at what time) map to BookableResourceBookings in D365 Field Service. If the D365 Field Service module is not licensed, assignments are stored as custom booking records linked to the Opportunity and Contact. Skills-based matching criteria from ServiceNow are preserved as custom fields.

The customer reference on a ServiceNow work order points to a Customer record (sn_customers) or Account equivalent. This migrates directly to a D365 Account record. The Account must exist before the Opportunity can reference it via the AccountId lookup. We sequence Account migration first.

ServiceNow users with FSM roles map to D365 Users who are also Bookable Resources. Email is the match key. If a ServiceNow technician has no D365 user account, we flag them for team assignment before migration. Active/inactive status is preserved. Skills, work zones, and certifications from ServiceNow become Resource Category and Custom Resource fields in D365.

ServiceNow time entries record labor hours against work orders. In D365 with Field Service licensed, these map to msdyn_timeentry linked to BookableResourceBooking. Without Field Service, a custom time-entry table is created in Dataverse and linked to the Opportunity. Original timestamps, technician user reference, and hours are all preserved.

ServiceNow FSM parts reserved against work orders map to Opportunity Product line items if they represent billable products. Inventory-only reservations (consumed but not billed) migrate as custom fields or a custom inventory-consumption table, since D365 Sales has no native inventory reservation entity.

ServiceNow stores service location addresses on work orders or related cmn_location records. These migrate to Account address fields (address1_composite or address1_line1 through address1_line3) or a custom address table for multi-site accounts. Lat/long coordinates from ServiceNow migrate as custom decimal fields.

ServiceNow SLA definitions attached to work orders have no D365 native equivalent. The SLA name and breach datetime migrate as custom text and datetime fields (new_slaname, new_slabreachtime). SLA compliance rules must be rebuilt as D365 Business Rules or Power Automate flows after migration.

ServiceNow knowledge articles linked to work orders are preserved as text references (article ID and title) in a custom field or as a Note attached to the Opportunity. D365 has no native knowledge-base linking to Opportunity records; the rebuild requires D365's Knowledge Management solution or a SharePoint-backed article library.

ServiceNow file attachments on work orders are extracted from sys_attachment, downloaded with their original filenames, and re-uploaded to D365 Notes (annotation entity) or SharePoint Document Location linked to the Opportunity. File size and type are preserved. Inline images in ServiceNow notes are re-hosted accordingly.

Custom fields on ServiceNow work order tables (all columns with u_ or x_ prefixes) migrate as new_ prefixed custom columns on the D365 Opportunity table. Field data type parity is maintained: text to text, date to datetime, pick-list to option set (value mapping applied per pick-list value), boolean to two-option. D365 field-level security is applied on the custom columns post-migration.