Migrate from Connect Field Service to Nutshell

Work Orders have no direct Nutshell equivalent. We extract the customer contact from WorkOrder.AccountId (mapped to Nutshell Person) and the service narrative becomes a Nutshell Activity of type 'note' with the Work Order number stored in a custom field (Work_Order_Number__c) for traceability. Work Order priority, status, and service type are preserved as custom fields on the Person record.

Each Work Order Line Item represents a task or parts line. Multiple line items from a single Work Order merge into one Nutshell Activity entry, with the item descriptions concatenated or expanded into separate Activity rows at your preference. Service type codes, quantity, and product references migrate as custom text fields on the associated Person.

Service Appointments record scheduled visits with start/end times, assigned resources, and status. In Nutshell, each appointment becomes an Activity of type 'meeting' with the original scheduled start and end preserved in custom datetime fields (Scheduled_Start__c, Scheduled_End__c). Appointment status (Scheduled, In Progress, Completed, Cancelled) migrates as a custom pick-list (Appointment_Status__c) on the Person.

Connect Field Service Accounts that represent customer locations or service sites map 1:1 to Nutshell Companies. The Account's shipping address, site name, and primary contact link to the Company record. Multi-site accounts with child locations preserve the parent-child hierarchy using Nutshell's manual parent-reference custom field since Nutshell has no native account hierarchy.

Salesforce Contacts who are internal technicians or dispatchers migrate to Nutshell People. Email, phone, title, and address fields map directly. The Contact's role in Connect Field Service (technician vs. dispatcher) is preserved in a custom pick-list field (FSL_Role__c) on the Person record since Nutshell has no native role-equivalent for internal staff.

Customer-facing Contacts on Work Orders map to Nutshell People with direct field mapping for name, email, phone, and title. If a Contact has multiple associated Accounts (common in field service for multi-site customers), we migrate one primary Account link and surface secondary site associations as custom text fields listing additional Company IDs.

Salesforce Leads without existing Work Orders or Service Appointments map directly to Nutshell Leads. Lead status, source, and custom fields migrate as-is where field types match. Connect Field Service-specific lead scoring models (if any) require custom field creation in Nutshell.

Assets represent installed or maintained equipment at customer sites. We link each Asset to the associated Nutshell Company (site location) and store asset metadata (product name, serial number, install date, warranty end date) as custom fields on the Company's Person record for the primary contact. Asset Relationship hierarchies (replacement or upgrade chains) are not natively supported in Nutshell — we surface them as a custom text block listing related Asset IDs.

Entitlements capture service‑level agreements such as warranties, SLA tiers, and coverage windows. Because Nutshell lacks a native entitlement object, we preserve this information by creating custom fields on the related Person record: Entitlement_Name__c for the agreement name, Service_Level__c for the tier, Coverage_Start__c and Coverage_End__c for the dates, and a pick‑list field Entitlement_Status__c to indicate whether the entitlement is active or expired.

Field service Skills (HVAC certified, electrical license, manufacturer-specific training) have no Nutshell equivalent. We migrate technician skill tags as a custom multi-select field (Technician_Skills__c) on the Person record so the skill inventory is preserved even if the scheduling use case does not transfer.

Products that represent service offerings or parts used in Work Orders map to a Nutshell Deal capturing the product context. Unit price and product code are stored as custom fields on the Deal. For parts-only migrations, we optionally create a simple Nutshell Product record linked to the Deal.

Connect Field Service generates Task records for technician check-ins, parts usage, and field updates. These map directly to Nutshell Activities of type 'task' with subject, description, original created date, and owner preserved. Completed status and task type (parts, check-in, cleanup) migrate as custom fields on the Activity.

Notes attached to Work Orders, Service Appointments, or Assets migrate as Nutshell Activities of type 'note' with the full note body preserved. File attachments (photos of completed work, signed service reports) re-upload to Nutshell Files and are linked to the corresponding Person or Activity record.

Connect Field Service managed-package objects — Scheduling Policy, FSL Operation, Optimization Data, Gantt Filter, Map Polygon — have no Nutshell equivalent. These represent destination-platform automation and spatial data that cannot be migrated to a non-field-service CRM. We export these definitions as a JSON reference file for manual documentation but they do not appear as Nutshell records.