Migrate from Fieldproxy to Nutshell

Fieldproxy Organizations map directly to Nutshell Companies. Organization name maps to Company name, domain maps to the website field, and address fields (street, city, state, postal_code, country) map to the corresponding Nutshell Company address fields. If an Organization has multiple locations, each location is evaluated for whether it warrants a separate Nutshell Company record based on your specification.

Fieldproxy People map to Nutshell People on a 1:1 basis. The Person's name, email, phone, title, and address fields map directly. Nutshell People are linked to a primary Company via the Company field on the Person record. For Fieldproxy People associated with multiple Organizations, the primary association maps to the Nutshell Company field; secondary associations are captured as notes or a custom field.

Fieldproxy Jobs map to Nutshell Deals. The Job name maps to Deal name, the estimated or final job amount maps to Deal amount, and the assigned technician's email resolves to the Nutshell user as Deal owner. Job status (Scheduled, In Progress, Completed, Invoiced) maps to a custom field on the Deal so the original service lifecycle is preserved. Active jobs map to open Deal stages; invoiced jobs map to Won.

Nutshell has no native equivalent to Fieldproxy's job status lifecycle. We create a custom pick-list field (Job_Status__c) on Nutshell Deals populated with Fieldproxy's exact status values (Scheduled, In Progress, Completed, Invoiced, Cancelled). This preserves the full service lifecycle in Nutshell without altering the standard Deal object behavior.

Fieldproxy Tasks (work order line items or checklist items) migrate as Nutshell Notes attached to the corresponding Deal or Person. Each Note captures the task description, completion status, and timestamp. If a Task has a technician assignment, the Note records the technician name and completion time for audit continuity.

Fieldproxy file attachments on Jobs or People are downloaded and re-uploaded to Nutshell Files, linked to the corresponding Person, Company, or Deal record. File size limits on the destination apply (Nutshell's file handling follows standard web upload limits). We preserve original file names and timestamps to maintain audit continuity.

Fieldproxy technician records map to Nutshell Users by email address match. A technician who is also a sales contact in Fieldproxy becomes both a Nutshell User (if they log in) and a Nutshell Person. Unmatched technicians are flagged before migration — you either invite them to Nutshell or assign their records to a fallback owner.

Fieldproxy Organization custom fields (e.g., service_tier, contract_type, SLA_level) migrate as Nutshell Company custom fields. We create the equivalent field type in Nutshell (text, number, pick-list, date, or checkbox) before data migration so the mapping resolves cleanly. If a custom field uses a pick‑list, we replicate the exact options to ensure data consistency in reports and filters.

Fieldproxy Person custom fields (e.g., certification_expiry, fleet_vehicle_id) migrate as Nutshell Person custom fields. Field types are matched or the closest Nutshell equivalent is used, with notes in the migration plan for your review before the full run. If a field contains date information, we map it to a Nutshell date field to enable time‑based triggers and reporting.

Fieldproxy job line items and parts used do not have a native Nutshell equivalent. We store the parts list as a custom text or JSON field on the Deal for reference, or surface it as a Note attachment listing each line item with quantity and price.

Fieldproxy workflows, dispatch rules, and AI scheduling automations do not migrate. They must be rebuilt in Nutshell using Nutshell's personal email sequences and basic automation triggers, or documented via our workflow export for your Nutshell admin to reference. Our export includes trigger conditions, action steps, and field dependencies to guide the rebuild process.

Fieldproxy integrations with QuickBooks, Stripe, Calendar, WhatsApp, and Gmail are platform-specific connections that must be re-established in Nutshell. Nutshell's marketplace lists 200+ native integrations including QuickBooks, Stripe, and Google Workspace — your admin can reconnect these post-migration. We also provide a connection checklist and configuration notes for each integration to speed up the re‑setup.