Migrate from Dispatch Pro to HighLevel

Dispatch Pro customer records map directly to HighLevel Contacts and Company records. The customer's primary address becomes the contact address fields. For customers with multiple service locations, we create one primary contact and additional Locations as custom fields or separate Company records.

Dispatch Pro Jobs become HighLevel Opportunities. Job name maps to Opportunity name; job amount maps to Opportunity value; job status maps to a pipeline stage. The job type (e.g., Service, Installation, Warranty) requires a custom field in HighLevel since pipeline stages alone cannot encode job-type variance.

Dispatch Pro job types such as service, replacement, warranty, and recall have no direct HighLevel equivalent in the Opportunity model. We create a Job_Type__c pick-list custom field on the Opportunity object and map each Dispatch Pro job type to the corresponding pick-list value during migration. This preserves job-type classification for filtering and reporting in HighLevel.

Dispatch Pro technicians map to HighLevel Users/Staff. Owner resolution happens by email match — each technician's Dispatch Pro email is matched to a HighLevel user account. Unmatched technicians are flagged before migration so your team can create HighLevel accounts first.

Dispatch Pro skill sets such as HVAC certified and electrical licensed have no native HighLevel equivalent on User records. We create a Skills__c multi-select custom field on the User object and populate it from Dispatch Pro's technician skill list during migration. This allows HighLevel Workflow triggers to parse this field for routing decisions.

Dispatch Pro zones and business units govern which technicians see which jobs. HighLevel has no native zone model. We create zone/business-unit custom fields on both User and Opportunity objects, enabling Workflow triggers to filter assignments by region after migration. This maintains routing continuity post-migration.

Dispatch Pro arrival windows (e.g., 2-hour windows) encode scheduling expectations on each job. HighLevel Appointment Calendars can represent these windows, but they are not tied to dispatch optimization. We migrate arrival window data as a text field on the Opportunity and as calendar events for scheduling continuity.

Dispatch Pro supports up to eight priority buckets that govern job sequencing in the routing optimizer. HighLevel Opportunities have no native priority field. We create a Priority__c pick-list custom field and map the Dispatch Pro priority bucket value during migration.

Dispatch Pro auto-lock sets the lead time (in minutes) before a job start during which Dispatch Pro stops moving the appointment. Max drive time limits how far a technician travels for a job. These are Dispatch Pro routing parameters with no HighLevel equivalent — they migrate as numeric custom fields on the Opportunity for reference.

Dispatch Pro customer tags drive ACP (Adjustable Capacity Planning) logic and migrate as HighLevel contact tags. ACP-specific flags encoding capacity parameters such as no-visit windows become custom fields on the Contact since HighLevel has no native ACP model. Post-migration, ACP rules must be rebuilt as HighLevel Workflow conditions.

Job history including service notes, completion records, and photos attached to jobs migrates to HighLevel Tasks and Notes linked to the Contact. Photos re-upload to HighLevel's file storage and link to the contact record. Original timestamps and technician owners are preserved on each activity record for audit continuity.

Dispatch Pro's routing optimizer settings (priority bucket weights, ACP capacity settings, troubleshooter alert thresholds) are ServiceTitan internal configuration. They do not export via API and have no HighLevel equivalent. We document the current routing configuration as a PDF reference for manual rebuild in HighLevel Workflows.