Migrate from FieldAware by GPS Insight to Freshsales

FieldAware Jobs are operational work orders; they map to Freshsales Deals as the closest equivalent. Job ID becomes a custom field (Job_ID__c). Job status (Open, In Progress, Completed, Cancelled) maps to Freshsales Deal stage values — defined per pipeline. Priority, type, SLA deadline, and technician name migrate as custom fields on the deal. Line items on the job (parts and labor) map to Freshsales product records linked to the deal.

FieldAware Customers map directly to Freshsales Accounts. Business name becomes Account Name. Primary address maps to the Account address fields. Industry, annual revenue, number of employees, and owner information carry over. Contacts nested under a FieldAware Customer map to Freshsales Contacts linked to the Account.

FieldAware Contacts migrate to Freshsales Contacts. Each contact's first name, last name, email address, phone number, mobile phone, job title, and physical address fields map directly to the corresponding Freshsales Contact fields. When multiple contacts exist under a single FieldAware Customer, each one becomes a separate Freshsales Contact record, automatically linked to the parent Account for proper relationship hierarchy and reporting.

FieldAware Locations represent service sites with multi-level address hierarchies. We map the primary location address to the Account address fields (street, city, state, postal code, country). Secondary locations and address hierarchies beyond the primary are preserved as custom fields (Location_Name__c, Location_Address2__c) on the Account record.

FieldAware's dedicated Asset module (serial number, manufacturer, model, warranty, installation date, parent account link) has no native equivalent in Freshsales. We create a custom object in Freshsales named FieldAware_Asset__c. Each Asset record is linked to the corresponding Account via a lookup field. Manufacturer, model, warranty, and install date migrate as custom fields.

FieldAware Invoices are billing records tied to jobs and line items. We map invoice records to Freshsales Deals — the invoice number and billing status migrate as custom fields on the deal. Line items from the invoice map to Freshsales Product records, with quantity and unit price, linked to the deal.

FieldAware Line Items (parts and labor with part number, description, quantity, unit price) map directly to Freshsales Products. Part number becomes SKU. Description becomes Product Name. Unit price and quantity are preserved. Products link to the parent Deal representing the invoice.

FieldAware custom field declarations (metadata: display name, type, position, default value) are platform-level schema. They do not export via API as reusable definitions. FlitStack captures the declaration details (name, type, entity class) as custom field values in Freshsales. Your Freshsales admin must manually create the corresponding custom field definitions in Settings → Custom Fields after migration.

FieldAware Tasks are child records of Jobs — representing individual steps within a work order. Task name, status, description, and scheduled datetime map directly to Freshsales Tasks. Duration migrates as a custom number field on the task. Parent task-to-job linking is maintained via a custom field (Parent_Job_ID__c) on the task.

FieldAware Users contain both contact details and system role information. We map user contact details (full name, email, phone) to Freshsales Users. Role (Field Technician, Dispatcher, Admin) and territory migrate as custom fields on the User record. Technician-to-job assignments are preserved by linking the technician User ID to the custom Technician field on the migrated Deal.