Migrate your FieldAware by GPS Insight data

Customers in FieldAware link to one or more Locations and Contacts. We migrate the customer record including service address, billing details, and linked hierarchy intact. Customer IDs are system-assigned and must be mapped to destination identifiers during import.

Locations represent service addresses under a Customer. FieldAware supports multiple locations per customer. We preserve the parent-to-child relationship and any location-specific custom fields during migration.

Contacts are linked to Customers and Locations. Each contact can have an assigned role. We migrate contacts with name, email, phone, and role, preserving their association to the parent customer and location.

Jobs are the core operational record in FieldAware, containing scheduling, asset assignments, line items, and job history. We export the full job lifecycle including status transitions, assigned technicians, and timestamps. Custom fields on Jobs require declaration recreation at the destination.

Invoices are generated from completed Jobs and include line items, tax codes, and payment status. We migrate invoice records including amounts, due dates, and whether payment has been received. Voided or refunded invoices are flagged separately.

Assets represent equipment at a Location and are linked to Jobs for tracking maintenance history. Asset serial numbers, model numbers, and custom fields migrate, but asset-to-job linkage requires reconstruction at the destination if the target system uses a different linking schema.

Items represent parts and services used on Jobs, with name, part number, description, and unit price. We export the item catalog and preserve pricing, though pricebook customization from the Premium tier must be mapped if the destination uses a different pricing structure.

Quotes in FieldAware are pre-job estimates that can be converted to Jobs or Invoices. We migrate quote records with line items, totals, and status. Converted quotes retain a reference to their resulting Job ID where present.

Tasks in FieldAware are checklist items or sub-tasks within a Job. We migrate Tasks with their completion status and link them back to their parent Job. Custom fields on Tasks are supported but require destination declaration.

Custom fields are declared per entity type (Job, Invoice, Asset, Customer, Contact, Location, Task, Item) and support Text, Number, CheckBox, Dropdown, Date, and Time types. Format type is immutable after creation. We export declarations as metadata and map values to destination custom fields, handling Dropdown option lists carefully to avoid value mismatches.

User accounts include role-based permissions tied to the plan tier. Starter caps at 2 users, Professional at 10, Premium is unlimited. We audit all active user accounts against the current plan cap and flag any over-limit users before migration scoping.

FieldAware maintains a chronological job history log per asset or customer. We export historical records including timestamps, technician assignments, and resolution notes. Large histories are chunked into manageable export batches to avoid API timeouts.