Migrate from Field Services Workflow and Logistics to Microsoft Dynamics 365 Sales

Field service work orders map directly to msdyn_workorder. Primary key (workorderid) becomes msdyn_workorderid in Dataverse. The work order's customer field maps to the Account lookup (customerid_account). If the destination has Sales Professional licensing only, work orders cannot be created — assets and cases migrate but work orders require Field Service license.

Source work-order line items (parts used, labor hours, fees) become msdyn_workorderincident records linked to the destination work order. Each incident has a product lookup (msdyn_product) and can carry custom fields for the original line-item metadata. The line-item sequence number maps to the incident's SortOrder field.

Technician records become bookableresource entities with ResourceType set to 'User' or 'Contact' depending on whether the technician is a system user. Skill certifications from the source map to msdyn_resourceskill fields on the bookableresource. Territory assignments map to msdyn bookableresourcebooking lookups.

Customer records in field services platforms map directly to Dynamics 365 Sales Account entities. The primary contact on the account receives a linked Contact record. Address fields map to the account's address composite fields or to msdyn_customeraddress for multi-location accounts.

Service locations and assets merge into msdyn_customerasset, which represents the installed equipment or service site. The asset's customer lookup links back to the Account. Parent-child asset hierarchies in the source become msdyn_customerasset records with ParentAssetId pointing to the parent record, preserving the location tree.

Active service cases from the source map to msdyn_incident. The incident title and description transfer directly. If the case is linked to an asset, the msdyn_customerassetid lookup connects it. Case priority and status reason pick-list values require value-by-value mapping to Dynamics 365 Sales incident resolution codes.

Scheduled appointments become msdyn_bookableresourcebooking records linking the technician (bookableresourceid) to the work order (msdyn_workorderid). The booking's start and end times transfer; resource requirement details from the source map to msdyn_bookingresourcepreference. Overlapping bookings are flagged for manual resolution before the full migration.

Recurring service agreements cannot migrate as active contracts — the destination requires admin-created agreement records with line-item details entered manually. We export the agreement terms, pricing, and frequency as a reference CSV and document the required Field Service agreement setup steps for your Dynamics administrator.

Field service product catalogs map to the Dynamics 365 Sales Product table. Product type (Inventory, Service, Non-inventory) maps to ProductTypeCode. Unit groups from the source map to the defaultuomscheduleid on the product. Custom attributes stored on products become new_ custom columns on the product entity.

Any extended fields on work orders, assets, or resources that have no direct Dynamics 365 equivalent become Dataverse custom columns with new_ prefix. We generate the column creation manifest (schema name, data type, required/optional) before migration runs so the Dynamics admin can pre-create the fields and prevent migration failures from missing column errors.

Documents attached to work orders or assets migrate as Note records (annotation entity) linked to the target record's ObjectId. File size limits apply: Dataverse enforces a 128MB per-file limit for note attachments. Inline images from inspection forms download and re-upload as base64-encoded note body content.

Technician visit logs, call records, and email threads linked to work orders become activitypointer records (PhoneCall, Task, or Appointment) with RegardingObjectId pointing to the destination work order. Original timestamps and technician owners are preserved; owner resolution runs against Dynamics 365 user email matches before the activity write.