Field Services Workflow and Logistics to Dynamics 365 migration
Moving from Field Services Workflow and Logistics to Microsoft Dynamics 365 Sales consolidates your field operations onto Microsoft's Dataverse-backed platform, where work orders map to the msdyn_workorderservicetask entity and technician records become Bookable Resources. FlitStack AI preserves original service-ticket timestamps, asset relationships, and custom field data while sequencing the migration to respect Dynamics 365 Sales entity dependencies and Business Process Flow requirements.
FlitStack AI migrates msdyn_workorders, msdyn_workorderincidents, bookableresources, accounts and msdyn_customerassets from Field Services Workflow and Logistics to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 25,000 records.

What moves from Field Services Workflow and Logistics to Dynamics 365?
Field services platforms store a fundamentally different data model than standard CRMs — work orders, service appointments, bookable resources, and asset hierarchies replace or supplement the Account-Contact-Opportunity triad.
Read the full summary
When migrating to Dynamics 365 Sales, we map these field-service primitives onto the combined Dynamics 365 Sales + Field Service entity model (msdyn_workorder, bookableresource, msdyn_customerasset) while preserving custom fields as Dataverse columns with the new_ prefix. The migration extracts data via the source platform's API, transforms field types (dates, pick-lists, lookups) to match Dataverse column definitions, and loads through the Dataverse Web API or bulk upsert endpoints. Dynamics 365 Sales licensing tier determines whether your deployment supports the full Field Service schema — Sales Enterprise includes Field Service capabilities while Sales Professional does not. We surface the following for manual rebuild: scheduling optimization rules, agreement-based service contracts, and resource role configurations that require Dynamics 365 admin setup rather than data migration. Key preparatory steps include confirming the licensing tier early, auditing custom field schemas, and validating asset hierarchies before the migration run.
Work Order → msdyn_workorder (Field Service)
Field service work orders map directly to msdyn_workorder.
How it maps
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.
Service Task / Line Item → msdyn_workorderincident
Source work-order line items (parts used, labor hours, fees) become msdyn_workorderincident records linked to the destination work order.
How it maps
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 / Field Resource → bookableresource
Technician records become bookableresource entities with ResourceType set to 'User' or 'Contact' depending on whether the technician is a system user.
How it maps
Skill certifications from the source map to msdyn_resourceskill fields on the bookableresource. Territory assignments map to msdyn bookableresourcebooking lookups.
Customer / Account → Account
Customer records in field services platforms map directly to Dynamics 365 Sales Account entities.
How it maps
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 Location / Site → msdyn_customerasset
Service locations and assets merge into msdyn_customerasset, which represents the installed equipment or service site.
How it maps
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.
Case / Service Ticket → Incident (msdyn_incident)
Active service cases from the source map to msdyn_incident.
How it maps
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.
- Work Ordermsdyn_workorder1:1
- Service Taskmsdyn_workorderincidenttransformed
- Technicianbookableresource1:1
- CustomerAccount1:1
- Service Locationmsdyn_customerassetmerged
- CaseIncident1:1
+ 6 more in the mapping below
How Field Services Workflow and Logistics and Dynamics 365 differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Field Services Workflow and Logistics | Dynamics 365 |
|---|---|---|
| Core entity model | Work orders and service appointments drive the data model; no native opportunity tracking | Opportunity entity is central; work orders require Field Service add-on and msdyn_workorder entity |
| Resource scheduling | Bookable resources represent technicians, crews, or equipment with skill profiles | Bookable Resource entity stores resources; Universal Resource Scheduling (URS) requires separate activation |
| Asset tracking | Customer assets linked to service locations and parent-child hierarchies | msdyn_customerasset entity with ObjectId linking to Account; asset hierarchy uses ParentAssetId lookup |
| Scheduling approach | Dispatcher board with drag-drop scheduling; route optimization built in | Schedule Board in Field Service; resource scheduling optimization (RSO) requires additional licensing |
| Custom field naming | Platform-specific naming conventions; custom fields stored as extended properties | Custom columns prefixed with new_ in Dataverse; stored in the same table with SchemaName collision protection |
| Pricing model | Per-technician or per-work-order flat-rate; unlimited users typical | Per-user-per-month: Sales Professional $65, Sales Enterprise $105, Field Service $95; user type (Full vs Team Member) affects access |
| Business Process Flows | Sequential workflow stages with automated routing and SLA tracking | BPFs enforced per-entity with stage transitions; workflow automation via Power Automate rather than native stage actions |
Field Services Workflow and Logistics to Dynamics 365 field mapping
The 30 most-used fields of 41 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
workorderidWork Ordermsdyn_workorderIdmsdyn_workorder -
workordernumberWork Ordermsdyn_namemsdyn_workorder -
statusWork Orderstatecodemsdyn_workorder -
priorityWork Ordermsdyn_prioritymsdyn_workorder -
createdonWork Ordercreatedonmsdyn_workorder
| Field Services Workflow and Logistics field | Dynamics 365 field | Mapping | Note |
|---|---|---|---|
Work Order.workorderid | msdyn_workorder.msdyn_workorderId | direct | |
Work Order.workordernumber | msdyn_workorder.msdyn_name | direct | |
Work Order.status | msdyn_workorder.statecode | value_mapping | Source status pick-list values map to Dynamics 365 statecode (Active/Inactive) and statuscode pairs. |
Work Order.priority | msdyn_workorder.msdyn_priority | direct | |
Work Order.createdon | msdyn_workorder.createdon | direct | |
Work Order.modifiedon | msdyn_workorder.modifiedon | direct | |
Work Order.scheduledstart | msdyn_workorder.msdyn_ServiceTerritory | transformed | Source scheduled start maps to the Territory lookup if location-based routing is configured. |
Work Order.actualarrivaltime | msdyn_workorder.msdyn_ActualArrivalTime | direct | |
Work Order.totallaborhours | msdyn_workorder.msdyn_TotalHours | direct | |
Work Order.custom_field_internalnotes | msdyn_workorder.new_InternalNotes | custom_field_required | Custom field requires pre-creation of new_InternalNotes text column in Dataverse. |
Technician.resourceid | bookableresource.bookableresourceId | direct | |
Technician.resourcename | bookableresource.name | direct | |
Technician.email | bookableresource.userid_email | transformed | For User-type resources, email resolves to the linked user record in the userid field. |
Technician.resource_type | bookableresource.resourcetype | value_mapping | Source resource type (Technician, Crew, Equipment) maps to Dynamics BookableResourceTypeCode enum. |
Technician.territory | bookableresource.msdyn_territory | direct | |
Technician.skill_certifications | msdyn_resourceskill.msdyn_skill | merged | Source skills split into separate msdyn_resourceskill records linked by ResourceId. |
Account.accountid | Account.accountid | direct | |
Account.accountname | Account.name | direct | |
Account.primarycontact | Contact.fullname | transformed | Source primary contact becomes a separate Contact record linked via primarycontactid on Account. |
Account.phone | Account.telephone1 | direct | |
Account.address | Account.address1_composite | direct | |
Account.website | Account.websiteurl | direct | |
Account.industry | Account.industrycode | value_mapping | Industry pick-list mapped per Dynamics 365 industrycode value set. |
Asset.assetid | msdyn_customerasset.msdyn_customerassetId | direct | |
Asset.assetname | msdyn_customerasset.msdyn_name | direct | |
Asset.customerid | msdyn_customerasset.msdyn_CustomerAsset_CustomerId | direct | |
Asset.parentassetid | msdyn_customerasset.msdyn_ParentAsset | direct | |
Asset.serialnumber | msdyn_customerasset.msdyn_serialnumber | direct | |
Asset.installlocation | msdyn_customerasset.msdyn_InstallLocation | direct | |
Asset.warrantyexpiration | msdyn_customerasset.msdyn_WarrantyExpiration | direct |
What to watch for in a Field Services Workflow and Logistics to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Work orders require a Field Service license that Sales Professional does not include
Microsoft sells Dynamics 365 Sales Professional and Sales Enterprise as separate SKUs, with Field Service capabilities gated behind Sales Enterprise or the standalone Field Service plan ($95/user/month).
How we handle it
If your destination tenant has Sales Professional licensing only, msdyn_workorder records cannot be created — the migration will write Account, Contact, and msdyn_customerasset data but skip the work-order and booking tables until a Field Service license is activated. We surface this before the migration runs and flag every work-order record that will be deferred.
Bookable Resource email-match collision causes booking orphans
Dynamics 365 Sales resolves bookableresource ownership by matching the Contact or User email to an existing user record.
How we handle it
If the same email appears in both the source technician list and the existing Dynamics user table — from a previous migration or a shared Microsoft 365 tenant — the booking links to the wrong resource or fails with a duplicate-reference error. We pre-scan the destination tenant for email collisions and either maps to the existing resource or creates a new bookableresource with an _migrated suffix before writing bookings.
Asset parent-child hierarchy creates circular reference risk
Source asset systems frequently store circular parent-child relationships (Asset A → Asset B → Asset C → Asset A) or orphan records where the parent ID no longer exists in the export.
How we handle it
Dynamics 365 Field Service msdyn_customerasset uses msdyn_ParentAsset as a self-referential lookup — importing a circular or dangling reference causes the upsert to fail for the entire batch. We validate the asset hierarchy graph before migration, break circular loops by nulling the parent reference, and surface orphaned asset IDs for manual disposition.
Agreement and service contract pricing doesn't transfer as active billing records
Field services platforms often store recurring service agreements with line-item pricing tied to specific assets or service levels.
How we handle it
Dynamics 365 Sales Field Service stores agreements as msdyn_agreement with agreement-invoice generation on a schedule, but the pricing setup requires the Dynamics admin to configure invoice lines and billing rules in the Field Service agreement form — not a data-import operation. We export the source agreement terms as a reference CSV and provide a step-by-step setup checklist for the Dynamics admin to rebuild billing rules post-migration.
Custom columns on work orders need pre-creation before bulk upsert runs
Dynamics 365 Sales uses Dataverse, which enforces a schema-first model — custom columns must exist before records are written to them.
How we handle it
The source platform's custom fields on work orders become new_* columns in the msdyn_workorder table. If the columns don't exist at migration time, the row write fails for those records. We generate a column-creation manifest (SchemaName, DataType, Required flag) from the source's extended property list and require confirmation that columns have been created in the target environment before the migration run begins.
How the migration runs
Audit source work-order schema and destination licensing tier
We connect to the source platform API and export the full object list — work orders, technicians, accounts, assets, products, and all custom fields.
What this step covers
Simultaneously, we check the destination Dynamics 365 tenant's active SKUs to confirm whether Field Service licensing is present. If Sales Professional only is active, we scope the migration to migratable entities and surface work-order deferral with a rebuild plan. The schema diff between source custom fields and existing Dataverse columns is generated as a creation manifest.
Validate asset hierarchy and resolve circular references
The asset tree from the source is parsed into a directed graph.
What this step covers
We run cycle-detection on the parent-asset relationships; any circular or orphaned references are flagged and resolved (circular loops broken, orphans tagged for the admin's review). The resolved asset graph is staged as the migration source of truth so the bulk upsert to msdyn_customerasset completes without Dataverse self-referential-lookup violations.
Resolve technician-to-user email matching
Each source technician record is matched against the Dynamics 365 tenant's user list by email address.
What this step covers
Matching technicians are linked directly to the existing bookableresource record. Non-matching technicians are created as new bookableresource entities. Email collisions — where the same address exists as both a user and a contact — are flagged and escalated for manual resolution before booking records write.
Run a representative sample migration with field-level diff
A slice of 100–500 records spanning work orders, assets, technicians, and cases migrates first.
What this step covers
We generate a field-level diff between source field values and destination column values so you can verify that custom field data landed correctly, that status reason pick-list values mapped cleanly, and that asset-to-account lookups resolved. The sample run also validates Dataverse API response times under your actual data volume so we can tune batch sizes for the full run.
Execute full migration with delta-pickup window
The complete record set writes to Dynamics 365 Sales in sequenced batches respecting entity dependencies (Accounts → Contacts → Assets → Work Orders → Bookings → Cases).
What this step covers
A delta-pickup window of 24–48 hours captures any records modified in the source during the cutover window. Every operation is logged to FlitStack's audit trail; one-click rollback reverts all writes if the reconciliation check fails.
Field Services Workflow and Logistics - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Field services migrations land in the upper half of FlitStack's range because the data model divergence between work-order-centric schemas and Dynamics 365 Sales' opportunity-first structure requires more transformation logic. Scope drivers include: record count of work orders and service tasks (each needing separate entity writes), number of custom asset relationship fields, whether the source uses N:N technician-to-location assignments, and whether Business Process Flows must be pre-built in Dynamics 365 Sales before data lands. Teams with existing Dynamics 365 Field Service licenses can receive the full work-order schema; those with Sales-only licenses receive asset and case data only. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Field Services Workflow and Logistics to Dynamics 365 →Why teams move from Field Services Workflow and Logistics to Dynamics 365
- Your current field services platform doesn't integrate natively with Microsoft 365 — email, Teams, and SharePoint operate in separate silos. Dynamics 365 Sales surfaces work orders inside Outlook and Teams, reducing the context-switching that dispatches report as their biggest daily friction point in G2 field service reviews.
- Scaling the dispatch team requires per-seat or per-work-order fees that become unpredictable at 20+ technicians. Dynamics 365 Sales Enterprise licensing with Field Service provides a per-user model with full resource scheduling optimization included, and Microsoft's modular pricing lets you add Field Service without re-buying core CRM.
- The field services platform's reporting module doesn't connect to Power BI without third-party connectors, limiting the dashboard depth dispatch managers need for SLA tracking and technician utilization analysis. Dynamics 365 Sales and Field Service write directly to Dataverse, making Power BI integration a native configuration rather than a custom integration project.
- Acquired a company running Dynamics 365 Sales — consolidating onto a single Microsoft tenant eliminates double licensing and enables cross-tenant reporting through Dynamics 365 finance and operations modules. Field service data migrates as historical records while new work orders flow into the unified system post-cutover.
Questions, answered
Field Services Workflow and Logistics to Dynamics 365 migration questions
How long does a Field Services Workflow and Logistics to Dynamics 365 Sales migration take?
Most field-service-to-Dynamics 365 migrations complete in 48–72 hours of clock time for under 25,000 work orders and associated records. Larger deployments with 100,000+ records, complex asset hierarchies, or N:N technician-to-location relationships extend to 5–10 days. The longest planning step is confirming the Field Service licensing tier in the destination tenant — without it, work orders cannot migrate as active records.
Will my field service scheduling rules and dispatch automations migrate to Dynamics 365 Sales?
No. FlitStack AI migrates data and schema only — scheduling optimization rules, dispatcher board configurations, route constraints, and automated dispatch triggers do not transfer. They must be rebuilt in Dynamics 365 Field Service using the Universal Resource Scheduling (URS) setup. We export your current scheduling rule definitions as a reference document and provide a URS configuration checklist for your Dynamics administrator.
What do source work orders become in Dynamics 365 Sales?
Work orders migrate as msdyn_workorder records in the Dynamics 365 Field Service entity model, provided your destination tenant has Field Service licensing. Each work order's service tasks become msdyn_workorderincident records. The technician assigned to the work order links via the Bookable Resource lookup. If the destination has Sales Professional licensing only, work orders are deferred and must be recreated manually post-migration.
Can I migrate custom fields from my field services platform to Dynamics 365 Sales?
Yes, custom fields on work orders, assets, and resources map to Dataverse custom columns using the new_ prefix. Before migration begins, we generate a column-creation manifest listing each custom field's SchemaName, DataType, and Required flag. Your Dynamics administrator reviews this manifest and pre-creates the columns in the target environment. This step is mandatory because Dataverse enforces schema-first writes — custom columns must exist before any records referencing them can be upserted into the database. The manifest also flags any data-type incompatibilities that may require transformation logic during the migration run.
What happens to my service agreements and recurring billing contracts?
Recurring service agreements and their line-item pricing cannot migrate as active billing records in Dynamics 365 Sales Field Service — the msdyn_agreement entity requires admin configuration of invoice generation rules that cannot be derived from raw data. We export the agreement terms, pricing schedules, and service-level commitments as a reference CSV and provide a step-by-step setup checklist for rebuilding billing rules in Dynamics 365 Field Service.
Does the migration affect my current field services platform during cutover?
No. FlitStack AI connects to your source platform with read-only API access — your dispatchers and technicians continue working without interruption. A delta-pickup window of 24–48 hours after the initial migration run captures any work orders, bookings, or case updates created or modified during the cutover window so Dynamics 365 Sales reflects the final state of the source system at go-live.
What happens if my destination tenant only has Sales Professional licensing?
Sales Professional licensing does not include the Field Service schema — msdyn_workorder, msdyn_bookableresourcebooking, msdyn_workorderincident, and msdyn_customerasset tables cannot be written to. We migrate Account, Contact, and Product records, which are available in Sales Professional. Work order and asset records are deferred and exported as CSV with setup instructions. The migration can be completed once a Field Service or Sales Enterprise license is added to the tenant.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → ActiveCampaign to Dynamics 365Mapping · history · rollbackCivicrm to Dynamics 365Mapping · history · rollbackInsightly CRM to Dynamics 365Mapping · history · rollbackPipedrive to Dynamics 365Mapping · history · rollbackZendesk Sell to Dynamics 365Mapping · history · rollbackBitrix24 to Dynamics 365Mapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Service protection limits (Microsoft Dataverse)
- Entity relationship behavior — Microsoft Learn
Get a quote
Moving from Field Services Workflow and Logistics to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote