Migrate from Dispatch to Pipedrive

Dispatch customer name, email, and phone map directly to Pipedrive person fields. The primary service address on the customer record becomes the person's address fields. Dispatch allows multiple contacts per customer — secondary contacts require a second person record linked to the same organization.

Dispatch customer business name merges into a Pipedrive organization record. The organization's address is populated from Dispatch's primary service location. If Dispatch stores billing and service addresses separately, both are preserved using Pipedrive's address fields and a custom field for the secondary location.

Each Dispatch job becomes a Pipedrive deal. Job name maps to deal title, job status (Scheduled, In Progress, Completed) maps to a Pipedrive pipeline stage value, and the service value or estimated charge maps to deal value. The Pipedrive pipeline is pre-created with stage names matching Dispatch job statuses.

Dispatch job statuses map value-by-value to Pipedrive stage names within the mapped pipeline. Dispatch 'Completed' maps to Pipedrive Won stage, 'Cancelled' maps to Lost, and in-progress statuses map to intermediate stage values. Probability weights on Pipedrive stages are set to match expected outcomes.

Dispatch technician records resolve to Pipedrive users by email match. Unmatched technicians are flagged before migration — either invited to Pipedrive first or assigned as a fallback owner. Technician name and role are preserved in Pipedrive user profile fields. We also capture the technician’s phone number and primary service region for future routing decisions.

Job-level notes in Dispatch migrate as Pipedrive activity notes attached to the corresponding deal or person. Original timestamps and the technician author are preserved. Multiple notes on a single job generate multiple Pipedrive note entries in chronological order. Each note is linked to the deal or person record using the Pipedrive API for direct reference.

Dispatch service completion records — showing what work was done, parts used, and time spent — are mapped as Pipedrive tasks with a completed status. The task subject reflects the service type, and the description field contains the full completion notes. This preserves service history within the Pipedrive activity timeline.

Dispatch service type (e.g., HVAC repair, installation, maintenance) has no native Pipedrive equivalent. We create a Pipedrive deal custom field (e.g., Service_Type__c) as a pick-list populated with Dispatch service type values. This allows filtering and reporting by service category in Pipedrive.

Dispatch priority levels (Urgent, High, Normal, Low) migrate as a custom pick-list field on Pipedrive deals. This maintains service-level context that Pipedrive's standard deal fields do not capture. Priority values are mapped one-to-one with no transformation. We also configure the pick‑list options to match your Dispatch priority taxonomy exactly.

Parts consumed during a service visit are stored as a custom field on the Pipedrive deal. If Dispatch records multiple parts per job, they are comma-separated in the custom field or migrated as a linked product record if a product catalog exists in Pipedrive. This preserves job-cost context for reporting.

Dispatch asset records tied to a customer (equipment serial numbers, model types, installation dates) migrate as custom fields on the Pipedrive person or organization record. This keeps service history attached to the customer record that technicians and account managers both reference.

File attachments on Dispatch jobs — photos, signed forms, work orders — are re-uploaded to Pipedrive as deal files or person attachments depending on attachment context. File size limits on Pipedrive's plan tier apply; large files may require compression or zip packaging before upload.