Migrate from Field Service Trakker to Nutshell

Work orders map directly to Nutshell Deals. Job type, priority, status, and description migrate as custom fields on the Deal. Original work order number is stored as Source_WorkOrder_ID__c for traceability. Close date maps to Nutshell deal close date if the job has a completion date.

Field Service Trakker customer records become Nutshell Companies. Business name, primary address, phone, and industry classification map directly. FST allows multiple service locations per customer — the primary location becomes the Company address; secondary locations migrate as custom address fields.

When a single customer in Field Service Trakker has multiple service locations across different sites or addresses, these locations are consolidated into one Nutshell Company record rather than creating separate companies. The primary or most recently modified FST service location becomes the standard Company address. All additional service locations associated with that customer are stored as custom multi-value fields on the same Company record. This approach preserves the complete address history and location details for each customer while preventing the creation of duplicate company records in Nutshell, maintaining data integrity and clean reporting.

Technician records map to Nutshell People. Owner assignment on migrated Deals is resolved by matching technician email to a Nutshell user account. Unmatched technicians are flagged before migration; your team either creates Nutshell accounts for them or assigns their records to a fallback owner.

Nutshell has no native asset or equipment object. Equipment records migrate as a Nutshell custom object named FieldServiceAsset with custom fields for serial number, model, warranty expiry, and linked service location. The custom object must be created in Nutshell before migration runs.

FST inventory line items linked to a work order are aggregated as custom fields on the corresponding Nutshell Deal — part number, quantity used, and unit price stored as text or number fields. Nutshell has no native inventory module, so parts consumption history is preserved at the deal level rather than as a separate object.

FST service visit records and activity logs migrate as Nutshell Activities attached to the corresponding Deal. Original visit date, technician, and service type are preserved. Activity type is set to 'Service Visit' to distinguish from standard sales call or email activities.

Work order notes migrate as Nutshell Notes attached to the Deal record. File attachments are re-uploaded to Nutshell's file storage and linked to the deal. File size limits apply — files exceeding Nutshell's 25MB per-attachment limit are flagged for manual retrieval.

FST invoices linked to work orders do not map to a native Nutshell billing object. Invoice number, total amount, and payment status are stored as custom fields on the corresponding Deal record. Nutshell lacks a billing or accounting module — finance teams use separate accounting tools integrated via API.

All custom properties defined in Field Service Trakker — on work orders, equipment, or customers — require corresponding custom fields in Nutshell. These must be created in Nutshell before migration begins. FlitStack delivers a custom-field creation plan listing each property name, data type, and target Nutshell field so your admin can pre-configure the schema.

Field Service Trakker dispatch rules — technician-to-region assignment, skill-based routing, time-window constraints — have no Nutshell equivalent. This logic must be rebuilt manually in Nutshell's workflow tools or assessed against third-party scheduling integrations. FlitStack exports the rule definitions as a rebuild reference.