Migrate from FieldPro to Pipedrive

FieldPro locations map to Pipedrive Organizations. The location name becomes the organization name, full address maps to Pipedrive address fields, and GPS latitude/longitude are preserved as a custom field on the organization record for reference. Location status (active/inactive) maps to Pipedrive visibility group assignment.

FieldPro location type (retailer, distributor, outlet) has no direct Pipedrive equivalent. We create a Pipedrive custom field of type picklist on Organizations and populate it with the original location type values. The picklist options are created in Pipedrive before migration runs.

FieldPro contacts at a location map to Pipedrive People. The contact name, email address, phone number, and job title map directly to Pipedrive person fields. Each Person is linked to its parent Organization (the FieldPro location) via the org_id field in Pipedrive.

FieldPro contact role (store manager, buyer, technician) has no Pipedrive equivalent. We create a Person-level custom field of type varchar to store the original contact role. This field is populated during migration and can be used for segmentation in Pipedrive.

Each FieldPro visit becomes a Pipedrive Activity record of type meeting. The visit start time maps to the Activity start timestamp, visit duration in minutes is stored as a custom field, and the agent who conducted the visit is resolved by email match to a Pipedrive user and assigned as the Activity owner.

FieldPro visits that include an order generate a Pipedrive Deal record. The deal name uses the format 'Visit - [Location Name] - [Date]'. The order value from FieldPro maps to the deal's monetary value in Pipedrive. The Activity and Deal are linked via Pipedrive's activity reference field so teams can see the original visit from within the deal record.

FieldPro orders map directly to Pipedrive Deals. The order number becomes the deal name prefix, order value becomes the deal value, and order status (pending, confirmed, fulfilled) maps to Pipedrive deal stage. The associated FieldPro location maps to the Pipedrive Organization linked to the Deal.

FieldPro order type (new, reorder, sample) has no Pipedrive standard field. We create a deal-level custom field of type varchar to store the original order type. FieldPro order reference numbers are stored as a second deal custom field for traceability.

FieldPro field agents are resolved by email match against Pipedrive users. Matched agents are assigned as owners on their respective Activity and Deal records in Pipedrive. Agents without a matching Pipedrive user are flagged before migration, and a fallback assignment is applied per migration plan.

FieldPro supports labels on locations, visits, and orders. Pipedrive has a separate Labels feature that exists per entity type independently. We preserve the label names as a custom field on each entity for reference. Full label recreation in Pipedrive's label system must be done manually after migration.

FieldPro custom properties defined on the Location object are created as Pipedrive Organization custom fields before migration. Field type mapping follows: text properties become varchar, numeric properties become number, date properties become date, and picklist properties become Pipedrive picklist fields.

FieldPro custom properties recorded on visits are created as Pipedrive Activity custom fields. This preserves any structured data your team captured during visits — such as stock levels, competitor presence, or compliance check results — as searchable fields in Pipedrive.