Migrate from Dispatch to Salesforce Sales Cloud

Dispatch customers migrate as Salesforce Accounts. Company name maps directly to Account.Name. Billing address, phone, and website transfer to standard Account fields. If Dispatch stores multiple contacts per customer, additional contacts migrate as Salesforce Contacts linked by AccountId.

Dispatch location records — site name, full address, latitude, longitude, and access notes — require decomposition. Street, city, state, and postal code map to Account.BillingStreet and custom fields. Site name and coordinates become custom fields on Account or a custom Address object linked by lookup relationship.

Dispatch jobs and work orders are the primary migration record and map 1:1 to Salesforce Cases. Case object fields cover status, priority, and description. Dispatch-specific attributes — job type, service category, assigned driver, scheduled window — migrate as custom fields on Case with original Dispatch IDs stored in Source_System_ID__c.

Dispatch job tasks or line items attached to a single job collapse into custom fields on the parent Case record. If Dispatch supports multiple line items per job with independent pricing and status, we create a custom Job_Line_Item__c object linked to the Case by lookup, preserving each task's status and description separately.

Drivers require a decision point. If drivers represent billable entities or subcontractors with their own records, they map to Salesforce Contacts with a custom Driver_Role__c flag. If drivers are operational assets rather than CRM contacts, we create a custom Driver__c object with certifications, safety scores, and availability as custom fields.

Dispatch vehicle records — license plate, vehicle type, capacity, and maintenance schedule — map to Salesforce Asset linked to the Account if vehicles are customer-sited equipment. For operational fleet vehicles without direct customer association, we create a custom Vehicle__c object with make, model, capacity, and status fields.

Dispatch route records and route logs have no direct Salesforce equivalent. We create a custom Route__c object capturing route name, date, start and end location, and total distance, then link individual jobs (Cases) to their route via a lookup field on the Case record.

Dispatch job notes, driver check-ins, and status-change logs migrate as Salesforce Tasks with Type='Job Note'. Time-stamped activity records map to Events. Rich-text job descriptions migrate as Salesforce Notes. Original timestamps and owner IDs are preserved on each activity record.

Any Dispatch custom fields attached to jobs — service category, work type, permit requirements, customer-specific instructions — create corresponding custom fields on the Salesforce Case object using the __c suffix. We create these fields in Salesforce during the schema setup phase before data loads begin.

Dispatch file attachments and photos attached to jobs re-upload to Salesforce as Salesforce Files linked to the corresponding Case record. File size limits at the destination apply; we chunk large files and flag any that exceed Salesforce's 25MB per-file default limit.

Dispatch dispatcher and admin users resolve to Salesforce Users by email address match. Unmatched users are flagged before migration so your team either invites them to Salesforce first or reassigns their records to a fallback owner. Dispatcher metadata without a Salesforce User match migrates as a custom Contact or custom Dispatcher__c record.

Any custom objects defined inside Dispatch — such as custom job categories, permit records, or equipment logs — migrate 1:1 to Salesforce custom objects. Custom object associations that use a many-to-many model in Dispatch require Salesforce junction objects when the relationship is also N:N in the destination.