Migrate from Field Nexus to Nutshell

Field Nexus Customer maps directly to Nutshell Person. Name, email, phone, address, and company association all transfer as standard Nutshell Person fields. Field Nexus contacts without a company link land as standalone People. Additional contact details like job title or birthday are preserved where they map to Nutshell Person fields, and any secondary email addresses are stored in custom fields for reference.

When a Field Nexus Customer record has an associated company, that company name, address, and web domain migrate to a Nutshell Company record. One-to-one mapping; Nutshell Company supports custom fields for additional company-level data from Field Nexus. If a customer belongs to multiple companies in Field Nexus, the primary company link is used for mapping; secondary links are noted in a custom field on the Person record for manual reconciliation.

Field Nexus WorkOrder becomes a Nutshell Deal. The work order number becomes the Deal name. Status, description, service address, assigned technician, and service type migrate as custom fields on the Nutshell Deal since Nutshell has no native work order object. Original create and close timestamps are preserved.

Field Nexus work order status values (Scheduled, In Progress, Completed, Cancelled) are mapped to Nutshell Deal stage values via a value-mapping table. Each Field Nexus status value maps to the closest Nutshell pipeline stage, with unmapped values flagged for admin decision before migration.

The Field Nexus technician assigned to a work order is resolved by email match against Nutshell user accounts. Unmatched technicians are flagged for admin review — they can be invited to Nutshell or assigned to a fallback owner before migration commits.

Field Nexus TimeEntry records associated with a work order are merged into custom time-tracking fields on the Nutshell Deal representing that work order. Total hours, billable hours, and date range are aggregated per deal so the Deal record carries a summary of the labor invested.

Field Nexus Invoice records are not native Nutshell objects. Invoice number, amount, status, and date migrate as custom fields on the associated Nutshell Deal. A PDF or CSV export of the invoice is attached to the Deal record for reference.

Field Nexus custom objects (configured on the Infor Nexus platform with primary, embedded, or configuration designs) do not have a 1:1 Nutshell equivalent. We create custom fields on the appropriate Nutshell object (Person, Company, or Lead) and map custom object field values directly into those custom fields.

Field Nexus employee records (technicians, dispatchers, admin staff) resolve by email to Nutshell user accounts. Active Field Nexus employees with Nutshell accounts become Nutshell owners on migrated Deals. Staff without Nutshell accounts are flagged for admin provisioning before migration. If a Field Nexus employee has multiple emails, the primary email is used; mismatches trigger a review flag with the option to assign a fallback owner.

Field Nexus work order service address (street, city, state, zip, country) migrates as a custom address block on the Nutshell Deal. This preserves the job location separate from the customer contact address, which is especially important for multi-site service organizations.

Field Nexus file attachments on work orders (photos, signed forms, service reports) are downloaded and re-uploaded as attachments on the corresponding Nutshell Deal record. File size limits from the Nutshell API apply; files over the limit are split or linked via URL.

Field Nexus notes, logged calls, and customer messages associated with a work order or customer record migrate as Nutshell Activity records or Notes on the corresponding Person or Deal. Original timestamps and author attribution are preserved. If a note contains attachments, those files are downloaded and attached to the corresponding Nutshell record, respecting Nutshell's file size limits by splitting large files or linking via URL.