Migrate from Field Harmony to Nutshell

Direct 1:1 map. Field Harmony person records carry name, email, phone, and address fields that map to Nutshell Person fields directly. Custom properties on the person record migrate as Nutshell custom fields on the Person object. Owner resolution by email match against Nutshell users before migration commits.

Direct 1:1 map. Field Harmony company records map to Nutshell Company records. Company-level custom properties migrate as Nutshell Company custom fields. Multi-location service addresses in Field Harmony require a decision: map primary address as the Company address and store secondary locations in a custom multi-line field, or create separate Company records per service location.

Direct 1:1 map for leads. Field Harmony leads with status 'new', 'contacted', or 'unqualified' migrate to Nutshell Leads with equivalent status labels. Leads converted to customers in Field Harmony map to Nutshell People — the decision point is based on Field Harmony's lead-to-customer lifecycle flag.

Field Harmony work orders have no direct Nutshell equivalent. We map them to Nutshell Deals, placing the work order number in the Deal name field and all work-order attributes (service type, status, scheduled date, technician) as Deal-level custom fields. Pipeline stage in Nutshell is assigned based on a value-map derived from Field Harmony's work-order status pick-list.

Field Harmony work-order statuses (e.g., Scheduled, In Progress, On Hold, Completed, Cancelled) map to Nutshell pipeline stage values via a pick-list value-by-value map. The mapping is defined before migration runs; each status value in Field Harmony routes to a specific Nutshell stage. Probability and forecast category are re-applied based on Nutshell stage settings.

Field Harmony technician assignments on work orders have no native Nutshell equivalent. The technician's name and ID migrate as a custom text field (e.g., Technician_Name__c) on the Deal record. If the technician is also a Nutshell user, we link the Deal to that user by email match on OwnerId — otherwise the custom field holds the value as read-only reference data.

Field Harmony stores multiple service addresses per customer. Nutshell allows one primary address per Company. We map the primary service address to the Company address fields and store all additional service addresses as a custom multi-value text field on the Company record (e.g., Additional_Service_Locations__c) listing each address with a label.

Field Harmony line items (parts used, quantities, costs) on a work order have no standard Nutshell equivalent. We store parts as a custom text area field on the Deal (e.g., Parts_Used__c) formatted as a readable list: 'Part Name | Qty | Unit Price.' For teams with high parts volume, we can create a separate custom object for parts if Nutshell's custom object capability is available on the account plan.

Field Harmony custom properties migrate as Nutshell custom fields on the corresponding object (Person, Company, or as Deal custom fields for work-order properties). Nutshell supports text, number, date, and choice field types. Unsupported field types (e.g., multi-select pick-lists that exceed Nutshell's choice limit) are stored as text fields with a note in the transformation log.

Field Harmony activities attached to work orders map to Nutshell Tasks (for calls and logged emails) and Notes (for free-form text entries). Original timestamps, technician owner, and parent-record linkage are preserved. Signature images captured in Field Harmony's mobile app are downloaded and reattached as Nutshell file attachments on the corresponding Deal.

Files attached to work orders or contacts in Field Harmony are downloaded and re-uploaded to Nutshell's file storage, linked to the corresponding Person, Company, or Deal record. File size limits follow Nutshell's attachment constraints (25MB per file for standard imports).

Field Harmony's dispatch rules, route-optimization triggers, and SLA timers are workflow constructs with no Nutshell equivalent. These are documented in an automation-rebuild specification during the migration engagement. Nutshell's automation tools (email sequences, task rules) can replace some follow-up logic but not field-service scheduling. Teams needing ongoing dispatch functionality must use a dedicated field-service integration alongside Nutshell.