Migrate from Q Dispatch to HubSpot

Q Dispatch stores customer name, phone, email, and address on a single customer record. HubSpot splits these into Contact (name, email, phone, title) and Company (name, domain, industry). We create both and link them via the primary company association on the contact.

Q Dispatch work orders map directly to HubSpot Deals. Job name becomes deal name, job amount becomes deal amount, and job status maps via value-mapping to a HubSpot deal stage pick-list. Original job create date is preserved as a custom property.

Q Dispatch job statuses (Scheduled, In Progress, Completed, Cancelled) map to HubSpot deal stages by value. If Q Dispatch uses custom status labels, we map them to the closest HubSpot stage or a custom pick-list property and document the mapping before migration.

Each line item on a Q Dispatch job transfers to a HubSpot deal line item, preserving the product name, quantity, unit price, and total amount. If Q Dispatch includes a product ID or SKU, we map it to the HubSpot product-record field for linking. The line-item-to-deal association is recreated using HubSpot's line-item relationship endpoint, ensuring that every line item appears under the correct deal in the CRM.

Q Dispatch technician profiles (name, email, certifications, capacity flags) map to HubSpot users by email match. Certification fields become custom user properties in HubSpot. If a technician email doesn't match an existing HubSpot user, the record is flagged for your admin to invite or reassign.

All notes attached to Q Dispatch jobs are migrated as HubSpot deal notes, preserving the original note body, creation timestamp, and author information. File attachments such as images, PDFs, or diagrams are re-uploaded to HubSpot Files and linked to the corresponding deal via the attachment API. After migration, the deal timeline displays the full note history, allowing service teams to review context without switching platforms.

Q Dispatch custom fields on jobs (routing tags, certification requirements, service-type codes) become HubSpot custom properties on the Deal object. We create each custom property in HubSpot before migration and map values field-by-field. Data types are matched: text fields to single-line text, pick-lists to single-select, numbers to number properties.

Q Dispatch stores scheduling windows, preferred time slots, and routing data that has no native HubSpot equivalent. We preserve the raw scheduling data as custom properties on the deal and as a note attachment. Your team decides which scheduling logic to rebuild as HubSpot workflows or a third-party scheduling integration.

Q Dispatch incoming service requests without an assigned job map to HubSpot contacts with an associated deal in an early pipeline stage. The contact holds customer details; the deal holds the estimated job scope. This prevents orphaned records and keeps the service funnel visible in HubSpot.

Q Dispatch job history reports (jobs completed per technician, average job duration) can be summarized as custom properties on the technician's user record in HubSpot or stored as deal-level fields for reporting continuity. We discuss the preferred approach during scoping.