Migrate from Field Harmony to Pipedrive

Field Harmony scheduling workflows have no Pipedrive equivalent

Field Harmony's smart scheduling, technician dispatch rules, and GPS-based routing are built into the platform's FSM engine and cannot be extracted as portable automation logic. Pipedrive's Automations handle basic assignment triggers and task creation, but GPS routing, SLA-based scheduling, and technician capacity rules require third-party scheduling tools. We export your Field Harmony routing and dispatch logic as a reference document so your Pipedrive admin can rebuild the rules that matter most using Pipedrive Automations or an integrated scheduling layer.

Asset records require custom fields — Pipedrive has no native asset module

Field Harmony tracks equipment, serial numbers, install dates, and asset locations as first-class objects. Pipedrive does not have an asset management module — equipment data has nowhere to land natively. We store asset IDs, serial numbers, equipment types, and service history as custom fields on the Organization record, with active assets also referenced on the related Deal. This preserves the relationship but requires pre-creating custom fields in Pipedrive before data can land.

Pipedrive API rate limits require batched bulk imports

Pipedrive enforces token-based rate limits on the API — limits vary by plan tier, and the specific hourly or daily request caps are set per API token. Migrating thousands of work orders, customers, and assets in a single pass can hit these limits mid-run. We batch import operations and implement exponential backoff on 429 responses. Pre-creating custom fields before the migration run also reduces the number of API calls needed during data insertion.

Multi-status work order flows map imperfectly to Pipedrive's linear stage model

Field Harmony work orders follow non-linear status paths — a work order can be open, then placed on-hold, rescheduled, and dispatched again before completion. Pipedrive Deals move through a linear pipeline: early stages toward won or lost, with won/lost as terminating states that technically allow reopening. Status-to-stage mapping requires decisions about which intermediate Field Harmony statuses get grouped under a single Pipedrive stage and which are dropped. We surface these mapping decisions in the workbook and let your team confirm before migration runs.

Technician records become Person records — not Pipedrive users

Field Harmony technicians are user records inside the platform tied to work order assignments. Pipedrive user accounts are separate from Person records — a technician in Pipedrive is a Person, not a User, unless they are actively using the CRM. We create Person records for each technician and assign Deals to Pipedrive Users by email match for owner tracking, but the technician's access to Pipedrive is a separate setup decision your admin makes after migration.