Migrate from Q Dispatch to Salesforce Sales Cloud

Q Dispatch Customer maps 1:1 to Salesforce Account. The primary service address from Q Dispatch migrates to Account.BillingAddress; secondary job-site addresses require a custom Service_Address__c field or nested Account Address object for multi-location customers. Additional fields like customer credit status, preferred service windows, and account manager assignments can be mapped to custom fields on Account if your Q Dispatch instance captures those attributes.

Q Dispatch contact records (site contacts, billing contacts, dispatch recipients) map to Salesforce Contact. Each Contact links to the parent Account via AccountId. Multiple contacts per customer collapse to individual Contact records with role-designation custom fields. The primary contact flag from Q Dispatch migrates to a Is_Primary_Contact__c custom field on Contact.

Q Dispatch jobs map to Salesforce Case in the field-service context. Case.Priority maps from job urgency level. Case.Origin maps from job creation channel. Case.Subject carries the job title. Salesforce Field Service objects (WorkOrder, WorkOrderLineItem) are an alternative destination if your org has FSM licensed.

Q Dispatch status values (Pending, Assigned, En Route, In Progress, Completed, Cancelled) map to a custom Work_Order_Status__c pick-list on Case. Each value is mapped individually. Completed timestamp from Q Dispatch becomes Case.ClosedDate; the original Q Dispatch status-change timestamps migrate as audit custom fields.

Q Dispatch Technician records resolve to Salesforce User by email match. Unmatched technicians are flagged before migration. Active technician status maps to User.IsActive; skill certifications from Q Dispatch migrate as custom pick-list or text fields on User for dispatch-skill matching in Salesforce Field Service.

Multi-technician job assignments in Q Dispatch require a custom junction object (Job_Technician__c) linking Case to User with a Role__c field (Primary, Secondary, Helper). This is surfaced in the migration plan; single-technician assignments map directly to Case.OwnerId. The junction object also supports an Hours_Worked__c field to track time allocation per technician on multi-technician jobs.

Q Dispatch appointment windows map to Salesforce Event with Event.StartDateTime and Event.EndDateTime preserved. The technician assigned to the appointment links via Event.OwnerId. All-day scheduling events use Event.IsAllDayEvent = true. Service-type notes from the appointment migrate to Event.Description. Recurring appointment patterns in Q Dispatch are noted for Flow-based recreation in Salesforce.

Q Dispatch service line items (labor type, materials, flat-rate services) require a custom Work_Order_Line_Item__c object with fields: Service_Type__c, Rate__c, Quantity__c, Total__c. This object links to Case via CaseId lookup and carries the pricing logic that lives inside the Q Dispatch job record.

Q Dispatch job notes map to Salesforce CaseComment on the parent Case. File attachments (photos, signed forms, job-site documents) re-upload to Salesforce Files via ContentVersion linked to the Case via ContentDocumentLink. Image attachments are stored with their original MIME type preserved in ContentVersion.FileType for downstream processing by field technicians using the Salesforce Mobile app.

Q Dispatch custom properties on jobs (e.g., Equipment_Model__c, Parts_Used__c, Site_Conditions__c) map to custom fields on Case with the __c suffix. Each custom property is reviewed for Salesforce data type (text, pick-list, number) and a corresponding custom field is created in the destination org before data loads.