Migrate from Dispatch Pro to Pipedrive

Dispatch Pro Jobs map directly to Pipedrive Deals. Job name, status, priority, and value carry over. Original Dispatch Pro create date is preserved as a custom datetime field since Pipedrive's CreatedDate reflects migration insertion time. Job ID is stored as Source_System_Job_ID__c for delta-run de-duplication.

Each Work Order in Dispatch Pro becomes a Pipedrive Activity record. Site visits, service calls, and installations map to Tasks with Type='Task' or Events depending on whether the dispatch has a start/end time. The Activity links to the parent Deal (formerly Job) via Pipedrive's deal_id foreign key. Original work-order timestamps are preserved.

Dispatch Pro Customers are split: business name becomes a Pipedrive Organization record, and the individual contact name, email, and phone become a Person record linked to that Organization. B2C customers with no company name create a Person only. The Organization must load before the Person to resolve the org_id foreign key.

Dispatch Pro location addresses — including multiple sites per customer — are merged into the Organization record's address fields. Additional site addresses beyond the primary are stored as Pipedrive custom fields on the Organization since Pipedrive supports one address per Organization record natively.

Dispatch Pro Technicians resolve by email match to existing Pipedrive Users. If the technician email matches a Pipedrive user, the Deal's owner_id maps to that user. Unmatched technicians are flagged pre-migration — the team either creates Pipedrive users or assigns their records to a fallback owner. The technician's Dispatch Pro ID is preserved as a custom field.

Dispatch Pro Job Type labels (e.g., 'HVAC Repair', 'Electrical Install', 'Preventive Maintenance') have no Pipedrive native equivalent. We create a Pipedrive custom pick-list field (Job_Type__c) on Deal, map all source values value-by-value, and preserve the full set of source labels so Pipedrive automations can trigger on specific job types.

Dispatch Pro priority buckets (1–8) are not native to Pipedrive's deal model. We create a custom integer or pick-list field (Dispatch_Pro_Priority__c) on the Deal object and map each priority value directly. Pipedrive's native deal importance flag can supplement this custom field after migration. The original priority values are preserved for reporting, filtering, and use in Pipedrive automation rule conditions to replicate similar follow-up routing based on priority level.

Dispatch Pro invoices and payment status have no Pipedrive equivalent — Pipedrive tracks deal value and expected close date but not line-item invoicing. We preserve invoice amounts and payment status as custom fields on the Deal (Invoice_Amount__c, Payment_Status__c) for historical reporting. Accounting integrations (QuickBooks, Xero) connect separately in Pipedrive.

Dispatch Pro tags on Jobs or Customers map to Pipedrive Labels on the corresponding Deal or Person record. Labels transfer directly as key-value strings. Pipedrive Labels apply across entities so the same tag can appear on both a Deal and a Person if the source tag is attached to multiple object types in Dispatch Pro.

Dispatch Pro file attachments and site photos are downloaded from ServiceTitan storage and re-uploaded to the corresponding Pipedrive Deal or Person as Files. Pipedrive's 25MB per-file limit applies; larger files are flagged before migration. Inline images from notes are re-hosted and linked.