Migrate from Dispatch Pro to Salesforce Sales Cloud

Dispatch Pro Customers map to Salesforce Account records for companies or business entities. Individual customers with no company affiliation store as a Salesforce Contact with an 'Unassigned Account' placeholder AccountId. Customer contact details (name, phone, email) map directly; the service location decomposes into Account's shipping or billing address fields.

The Job record is the primary migration entity. Dispatch Pro job status (Scheduled, In Progress, Completed, Cancelled) maps to Salesforce Case Status pick-list via value mapping. Job priority levels (Emergency, High, Standard) map to Case Priority. Original job number from Dispatch Pro is stored as Source_Job_Number__c for reconciliation. The job's primary technician resolves to Case.OwnerId via email match to a Salesforce User.

Dispatch Pro line items for materials and labor attach to the Case as a custom Line_Item__c child object with fields for description, quantity, unit price, and total. This preserves the full billing breakdown from Dispatch Pro and allows Salesforce admins to surface line items in Case reports or link them to Opportunities if the business quotes and bills from Salesforce.

Dispatch Pro technician records do not map directly to Salesforce Users because technician skill sets, trade licenses, and zone assignments have no native Salesforce equivalent. We migrate the technician identity to a Salesforce User record (matched by email) and create a Skill__c custom object to preserve skill tags, certifications, and service zones. This separation lets the Salesforce admin expose skills via a related list on the User page layout without overloading the User object.

Dispatch Pro service addresses associated with jobs migrate to the linked Salesforce Account's ShippingAddress or a separate Location custom object when the same customer has multiple service sites. Address components (street, city, state, zip) map to Salesforce's standard address compound field. If Dispatch Pro stores geo-coordinates, those migrate to Latitude__c and Longitude__c custom fields for routing or mapping integrations.

Dispatch Pro's job timeline — each status transition with timestamp and technician name — is reconstructed in Salesforce as a combination of Case History (for field-level changes) and Event records (for significant milestones such as arrival, departure, and job completion). Original timestamps and actor names are preserved so the Salesforce Case timeline reflects the complete job lifecycle as experienced in the field.

Dispatch Pro signature captures on completed jobs download as image files and re-upload to Salesforce as ContentVersion records linked to the Case via ContentDocumentLink. Signature metadata (captured date, signing party name) stores as custom fields on the ContentVersion record for compliance and audit trail purposes.

Job photos, PDFs, and documents from Dispatch Pro are downloaded and re-hosted in Salesforce Files (ContentVersion/ContentDocument). They attach to the corresponding Case via ContentDocumentLink. Salesforce's 25MB per-file limit applies; files exceeding this threshold are flagged and split into multiple attachments. Inline images in job notes are extracted and stored separately to preserve visual documentation.

Any Dispatch Pro custom properties on jobs — such as warranty codes, permit numbers, or equipment serial numbers — migrate to Salesforce custom fields with the __c suffix on the Case object. The migration plan enumerates every Dispatch Pro custom property before data moves and your Salesforce admin pre-creates the corresponding fields so validation runs cleanly on the first pass.

Dispatch Pro invoices map to Salesforce Order records when the business uses Salesforce's native quote-to-cash flow. Invoice line items decompose to OrderItems. When Salesforce Orders are not in use, invoices migrate as a custom Invoice__c object with a lookup to the Case for traceability. Payment status and amounts are preserved as custom fields on the relevant record.

Dispatch Pro's automated playbook rules (auto-assignment triggers, SLA escalation timers, customer notification workflows) have no Salesforce equivalent that migrates automatically. We export the full playbook definition as a structured JSON document your Salesforce admin can use as a reference when building equivalent Flows in Salesforce.

Dispatch Pro's reporting and dashboard definitions — dispatch board views, technician utilization charts, job-cycle-time reports — do not transfer to Salesforce. The underlying data (jobs, technicians, timestamps) migrates completely, giving your Salesforce admin a clean base to build equivalent reports in Salesforce Reports & Dashboards or Tableau CRM.