Migrate from FieldAware by GPS Insight to Twenty CRM

FieldAware Customers map directly to Twenty Companies. A Customer in FieldAware is a business entity (HVAC company, property manager) — Twenty's Companies object stores organization name, industry, domain, and size. FieldAware's Customer-level custom fields (e.g., SLA tier, service agreement type) migrate as custom fields on the Twenty Company record. If a Customer has multiple service Locations, each Location becomes a separate Company record in Twenty linked by a custom parent-company relationship.

FieldAware Locations are service-site addresses attached to a Customer (e.g., a restaurant chain with 12 branch locations). In Twenty, each Location becomes a Company record with a custom Location_Type__c field set to 'Branch' and a Parent_Company__c relation pointing to the primary Customer Company. Address fields (street, city, state, zip, country) map to the address compound field on the Twenty Company. This preserves the full location hierarchy for service dispatch history.

FieldAware Contacts (individuals linked to a Customer or Location) map directly to Twenty People. Standard fields — first name, last name, email, phone, job title — migrate as-is. The Contact-to-Customer relationship becomes a Company relation on the Twenty Person record. Role labels on FieldAware Contacts (e.g., Site Manager, Operations Director) are preserved as a custom Role__c field on Person.

FieldAware Jobs are work orders — the core entity of the FSM model. They carry status (Scheduled, In Progress, Completed, Cancelled), assigned technician, scheduled date/time, location, line items (parts and labour), and custom fields per job. In Twenty, Jobs map to two targets: (1) an Opportunity record capturing the commercial value of the job (amount, stage as job status, close date), and (2) a custom JobHistory__c object storing full job detail — technician assigned, actual start/end times, parts used, signature captured, and custom checklist responses.

FieldAware job statuses (Scheduled, En Route, On Site, Completed, Invoiced, Cancelled) map to Twenty Opportunity stage values. Each status becomes a named stage in Twenty's pipeline. Probability and forecast category are re-applied based on the mapping — Completed maps to Closed Won, Cancelled maps to Closed Lost, and active statuses distribute across the pipeline stages. Job stage-change timestamps are preserved in a custom Stage_Changed_At__c datetime field on the Opportunity.

FieldAware Assets are equipment records tracked at customer locations (HVAC units, elevators, refrigeration systems). These have serial numbers, make/model, install date, warranty status, and service history. Twenty has no native Asset object, so FlitStack creates an Asset__c custom object with fields for name, serial number, make, model, install date, warranty expiry, and a relation to the Company record representing the asset's location. Asset-to-Job associations (which jobs were performed on which assets) migrate as a custom Asset_Job__c junction object.

FieldAware Invoices carry line items, tax, payment status, and a link to the originating Job. Twenty has no native invoicing module. FlitStack creates an Invoice__c custom object with fields for invoice number, date, amount, tax amount, status (Paid, Unpaid, Overdue, Void), payment date, and a relation to the Opportunity representing the Job. Invoice line items migrate as a custom InvoiceLineItem__c object with description, quantity, unit price, and total — linked to Invoice__c.

FieldAware Items are parts and services in the pricebook — used on Job line items and Quotes. These map to a ServiceItem__c custom object in Twenty with fields for name, part number, description, unit price, cost, and a type pick-list (Part, Labour, Miscellaneous). Items linked to invoices carry that relationship forward via the Invoice__c junction.

FieldAware Tasks (internal to-do items on jobs, often assigned to technicians) map directly to Twenty Tasks. Subject, description, due date, assignee, and completion status carry over. Tasks linked to a Job Opportunity in Twenty are connected via the Opportunity relation on the Task record. Completed task timestamps are preserved from the FieldAware record.

FieldAware Notes (free-text annotations on Jobs, Customers, or Assets) migrate to Twenty Notes. The body, author, and creation timestamp are preserved. Notes attached to a Job Opportunity carry the Opportunity as their parent record. If a note references a specific asset or location, the custom object relation is established via a lookup field on the Note.

FieldAware Users (dispatchers, technicians, admins) map to Twenty Workspace Members. Resolution happens by email match — each FieldAware user email is matched against Twenty workspace member emails. Unmatched users are flagged before migration. Active status and role (technician vs. admin) are preserved as a Role__c text field on the WorkspaceMember record. Note that FieldAware's permission model (Roles & Rights) does not migrate — Twenty's permission groups are set up separately.

FieldAware supports custom fields on Jobs, Customers, Contacts, Locations, Assets, Invoices, Items, and Tasks with types: Text, Number, CheckBox, Dropdown, Date, Time, and for Job/Asset — syncable-to-mobile flags. Each custom field declaration migrates as a custom field in Twenty on the corresponding object. Dropdown custom fields in FieldAware create pick-list custom fields in Twenty with the same option values. CheckBox maps to Boolean; Date and Time map to Date and DateTime respectively in Twenty.

FieldAware file attachments on Jobs (photos, PDFs, signatures) re-upload to Twenty's file storage. File size limits apply — FieldAware documents within standard limits migrate fully. Signature images captured on the mobile app are stored as image files attached to the JobHistory__c custom object record. If files are inline in notes (e.g., embedded images), they are extracted, rehosted, and the note body is updated with the new URL reference.

FieldAware dispatch and scheduling workflows — auto-assignment rules, geo-routing, technician skill matching, and SLA alerting — are platform-specific automation with no native equivalent in Twenty CRM. These are documented in an exportable workflow definition for rebuild in Twenty's workflow builder or an external automation tool. This is a manual-rebuild item disclosed upfront.