Migrate from FieldAware by GPS Insight to Nutshell

FieldAware Customer maps directly to Nutshell Company. The customer name becomes the Company name, the domain becomes the Website field, and industry or value classifications map via Nutshell's industry pick-list. For multi-location customers with several service sites, a single Company record is created and the primary location's address populates the main Company address fields. The customer record's unique identifier is preserved for audit traceability.

FieldAware Contact maps directly to Nutshell Person. First name, last name, email, phone, mobile phone, title, and role all map to Nutshell Person fields. Each Contact's owner (technician or dispatcher) maps to the Nutshell user by email match if the email corresponds to a Nutshell user account.

FieldAware Locations associated with a Customer become address data on the corresponding Nutshell Company record. If a Customer has multiple Locations, the primary location populates the Company address fields and subsequent locations are stored as custom text fields (Location_2_Address__c, Location_3_Address__c, etc.) since Nutshell supports a single primary address per Company.

FieldAware Jobs and Work Orders map to Nutshell Deals. Job name becomes the Deal name, the scheduled date becomes the Nutshell expected close date (repurposed as the job date), job status maps via value mapping to Nutshell's deal status (Open = Won if completed, Closed Lost if cancelled), and job total maps to Deal value.

FieldAware parent-child job structures (a Job with child Work Orders) must be collapsed into a single Nutshell Deal because Nutshell has no native job hierarchy. Work Order line items are flattened into Nutshell custom fields (Work_Order_1_Service__c, Work_Order_2_Service__c, etc.) or preserved as a JSON block in a custom long-text field. FlitStack surfaces this plan before migration so your team decides whether to merge or keep only the parent Job.

Nutshell has no native Asset object. Equipment tracked in FieldAware (serial numbers, manufacturer, model, warranty dates, service tier) migrates to Nutshell as custom fields on the Company record for customer-owned equipment, and on the Deal record for equipment associated with a specific job. A custom Asset__c text field stores the original FieldAware Asset ID for traceability.

FieldAware custom fields declared on Jobs, Customers, Contacts, Locations, Assets, and Items require individual Nutshell custom field creation. FlitStack audits every active custom field declaration, maps the type (Text → Text, Number → Number, CheckBox → Boolean, Dropdown → Choice, Date → Date), and creates a setup checklist for your Nutshell admin to apply before migration data loads.

FieldAware users and technicians are matched to Nutshell users by email address. Unmatched FieldAware users are flagged — their records are assigned to a fallback Nutshell owner (your admin specifies the fallback). The original FieldAware user role is preserved as a custom text field (Source_User_Role__c) for reference when rebuilding permissions.

FieldAware Quotes attached to a Job become Nutshell Deal records with the quoted amount stored in the Deal value field. Line-item details are preserved in custom text fields (Quote_Line_Items__c) since Nutshell does not have a native quote line-items model. The quote status (Sent, Accepted, Declined) maps to custom choice fields.

FieldAware Invoices do not have a native Nutshell equivalent. Nutshell supports basic billing integration with QuickBooks and Stripe but does not maintain a full invoice record within the CRM. Invoices are preserved as custom fields on the related Deal (Invoice_Number__c, Invoice_Date__c, Invoice_Amount__c) or exported as a separate file. Accounting integration is handled post-migration.