Migrate from Mobile Service App to Microsoft Dynamics 365 Sales

Mobile Service App customer records map 1:1 to Dynamics 365 Accounts. The customer's primary contact information migrates as the Account's primary contact lookup. Multi-location customers may require Account hierarchy setup with a parent Account record created first, followed by child Customer Address records for each service location.

Mobile Service App service locations attach to customers and store address, contact person, and site-specific notes. When a customer has multiple service locations, we create the parent Account first, then add Customer Address records (logical child) for each site. Site-specific notes become custom fields on Customer Address or as notes attached to the parent Account.

Work orders map to Dynamics 365 Field Service Work Order if Field Service is provisioned, otherwise to native Case/Incident entities. Work order status (Open, In Progress, Completed, Cancelled) maps to Case Status field values. Service type, priority, and scheduled dates become custom fields or mapped attributes depending on the destination schema.

Mobile Service App technician profiles map to Dynamics 365 Users (systemuser entity). Resolution happens by email match — the technician's email in Mobile Service App must match a user's email in Dynamics 365. Unmatched technicians are flagged before migration so your admin can either create Dynamics users first or assign records to a fallback user.

Mobile Service App parts and inventory items map to Dynamics 365 Products. Unit of measure (uomscheduleid) and pricing fields transfer as Product's default unit and price list entries. Parts linked to work orders create Product liability or are referenced via manual line-item notes since Case doesn't natively support product-invoice relationships without an Opportunity or Order.

Field service visits logged in Mobile Service App map to Dynamics 365 Activities — specifically Appointment entities for scheduled visits with start/end times, and Task entities for completion confirmations. Original timestamps, assigned technician (owner), and parent customer lookup are preserved on the migrated activity records.

Text notes and file attachments on Mobile Service App work orders migrate as Dynamics 365 Notes (annotation entity) and Attachments (activitymimeattachment). File size limits apply — Dynamics 365 default is 10MB per file for notes attachments. Large files or inline images are downloaded, rehosted in SharePoint or Dynamics cloud storage, and linked by URL.

Mobile Service App location-level contact persons map to Dynamics 365 Contacts. The contact's email and phone migrate as standard fields. Contacts are associated to the parent Account via the parentcustomerid lookup. If the same person appears across multiple service locations, a primary contact is assigned to the parent Account; others become Account Contact Relationships.

Mobile Service App custom fields and extended properties that have no direct Dynamics 365 equivalent are preserved as custom fields on the target entity (Account, Contact, Case, Product, or custom table). We use the field label as the display name and a normalized API name. Custom field type mapping: text strings to Text(2000), numeric values to Decimal, dates to DateTime, and pick-lists to Option Sets with values mapped individually.

Mobile Service App billing records and invoices do not map directly to Dynamics 365 Sales entities because Field Service billing typically requires integration with Dynamics 365 Finance or a separate ERP. We preserve billing data as a custom entity or exported to a staging table in Dataverse for your finance team to reconcile with Business Central or another accounting system.

The Mobile Service App scheduling board (time slots, technician assignments, route optimization) has no direct Dynamics 365 Sales equivalent — native scheduling requires Dynamics 365 Field Service with the Schedule Board add-in. We map technician availability and work order assignments as data; the scheduling board UI must be recreated in Dynamics 365 Field Service or via Power Apps.

Customer signatures captured in Mobile Service App (typically images or PDFs attached to completed work orders) migrate as Dynamics 365 Attachments on the Case or as Notes with the signature image embedded or linked. Signature capture data is preserved for compliance and service audit purposes.