Migrate from FieldAware by GPS Insight to Pipedrive

FieldAware Customer maps to Pipedrive Organization. The primary business name, billing address, and customer-level custom fields migrate as Organization custom fields. Multi-location customers are handled by creating one Organization with address fields from the primary location; additional locations surface as Organization address lines or custom address fields.

FieldAware Contact maps directly to Pipedrive Person. Name, email, phone, mobile, job title, and contact-level custom fields carry over. The Contact's linked Customer becomes the Person's parent Organization via OrganizationId lookup. If a Contact has no Customer link, it creates an Organization placeholder in Pipedrive.

FieldAware Job is the core FSM entity with status, assigned technician, line items, and timestamps. Migrates as a Pipedrive Deal with the Job name as Deal title, Job status mapped to Pipedrive stage, total billed amount as Deal value, and the linked Customer/Contact as Organization/Person. Job custom fields (e.g., service type, priority) become Deal custom fields. Original Job create date preserved as a custom datetime field since Pipedrive's CreatedDate reflects migration time.

FieldAware Asset records (equipment serial numbers, maintenance schedules, linked locations) split across Pipedrive. Equipment that represents billable service items creates Pipedrive Products with name, description, and unit price. Equipment that represents customer-owned infrastructure maps to custom fields on the Organization (e.g., Asset_Serial_Number__c, Maintenance_Schedule__c). The split decision is made per Asset type field in FieldAware.

FieldAware Location carries service-site address, geocoordinates, and linked Assets. Migrates as Organization address fields (street, city, state, zip, country) plus custom fields for latitude/longitude. Multiple Locations under one Customer create multiple Organization records with name differentiating each site, or use Organization address labels. Location-level custom fields (e.g., site access codes) become Organization custom fields.

FieldAware Task (technician action linked to Job) maps to Pipedrive Activity with Type='Task'. Subject carries the Task description, due date maps to Activity due date, and the linked Job/Contact/Organization relationships are preserved via Pipedrive's activity-linked entity model. Completed status migrates as Activity marked done with completion timestamp.

FieldAware Item (parts, labor rates, service line items) maps to Pipedrive Product with name, code (mapped from Item ID), description, and unit price. Products can be linked to Deals as line items in Pipedrive, preserving the Job's billable line-item structure at a Deal level.

FieldAware Job custom fields (service type, priority flag, technician skill requirement) create Pipedrive Deal custom fields. FieldAware custom field types (Text, Number, CheckBox, Dropdown, Date, Time) map to equivalent Pipedrive field types. Pipedrive generates a 40-character hash key per custom field; FlitStack records the mapping for traceability and delta-run de-duplication.

FieldAware custom fields declared on Customer, Contact, Asset, Location, and Item entities each create corresponding custom fields in Pipedrive on Organization, Person, or Product. The per-entity custom field declaration model in FieldAware requires creating individual custom fields per Pipedrive entity rather than inheriting across entities.

FieldAware users and technicians resolve by email match against Pipedrive users. Unmatched technicians are flagged before migration; your team either creates Pipedrive user accounts first or assigns their records to a fallback Pipedrive user. Job assignments in FieldAware carry as Deal owner or as a custom field if no Pipedrive user match exists.

FieldAware Invoice is a billing construct tied to Jobs with line items, payment status, and customer billing. Pipedrive has no native invoicing entity. We preserve Invoice data (amount, status, linked Job, line items) as custom fields on the related Deal for reference, but the financial model must be rebuilt in Pipedrive's billing tools or a connected accounting integration.

FieldAware Job status values (Scheduled, In Progress, On Hold, Completed, Cancelled) map value-by-value to Pipedrive Deal stage values. Stage probability and forecast category re-applied from Pipedrive's stage configuration. If your Pipedrive account uses multiple pipelines, each FieldAware status set maps to a separate pipeline's stage values.