Migrate from Jobsite Mobile to Microsoft Dynamics 365 Sales

Jobsite Mobile contacts map directly to Dynamics 365 Contact records. Every contact must have a parent AccountId — contacts without a primary company link are attached to a placeholder 'Unassigned Account' in Dynamics. Email, phone, job title, and address fields migrate as direct text fields. OwnerId is resolved by email match against Dynamics users.

Jobsite Mobile companies map to Dynamics 365 Account records. Company name becomes Account.Name; domain/website maps to Website; industry pick-list values map value-by-value to Dynamics Industry pick-list where matches exist. Parent-company hierarchies in Jobsite Mobile map to Account.ParentAccountId in Dynamics, requiring parent records to migrate first to avoid circular-reference errors.

Jobsite Mobile work orders do not have a direct Dynamics 365 Sales equivalent — they are project or job records, not sales opportunities. FlitStack maps them to a custom Dataverse table named 'new_WorkOrder' with a 1:1 field mapping. The original work-order number is preserved as new_WorkOrderNumber. Work-order status transitions are logged as custom datetime columns (new_StatusChangedOn) for reporting continuity.

Each line item on a Jobsite Mobile work order (materials, labor hours, equipment charges) maps to a custom Dataverse table record linked to the work-order table via a lookup column (new_WorkOrderId). Quantity, unit price, and line total migrate as new_Quantity, new_UnitPrice, and new_LineTotal decimal fields.

Jobsite Mobile assets (equipment, vehicles, site equipment) that are used in work orders map to a custom Dataverse 'new_Asset' table with serial number, location, and status fields. Assets that are also sellable products (spare parts, consumables) additionally map to the Dynamics Product table with the new_AssetId cross-reference stored for traceability.

Jobsite Mobile user accounts — including technicians, dispatchers, and admins — are resolved against Dynamics 365 SystemUser records by email address. If a Jobsite Mobile user has no matching Dynamics user, FlitStack flags the record and assigns it to a migration fallback owner until your admin provisions the user in Dynamics.

Jobsite Mobile tracks each status change on a work order with a timestamp and the user who made the change. Since Dynamics 365 has no native status-history audit table for custom tables, FlitStack creates a custom column set (new_StatusHistoryJson or separate new_LastStatusChangeDate / new_LastStatusChangeBy fields) to preserve this history as structured data in the migration.

Files and photos attached to work orders in Jobsite Mobile are downloaded and re-uploaded to Dynamics 365's SharePoint-connected annotation store (the Annotation entity). Original filenames and MIME types are preserved. Files exceeding Dynamics' 25 MB per-attachment limit are split or referenced via external URL fields on the work-order record.

Jobsite Mobile custom fields on work orders — such as site_access_instructions, permit_number, inspection_required — are created as new_ columns in the custom work-order Dataverse table before migration. Field data types are matched: text to string, pick-lists to choice columns, dates to datetime columns, checkboxes to two-option columns.

Jobsite Mobile workflows (e.g., automatic work-order assignment when a status changes, reminder triggers, notification rules) have no direct equivalent in Dynamics 365 Sales. FlitStack exports workflow definitions as JSON and provides a mapping document showing the Power Automate trigger/action equivalent for each Jobsite Mobile rule.

Jobsite Mobile stores GPS coordinates for work-order locations and technician route data. This is preserved as new_SiteLatitude and new_SiteLongitude decimal fields on the work-order table. Routing and dispatch visualization requires Dynamics 365 Field Service or a Power Apps Canvas app — not included in the migration scope.

If Jobsite Mobile contains invoiced work orders, the line-item data maps to Dynamics 365 Sales Invoice or Order records (InvoiceDetail lines). Status (Paid, Outstanding) maps to the Invoice Status field. The original Jobsite Mobile invoice number is stored as new_JobsiteInvoiceNumber for reconciliation against source records.