Migrate from MobileWorker to Microsoft Dynamics 365 Sales

MobileWorker worker records map directly to Dynamics 365 Contacts. The Contact's full name is constructed from the worker's first and last name fields. Worker skill certifications, certifications expiry dates, and availability windows migrate as custom fields on the Contact record. Each Contact is linked to a parent Account representing the worker's employer or agency.

MobileWorker workers who will log in to Dynamics 365 are provisioned as Dynamics 365 Users and matched to their Contact record by email address. Workers who will only be referenced as resources (not Dynamics logins) remain as Contacts only. The User's security role assignment is determined by the worker's role in MobileWorker.

MobileWorker organizations and client sites — the business entities receiving field service — map to Dynamics 365 Accounts. The Account name, address, phone, and industry fields map directly. Multiple MobileWorker sites belonging to the same client can be mapped to a single Account with site-specific address details stored in a custom Sites__c child object or as custom address fields.

MobileWorker assignments are the primary migration object, mapping to Dynamics 365 Opportunities. Each assignment becomes one Opportunity record. The Opportunity's name derives from the assignment title or a constructed identifier combining the client site and assignment number. The assignment description maps to the Opportunity's Description field. Multiple assignment types can be segmented by Opportunity record type.

MobileWorker assignment state values (unassigned, assigned, dispatched, in-progress, completed, cancelled) map to Dynamics 365 Opportunity StageName pick-list values. Each source state is mapped to the nearest equivalent stage. The mapping is defined before migration in the migration plan. Stage probability and forecast category are applied per the destination business unit's sales process.

MobileWorker assignment priority levels migrate to a custom Priority__c pick-list field on the Opportunity. Dynamics 365 Sales has no native Opportunity priority field, so a custom field is required. The priority values (urgent, high, normal, low) are preserved exactly as they exist in MobileWorker.

MobileWorker skill certifications and qualification tags on workers migrate as custom text or pick-list fields on the Dynamics 365 Contact. If the number of distinct skill types is large, a Skills__c multi-select pick-list or related custom Skills table may be warranted. We surface this choice in the pre-migration schema plan.

MobileWorker assignment GPS coordinates and formatted address map to the Opportunity's address fields (Address1_Name, Address1_Line1, Address1_City, Address1_StateOrProvince, Address1_PostalCode, Address1_Country). Latitude and longitude can be stored as custom decimal fields for geographic reporting. Site-specific locations also map to Account address fields when the site is a client entity.

MobileWorker photo attachments and document uploads on assignments are downloaded and re-uploaded to the Dynamics 365 Opportunity's related SharePoint document location or as Note attachments. Original file names and upload timestamps are preserved as metadata. File size limits in Dynamics 365 apply — files exceeding 25MB are chunked or referenced via URL.

MobileWorker dispatch notes, worker comments, and completion remarks migrate to the Opportunity's Description field. If notes are timestamped and attributable to a specific worker, they can be represented as Dynamics 365 Notes (annotations) with the Contact as the regarding lookup, preserving the attribution and timestamp.

MobileWorker time entries recording labor hours per assignment migrate as a custom Total_Hours__c decimal field on the Opportunity and as individual Task records with Type='Labor' for detailed time-logging. The migration plan determines whether aggregated totals or per-entry activity records best match the business's reporting needs.

MobileWorker custom properties on assignments (any API-accessible field beyond the standard schema) map to custom fields on the Dynamics 365 Opportunity. Field type mapping is determined by the data type: text to string, numbers to decimal or integer, dates to datetime, and pick-lists to pick-list. A migration plan enumerates every custom property and its recommended Dynamics 365 type before migration runs.