Migrate from Dispatch to HubSpot

Dispatch customer records map directly to HubSpot Company objects. Customer name, phone, and primary contact information migrate as Company properties. Multi-location customers require primary address designation in HubSpot since HubSpot Contacts have a single primary company association. Each customer location from Dispatch that is a separate service site needs a corresponding Contact record with its own address.

Dispatch service locations associated with customers merge into HubSpot Contact records with address properties. If the same customer has multiple service locations, each location gets a separate Contact record linked to the primary Company. Geocoordinates stored as custom properties since HubSpot has no native lat/long fields.

Dispatch job records map to HubSpot Deals. Job name becomes Deal name, job amount maps to Deal amount, and Dispatch job status labels map via value-by-value translation to HubSpot deal stage pick-list values. Job create date preserved as a custom datetime field since HubSpot CreatedDate reflects migration time.

Dispatch uses custom job status labels (e.g., Scheduled, Dispatched, En Route, On Site, Completed, Cancelled) that require one-to-one mapping to HubSpot deal stage pick-list values. Each Dispatch status label is mapped to the nearest HubSpot stage. If Dispatch has statuses HubSpot doesn't support, we create custom stage values in the target pipeline.

Dispatch driver and technician records resolve by email match to HubSpot user accounts for owner assignment. If a Dispatch driver has no matching HubSpot user email, their records assign to a fallback owner or are flagged for team provisioning before migration. Driver name and role stored as a custom property on migrated records for reference.

Dispatch vehicle records (plate, make, model, capacity) have no native HubSpot equivalent. We create a HubSpot custom object named 'Vehicle' or migrate as a custom property group on the Deal or Company record depending on volume. Vehicle-to-driver associations use HubSpot's custom object associations or a junction property.

Dispatch work order completion notes, technician comments, and service details migrate as HubSpot engagement timeline entries — either as Notes with timestamps or as Tasks logged against the associated Deal or Contact. Original Dispatch timestamps preserved so the timeline reflects when work actually occurred.

Dispatch360 Enterprise custom fields per job record map to HubSpot custom properties. Field types are preserved (text, number, date, pick-list) and custom pick-list values map to HubSpot pick-list options. If a Dispatch custom field has no HubSpot equivalent, it migrates as a text property for reference.

Dispatch invoice and payment records associated with jobs migrate as custom properties on the HubSpot Deal (e.g., Invoice_Number__c, Payment_Status__c, Amount_Paid__c). Financial records themselves do not migrate — only the reference data. Billing history surfaces in the Deal timeline as notes.

Dispatch file attachments on job records (photos, signed forms, inspection reports) re-upload to HubSpot Files and associated to the corresponding Deal or Contact record. File size limits per HubSpot's storage tier apply. Inline images in notes are extracted and rehosted as HubSpot file attachments.

Dispatch groupings of drivers or technicians map as a custom pick-list property (e.g., Team__c) on records. HubSpot's native Teams feature separates user access and permissions; Dispatch team groupings are operational labels preserved as record properties rather than security boundaries. This preserves the operational view of team structure without altering HubSpot's access model.

Dispatch preventive maintenance schedules and recurring job templates have no direct HubSpot equivalent. PM data migrates as reference properties on the associated Deal or Contact. Recurrence logic needs to be rebuilt in HubSpot using Workflows (if triggering on date properties) or documented for the operations team to handle manually.