Migrate from Dispatch Pro to Microsoft Dynamics 365 Sales

Dispatch Pro customers (business entities receiving service) map directly to Dynamics 365 Account records. The customer name, primary address, phone, and website transfer as Account.Name, Address fields, Telephone1, and WebsiteURL. Dispatch Pro customers without a company name default to a placeholder AccountName so the record is valid in Dynamics.

Named contacts on a Dispatch Pro customer map to Dynamics 365 Contact records linked via AccountId. Dispatch Pro stores the contact name, email, phone, and role (e.g., Site Manager). These transfer to Contact.FirstName, EmailAddress1, Telephone1, and JobTitle. A customer with no named contacts generates at least one Contact record with the customer's business name as a fallback.

Each Dispatch Pro Job becomes a Dynamics 365 Opportunity. The Job Name maps to Opportunity.Name; the scheduled start and end windows map to estimatedclosedate or custom datetime fields. Job status (Scheduled, In Progress, Completed, Cancelled) maps via a value-mapping table to Opportunity.StatusCode. Job Priority (Low through Critical) requires a custom Opportunity.Priority__c pick-list field because Dynamics 365 has no native priority field on the Opportunity entity.

Dispatch Pro job types (e.g., Repair, Maintenance, Installation) have no direct Dynamics 365 equivalent. We map them to a custom text or pick-list field on the Opportunity (new_servicetype__c). If the job type implies a specific product catalog item, we also create an OpportunityProduct line so Dynamics 365 can track the service line alongside the opportunity amount.

Dispatch Pro technician records resolve by email match to existing Dynamics 365 SystemUser accounts. Each technician's user record in Dynamics 365 is the OwnerId on the migrated Opportunities. Unmatched technicians are flagged before migration — teams either pre-create their Dynamics 365 user accounts or a fallback technician owner handles orphaned records until assignment is corrected post-migration.

Dispatch Pro Business Units represent regional or departmental cost centers that control dispatch access and reporting. Dynamics 365 has both Teams (lightweight, record-sharing) and Business Units (full hierarchy, security role inheritance). We recommend mapping each Dispatch Pro Business Unit to a Dynamics 365 Team initially, associating migrated Opportunities with the appropriate team so regional accountability survives the cutover without triggering Dynamics 365's full Business Unit hierarchy rebuild.

Dispatch Pro Zones define geographic service areas for routing optimization. Since Dynamics 365 has no native zone entity, we create a custom text field (new_zone__c) on the Opportunity and populate it from Dispatch Pro. Zone-to-territory routing logic that Dispatch Pro handles automatically must be rebuilt as Power Automate flows or Dynamics 365 territory management post-migration.

Dispatch Pro's job timeline events (check-in, check-out, status changes, technician notes, signature captures) migrate as Dynamics 365 Annotations on the related Opportunity. Structured events with a date and assignee (e.g., a scheduled follow-up call after job completion) create Task or Appointment records. Original timestamps are preserved in the annotation body so audit continuity is maintained.

Dispatch Pro stores job photos and signed forms in ServiceTitan's blob storage. Dynamics 365 can attach files to Opportunity records via Dataverse annotations or SharePoint document management. We export the files, upload them to the target SharePoint site or Dataverse file field, and link each file to its parent Opportunity record. The original file names and upload timestamps are preserved for traceability.

Dispatch Pro custom job properties (e.g., equipment model, refrigerant type, permit number) map to custom Dataverse columns on the Opportunity table. Each custom property becomes a new_ColumnName__c column with a type determined by the source data (text, number, pick-list, date). If a custom property uses a pick-list in Dispatch Pro, we create a matching pick-list in Dataverse and run a value-mapping pass during data load so the enumerated values are consistent across records.

Dispatch Pro stores service locations separately from the billing customer. The service address maps to the Account's Address1 fields (Address Line, City, State, Postal Code, Country). If a service location differs from the billing address, we create a separate Account record flagged as a service location (new_isservicelocation__c = true) so both billing and on-site addresses are preserved without duplication.

Dispatch Pro job estimates transfer as Dynamics 365 Quote records linked to the migrated Opportunity. The quote amount, line items, and status (Draft, Sent, Accepted, Lost) map to Quote columns. If the Dispatch Pro estimate was converted to an invoice, we also create a corresponding SalesOrder or Invoice record in Dynamics 365 to preserve the full billing history.