Migrate from FieldFX to Nutshell

Direct field mapping from Salesforce Account to Nutshell Company. All standard Account fields including Name, Industry, Website, AnnualRevenue, and NumberOfEmployees migrate to equivalent Nutshell Company fields. The ParentId relationship is preserved using Nutshell's parent-company reference where available; if the parent-company relationship is unavailable in your Nutshell plan, the hierarchy is flattened and parent references are stored as a custom field on the child Company record.

Direct field mapping from Salesforce Contact to Nutshell Person. Standard Contact fields including FirstName, LastName, Email, Phone, and Title map to their Nutshell Person equivalents. The critical mapping step is resolving the AccountId lookup relationship — this foreign key resolves to the Nutshell Company record that was created during the Account mapping phase, establishing the person-to-company relationship in Nutshell upon which activity linking depends.

FieldFX Ticket has no Nutshell equivalent. The Ticket record migrates as a Nutshell Activity (Task or Event depending on type__c) with ticket ID, status, priority, and assigned technician preserved as Nutshell custom fields on the related Person record. TicketItem records are appended as a custom multi-value field.

WorkOrder__c migrates as a Nutshell Activity with the WorkOrder ID stored in a custom reference field. WorkOrderLineItem records are flattened and stored as a custom field on the activity — original line item descriptions, quantities, and costs are preserved in structured text.

Asset records link to Account (service-location account) and Product2 (equipment catalog). The asset name, serial number, and install date are stored as custom fields on the Nutshell Company record representing the asset's location. Full asset-to-product relationship is preserved in a structured custom field.

Each WorkOrderLineItem__c record is parsed and its fields (description, quantity, unit cost, line total) are appended to a structured custom field on the parent WorkOrder Activity in Nutshell. Multiple line items per WorkOrder result in multiple entries within the same custom field.

TicketItem__c records hold parts and labor lines on a Ticket. We split each item into a structured text entry appended to a Nutshell custom field on the Ticket Activity. Source ticketitem ID and source work order ID are retained for audit traceability.

Salesforce User records resolve to Nutshell Persons by email match. Unmatched users (e.g., deactivated Salesforce users) are flagged before migration and assigned to a fallback Nutshell user designated by your admin. User ID is preserved in Source_System_Owner_ID__c on the Person record.

CPQ quote records carry pricing schedules, approval status, and line-item pricing that cannot be natively represented in Nutshell. Quote summary, total amount, status, and primary contact are stored as custom fields on the Nutshell Deal. Detailed pricing line items are exported as a structured reference document.

FieldFX Status Workflows control Ticket and WorkOrder state transitions with conditional logic. Nutshell has no equivalent workflow builder for ticket-equivalent objects. We export the workflow definitions as a reference JSON file for manual rebuild in Nutshell using Sequences and custom fields.

DataGuide forms capture structured inspection and compliance data on WorkOrders. Nutshell has no forms or structured data-capture equivalent. Form response data is exported as structured records linked to the related WorkOrder Activity in Nutshell, preserving the field names and values.

FieldFX ticket and work order attachments stored as Salesforce Files are downloaded in their original format and re-hosted as Nutshell Notes attached to the corresponding Activity record. File metadata including the original file name and ContentVersion description are preserved in the Note body. Nutshell enforces file size limits for attachments; any files exceeding these limits are flagged during migration review and marked for manual download and re-upload by your administrator after cutover.