Migrate from Q Dispatch to Pipedrive

Q Dispatch customer records with name, email, phone, and address map directly to Pipedrive People. Customers with multiple service locations retain the primary address on the Person record; additional locations stored as custom fields on the Person or as notes for reference.

Q Dispatch customer organizations map to Pipedrive Organizations — the corporate parent of the Person record. Business address, industry, and employee count map to Organization fields. Organization-level custom fields on Q Dispatch create equivalent Pipedrive custom fields. These mappings ensure that corporate details are visible on every associated Person and Deal record.

The Q Dispatch work order is the primary record for migration. Work order ID, title, job description, and quoted/actual amount map to Pipedrive Deal fields. The work order status (Scheduled, In Progress, On Hold, Completed, Cancelled) maps to a Pipedrive pipeline stage. Each work order lands as one Deal.

Q Dispatch work order status values (Scheduled, In Progress, On Hold, Completed, Cancelled) map value-by-value to Pipedrive deal stage pick-list values. The mapping is defined during planning — if Q Dispatch uses custom status names, each one is mapped explicitly to an existing or newly created Pipedrive stage.

Q Dispatch service addresses attached to individual work orders are stored as a combined string in the source. FlitStack parses street, city, state, and zip, then populates the Organization address fields where the address is the customer's primary location. Work-order-specific service addresses also populate a Pipedrive Deal custom field (Service Address __c) so the job-specific location is visible on the deal record.

Q Dispatch technician assignments map to Pipedrive User as the deal owner (OwnerId). Resolution happens by matching the technician's email address in Q Dispatch to an active Pipedrive user account. Unmatched technicians are flagged before migration — your team either creates Pipedrive users first or assigns those deals to a fallback owner.

Q Dispatch job history entries — technician check-ins, status changes, notes — migrate as Pipedrive Activities. Each history event becomes a Task or Call activity type on the migrated deal, with the original timestamp and the technician name as the activity owner. Inline comments on jobs surface as Activity notes.

Q Dispatch job type or service category values (e.g., HVAC Repair, Preventive Maintenance, Installation) have no native Pipedrive equivalent. We create a Pipedrive Deal custom field (Job_Type__c) as a pick-list, map every source value to a corresponding pick-list option, and apply the mapping during the migration.

Q Dispatch priority levels (e.g., Emergency, High, Normal, Low) migrate as a Pipedrive Deal custom field (Priority__c) with the source values preserved as pick-list options. This field is visible on the deal for sorting and filtering in Pipedrive's pipeline view.

Q Dispatch notes and internal comments attached to work orders migrate as Pipedrive Notes linked to the corresponding deal. The note creator and original creation timestamp are preserved. Rich-text formatting in Q Dispatch notes is converted to plain text to ensure compatibility with Pipedrive's Note model.

Q Dispatch file attachments and job photos associated with work orders are re-uploaded to the corresponding Pipedrive deal as attachments. File size limits follow Pipedrive's attachment constraints (25 MB per file). Large photo sets are preserved in batches to avoid timeout errors.

Q Dispatch scheduling and technician-routing rules have no Pipedrive equivalent — Pipedrive has no native scheduling or route-optimization engine. We export the scheduling rule configuration as a structured reference document that your team can use to configure Pipedrive Automations for appointment-setting workflows.