Migrate from Field service software to Nutshell

Direct 1:1 mapping from FSM customer contacts to Nutshell People records. The Nutshell People object holds name, email address, phone numbers, job title, and full postal address. Source contact records that do not have a company association land as standalone People records without a linked Company reference. Primary company link from the source FSM maps to a Nutshell Company lookup field, establishing the people-to-company relationship in Nutshell's relational structure.

Direct 1:1 mapping from FSM company or account records to Nutshell Company objects. Company name, website domain, industry classification, employee count, and billing address migrate as Nutshell Company standard fields. If the source FSM uses parent-child company hierarchies to represent corporate structures or franchise relationships, the parent link maps directly to Nutshell's parent-company association field, preserving organizational structure within Nutshell.

Work orders transform into Nutshell Deals using FSM work order data. The Deal Name derives from the service type concatenated with the customer name for immediate identification. FSM job status values including Scheduled, In Progress, Completed, and On Hold map to Nutshell Deal stage values — we configure a custom stage set that mirrors your FSM workflow during setup. The original work order number from the source system is stored as a custom field on the Deal for full traceability back to the source record.

Unconverted leads residing in the FSM system map directly to Nutshell Lead records with a 1:1 relationship. Source lead status values including New, Contacted, Qualified, and Converted map to Nutshell Lead status pick-list values configured during setup. Leads that have an associated open work order in the FSM route to both a Nutshell Lead record and a corresponding Deal record simultaneously, ensuring the service opportunity and sales prospect remain synchronized across both record types.

Equipment records from the FSM asset register map to custom fields on the linked Nutshell Company record, including asset_tag, serial_number, install_date, and warranty_expiry fields. For FSM installations using a comprehensive asset register with full maintenance history, multiple location records, and depreciation tracking, migration to a Nutshell Enterprise custom object is required. We identify which approach fits your data during the scoping phase based on asset register complexity and your Nutshell subscription tier.

FSM technicians who are also customer contacts or sales leads map to Nutshell People records with a technician_role custom field populated for identification. Technicians who require system access to view and manage their assigned work orders become Nutshell Users matched by email address during the migration. Any technician records that do not resolve to a matching Nutshell User or People record are flagged in the pre-migration report for manual user creation or cleanup before the migration run executes.

Completed service visits from the FSM migrate as Nutshell Activity records — service type, technician name, and resolution summary populate the Activity description field for reference. Original timestamps including visit date and time plus duration data are preserved on the migrated Activity record. If the FSM logs multiple line-item tasks per individual visit such as inspection steps, parts installed, and quality checks, each task becomes a separate Activity linked to the same parent Deal record to maintain granular service history.

Parts and materials used on a work order migrate using one of two approaches depending on your reporting needs. Structured custom fields on the Deal including part_name, part_number, quantity, and cost capture line-item detail in a queryable format. Alternatively, a Note attachment with embedded CSV data preserves full parts detail without occupying multiple custom fields. Nutshell has no native line-item object or product table on Deals — we agree on the format during scoping based on your post-migration reporting requirements.

Nutshell provides no native invoicing, billing, or payment object for financial transaction recording. Invoices from the FSM migrate as Notes attached to the corresponding Deal, preserving invoice number, date, and line-item summary. Alternatively, a custom currency field captures total billed amount and payment status for quick reference on the Deal. Given that Nutshell is a CRM rather than an accounting system, we recommend managing all accounting and billing data in a dedicated accounting platform post-migration to maintain financial accuracy and compliance.

Service-type tags, customer segment labels, equipment categories, and priority classifications from the FSM migrate as Nutshell Tags that attach to People, Companies, and Deals for filtering, segmentation, and reporting purposes. FSM-specific taxonomy such as trade_type codes, priority_level ratings, and service_category labels that require structured values rather than simple tag associations map to Nutshell custom fields configured during schema setup if tags alone prove insufficient for your reporting needs.

FSM appointment windows, scheduled time slots, technician assignments, and dispatch data lack a direct equivalent in Nutshell's activity model. We preserve this operational data as Nutshell Activity records with scheduling metadata stored in custom fields including scheduled_date, appointment_window_start, appointment_window_end, assigned_technician_email, and visit_status. Routing optimization data, geo-coordinates for dispatch mapping, and multi-technician scheduling dependencies do not migrate as they require specialized FSM scheduling algorithms that Nutshell cannot replicate.

File attachments associated with work orders in the FSM including photographs of completed work, signed service forms, inspection reports, and equipment diagrams migrate as Nutshell Notes with file attachments re-uploaded to Nutshell's storage infrastructure. Nutshell's attachment size limits apply with a maximum of 25MB per individual file. For FSM records containing multiple attachments per work order, each file becomes a separate Note attachment linked to the parent Deal, preserving the original attachment structure and naming conventions where available from the source system.