Migrate from Mobile Worker to Microsoft Dynamics 365 Sales

Mobile Worker worker profiles map directly to D365 Contacts. Worker name, email, phone, and role fields translate in a one-to-one mapping to the corresponding Contact fields. If the worker is also a customer contact in the system, the record duplicates to both the Contact entity and any associated Opportunity records to preserve both worker and customer relationships in the destination CRM.

Workers who are D365 Sales licensed users are matched by email address to existing SystemUser records. Workers without a D365 user license become Contacts only without SystemUser linkage. OwnerId on migrated Opportunities resolves to the matched SystemUser, ensuring job ownership maps correctly in the destination system.

Each Mobile Worker job translates to a D365 Opportunity with the job name serving as the Opportunity Name. Job status values (Dispatched, In Progress, Completed) map via value mapping to the corresponding Opportunity StageName picklist entries. Job address fields map to the Opportunity's Address1 composite address field.

If Mobile Worker stores the customer company inside the job record without maintaining a standalone company object, FlitStack extracts the embedded customer name and address to create an Account record first. The migrated Opportunity then links to this Account via AccountId, establishing the proper CRM relationship structure in D365.

Mobile Worker dispatch assignments containing assigned worker, job reference, and time window translate to a custom FieldDispatch table in Dataverse linked to the Opportunity. This preserves scheduling context. Note that Dynamics 365 Sales Professional limits custom tables to 15—Enterprise licensing removes this constraint.

Time entries logged against a Mobile Worker job migrate as D365 Tasks attached to the corresponding Opportunity via the Regarding lookup. Original clock-in and clock-out timestamps are preserved as custom datetime fields on the Task, maintaining the complete labor tracking history.

Mobile Worker geo-positioning logs migrate to a custom WorkerLocation table in Dataverse linked to the Contact record. Dynamics 365 Sales has no native location-history entity, so these records serve as audit trails and compliance documentation for field service operations.

Work order photos, signed forms, and file attachments export from Mobile Worker and re-upload to D365's SharePoint integration or the Notes (annotation) entity attached to the corresponding Opportunity. Standard file size limits of the destination apply during the upload process.

Mobile Worker custom fields per job—such as job_type, crew_size, or equipment_used—map to custom columns on the Opportunity table in Dataverse. Field type mapping applies consistently: text fields become nvarchar, numeric fields become decimal, and date fields become datetimeoffset.

Worker skill ratings and certifications stored in Mobile Worker map to a custom WorkerSkill table in Dataverse linked to Contact. These skill records can be referenced by D365 Field Service resource scheduling optimization when that module is added to the tenant post-migration.

Mobile Worker stores customer name, phone, and email inside each job record rather than as standalone entities. FlitStack normalizes this by extracting all unique customer values across jobs, deduplicating by email match, creating corresponding Account and Contact records, and then linking each migrated Opportunity to the resolved Account.