Migrate from Field Squared to Nutshell

Field Squared WorkOrders map to Nutshell Deals with WorkOrder fields (name, amount, status) translated to Deal attributes. The work-order hierarchy (parent/child WorkOrders) collapses to a single Deal per work order; any sub-work-order relationships are stored as a custom field reference for manual reconciliation in Nutshell.

Field Squared Tasks map 1:1 to Nutshell Activities. Task.Name becomes Activity.subject, Task.Description becomes Activity.notes, and Task.Status maps to a value list (Not Started → Open, In Progress → In Progress, Completed → Completed). Original owner resolved by email match to Nutshell user.

Field Squared Contact records — technicians, subcontractors, and customer contacts stored in the platform — migrate as Nutshell People. All standard name/email/phone fields map directly. Contact type (Technician vs Customer) is preserved as a Nutshell custom field on the People record.

Field Squared's CustomerOrganization (the business receiving service) maps directly to Nutshell Company. Company name, address, and industry fields map to their Nutshell equivalents. Multi-location organizations from Field Squared collapse to one Company record in Nutshell with location details stored in the address custom field.

Field Squared Assets (equipment under service contract) have no direct Nutshell equivalent. We create a custom field on the linked Nutshell Company record (Asset_Tags__c) storing the asset IDs and names as a text reference. Full asset lifecycle data is exported as a JSON report for your Nutshell admin to build a separate asset tracking system if needed.

Field Squared ScheduleEntry records (with ScheduledStart, ScheduledEnd, GPS coordinates) translate to Nutshell Events with original start/end datetimes preserved. GPS/route data from Field Squared has no Nutshell equivalent and is stored as a custom text field (Schedule_Route_Data__c) for reference. Route planning views from Field Squared do not carry over.

Field Squared Documents (attachments on WorkOrders, Tasks, Assets) re-upload to Nutshell Files and attach to the corresponding migrated record. Files over 25MB are flagged for chunked upload. Document metadata (name, upload date, description) is preserved; internal Field Squared document IDs are stored as a custom field for traceability.

Field Squared custom fields on WorkOrders must map to custom fields on Nutshell Deals. Nutshell natively supports custom fields on People, Company, and Lead but not on Deal — we create Deal-level custom fields via Nutshell's API (allowed for Nutshell Enterprise accounts). If your Nutshell plan does not support Deal custom fields, WorkOrder custom fields are stored as text on the linked People record with a prefix.

Task-specific custom fields from Field Squared (created via Custom Fields API with over 30 field types) translate to Nutshell custom fields on the associated People record. Field type mapping: text → string, number → number, date → date, dropdown → picklist. Some Field Squared field types require approximation in Nutshell's simpler custom field model.

Field Squared users (technicians, dispatchers, admins) are matched to Nutshell users by email address. If a Field Squared user has no corresponding Nutshell account, their records are assigned to a fallback Nutshell user specified during migration planning. Owner history on WorkOrders and Tasks preserves the original Field Squared user name as a custom field.

Field Squared workflow configurations and automation rules are not migratable. We export your Field Squared workflow definitions as a JSON specification document that your Nutshell admin can use as a reference when rebuilding sequences and automation rules in Nutshell's sales automation tools.