Migrate from Fieldy to Pipedrive

Fieldy stores each customer contact as a flat record with company details embedded. We split these into a Pipedrive Person record (name, email, phone, title) and an Organization record (company name, domain, address). The organization is created first so the person can link via the org_id field on import.

Fieldy Jobs map to Pipedrive Deals as the primary migration object. Each job carries customer, staff, location, status, priority, and line items. In Pipedrive the deal holds the work summary, linked person, and linked organization, with custom fields capturing the FSM-specific metadata that Pipedrive's native schema does not cover.

Fieldy job lifecycle states — Scheduled, In Progress, On Hold, Completed, Cancelled — map value-by-value to Pipedrive deal stages. We match the source status labels to existing Pipedrive stage names or create new stages that mirror Fieldy's workflow, preserving the original transition sequence for reporting continuity.

Fieldy job priority (Low, Medium, High, Urgent) has no native Pipedrive equivalent. We create a Priority__c custom field on the Deal object and populate it from Fieldy's priority value. This field is visible on the deal detail view and usable in Pipedrive filters and automation conditions.

Fieldy work-order line items — parts, labor, service fees — migrate as Pipedrive Products. Each product carries name, code, pricing, and currency. During deal migration, products are attached to the deal via the deal_product association so the deal view shows the full service itemization.

Fieldy Staff records represent field technicians and dispatchers. We resolve staff by email against Pipedrive users and assign migrated records to the matched owner. Unmatched staff are flagged as a pre-migration action — either invite them to Pipedrive first or assign their jobs to a fallback owner.

Fieldy site visits, service appointments, and scheduled activities migrate as Pipedrive Activities (Task type). Each activity records the subject, due date, assigned user, and linked deal. Original visit timestamps and duration data are preserved in the activity notes field for service-history continuity.

Fieldy job descriptions and internal notes are written to Pipedrive Deal Notes. Notes preserve the original text, author (where resolvable), and creation timestamp. Rich-text formatting from Fieldy is flattened to plain text to ensure clean rendering in Pipedrive's note format.

Fieldy stores the job site address separately from the customer address. The service-site address is preserved as a custom text field on the Pipedrive Deal. The customer address remains on the Organization record. If Fieldy stores GPS coordinates, these migrate to a custom lat-long text field for reference.

Fieldy's live dispatch board, GPS technician location, and route-optimization data have no Pipedrive equivalent. Historical location snapshots can be written to custom datetime-stamped text fields on the deal as an audit record, but the real-time dispatch board cannot be migrated. Organizations relying on Fieldy's field-service operations need to evaluate whether Pipedrive's task management is sufficient for their coordination needs.