Migrate from Q Dispatch to Microsoft Dynamics 365 Sales

Q Dispatch company records map directly to Dynamics 365 Sales Accounts. Company name becomes Account Name; physical address fields map to Address composite fields in Dataverse. Multi-location Q Dispatch customers (branch offices) map to one Account with multiple Address1/Address2 lines or child Account records via Parent Account relationship.

Q Dispatch service contacts (site contacts, billing contacts) map to Dynamics 365 Sales Contacts. The Contact's AccountId links to the parent Account record migrated from the Q Dispatch Customer. Email, phone, and role fields migrate as standard Contact fields; contact type labels from Q Dispatch (e.g., site manager, billing contact) migrate as a custom Contact_Type__c pick-list.

Q Dispatch work orders are the primary migration object. In Dynamics 365 Sales Enterprise, they map to a custom Service_Order__c table keyed to Account and Contact lookups. In Sales Professional (15-table limit), active open work orders map to Opportunities with a Work_Order_ID__c custom field. Historical closed jobs migrate as historical Opportunities with a Closed_Date__c and Status = 'Won' or 'Lost' for reporting continuity.

Each Q Dispatch work order may have multiple line items (parts, labor, travel). These merge into Opportunity Product records in Dynamics 365 Sales if a product catalog exists. If no product catalog is present, service lines migrate as a custom Service_Line__c table with a lookup to Service_Order__c, storing description, quantity, and unit_price fields directly.

Q Dispatch technicians map by email match to Dynamics 365 Sales SystemUser records, which resolve the OwnerId on Accounts, Contacts, and Opportunities. If a Q Dispatch technician has no matching Dynamics user, they are flagged for admin resolution before migration. For teams that maintain a technician roster distinct from CRM users, a custom Technician__c table is created in Dynamics 365 Sales Enterprise.

Q Dispatch dispatch board assignments (technician, time window, job location) have no native Dynamics 365 Sales equivalent. We store dispatch schedule data as custom fields on the Service_Order__c record: Scheduled_Technician__c (lookup), Schedule_Date__c (date), Time_Window_Start__c, Time_Window_End__c, and Route_Sequence__c (integer). Office staff reviewing post-migration data can build Power Apps dispatch boards referencing this data.

Q Dispatch job statuses (Unassigned, Scheduled, En Route, In Progress, Completed, Cancelled) have no direct Dynamics 365 Sales equivalent. We create a custom Work_Order_Status__c pick-list on the Service_Order__c table with value-by-value mapping to Q Dispatch status strings. Probability and forecast category are derived from status values — completed jobs receive 'Won' stage; cancelled jobs receive 'Lost'.

Technician notes and dispatch comments from Q Dispatch migrate as Dynamics 365 Sales Notes attached to the parent Service_Order__c or Opportunity. Rich-text formatting in Q Dispatch notes is preserved as HTML in the Note 'notetext' field. Long-form job narratives requiring structured fields migrate to a custom Service_Note__c table in Dynamics 365 Sales Enterprise.

Q Dispatch invoices do not map to Dynamics 365 Sales standard objects without Business Central. We preserve invoice data as a custom Invoice__c table (Sales Enterprise) or as a JSON blob in a long-text field on the Service_Order__c record. For teams migrating to Business Central post-Dynamics 365 Sales, invoice records are staged for a second-phase import into the Business Central Sales Invoice table.

Q Dispatch route assignments and geographic service zones map to a custom Route_Zone__c pick-list on the Service_Order__c record. Zone names from Q Dispatch are preserved as pick-list values; latitude/longitude coordinates, if stored, migrate to custom Lat__c and Long__c decimal fields for post-migration Power BI territory mapping.

Every migrated record receives a Source_System_ID__c custom field storing the Q Dispatch internal record ID. This field enables delta-run de-duplication (if the same record is updated in Q Dispatch during cutover), cross-referencing for audit trails, and one-click rollback targeting specific records without a full re-import.