Migrate from FieldAware by GPS Insight to HubSpot

FieldAware Customers (business entities with name, address, billing info) map directly to HubSpot Companies. We pull the customer name, primary location address, phone, and email and write them to the corresponding HubSpot Company properties. Parent-child customer hierarchies map to HubSpot's parent company association.

Each FieldAware Customer Contact — the person linked to a customer — maps to a HubSpot Contact. We preserve the contact's name, email, phone, role, and the customer link. Multiple contacts per customer collapse to individual HubSpot Contacts with the same Company association.

FieldAware Locations store site-level addresses and service details. If a customer has one primary location, the address migrates to the HubSpot Company record. Multi-location customers with distinct service sites get a Location Custom Object in HubSpot (Enterprise) so each site is queryable independently with its own address, asset list, and work-order history.

FieldAware Work Orders carry job status, technician assignment, scheduled time, location link, and notes. We map status to HubSpot Ticket lifecycle (New → Open → Closed) and preserve job details as custom properties. For customers needing full job history with line items and time tracking, we create a Job Custom Object in HubSpot (Enterprise) and link it to the associated Company and Contact.

FieldAware Assets (equipment tracked at locations with serial numbers, warranty dates, and maintenance history) have no HubSpot native equivalent. We create a HubSpot Asset Custom Object with fields for asset name, serial number, make/model, warranty expiration, last service date, and a lookup to the associated Company and Location. Service history from past Work Orders attaches as activity entries.

FieldAware Invoices contain line items, taxes, payment status, and amounts tied to work orders. HubSpot has no native invoicing object. We preserve invoice metadata — invoice number, total amount, status, date — as custom properties on the related Company or Job Ticket record. The financial data lives for reference; actual invoicing must be handled by an ERP integration post-migration.

FieldAware Items (parts, materials, service codes with descriptions and unit prices) map to HubSpot Products. We write item name, part number, description, and unit cost. Inventory quantities and warehouse locations are FieldAware-specific and stored as custom properties since HubSpot Products do not track multi-warehouse stock levels natively.

FieldAware Quotes (proposed work with line items and pricing) map to HubSpot Deals when the migration use case includes opportunity management. Quote line items attach as Deal Line Items in HubSpot. If no sales pipeline exists, Quotes migrate as closed-lost Deals or stored as a custom Quote Custom Object for reference.

FieldAware Tasks (standalone to-do items not tied to a work order) map to HubSpot Tasks. We write task subject, due date, assigned user (resolved by email match to HubSpot users), and completion status. Tasks with a Work Order association link to the corresponding Ticket or Job Custom Object record.

FieldAware Users and Technicians are staff records with email addresses, roles, and skills. We match FieldAware users to HubSpot Users by email. Unmatched users are flagged before migration — your team decides whether to invite them to HubSpot or assign their records to a fallback HubSpot user. Skills and certifications from FieldAware store as custom properties on the HubSpot User record.

FieldAware custom fields are declared per entity type with display names, types (Text, Number, Checkbox, Dropdown, Date, Time), and optional default values. For Job and Asset custom fields with mobile-sync flags, we create HubSpot custom properties with the same type and store the sync flag as a text property for admin reference since HubSpot has no per-property mobile-display toggle.

FieldAware's customer-facing portal lets clients view job status, approve quotes, and sign off on work. HubSpot has no built-in customer portal — this must be rebuilt using HubSpot's member portal features (Enterprise) or a third-party self-service integration. We document the existing portal structure as a rebuild reference.