Migrate from FieldPro to Nutshell

FieldPro field workers map to Nutshell Users as the owner of records. Email-based matching is used to resolve each FieldPro user to the corresponding Nutshell user account. Records owned by FieldPro workers who have no Nutshell account are assigned to a fallback owner flagged before migration.

FieldPro customer records map directly to Nutshell People. A FieldPro customer may have one or more associated contacts; each becomes a separate Nutshell Person record with a link to the parent Company in Nutshell. If a FieldPro customer record contains custom properties, those values transfer to corresponding Nutshell custom fields on the Person record after pre-migration field creation.

FieldPro company or account records map to Nutshell Companies. Company addresses, industry classification, and revenue estimates translate to Nutshell Company fields. If FieldPro uses parent-child hierarchies, the top-level company becomes the Nutshell Company and child locations are created as separate Nutshell Companies linked by a custom Parent_Company__c field.

FieldPro leads or prospects that are not yet converted to customers map to Nutshell Leads. Lead status values in FieldPro are mapped to Nutshell Lead status pick-list values through a value-mapping table created during the mapping phase. This mapping ensures that lead qualification stages and source attributions translate correctly into Nutshell's lead management workflow.

FieldPro deals and work orders map to Nutshell Deals, but the semantics differ. FieldPro work-order status (e.g., Assigned, In Progress, Completed) maps to Nutshell Deal stage pick-list values, with Completed mapping to Won and active statuses mapping to pipeline stages. Deal value translates to Nutshell Deal monetary value. FieldPro work-order ID is preserved as Source_Work_Order_ID__c on the Nutshell Deal.

FieldPro field visit logs, check-ins, and completed tasks map to Nutshell Tasks. The task subject uses FieldPro's activity type (e.g., 'Site Visit', 'Delivery Completed'). Original timestamps from FieldPro are preserved in Nutshell Task's created date and completion date fields. Owner is set to the FieldPro field worker matched to a Nutshell User by email.

FieldPro route and route-assignment records have no direct Nutshell equivalent. Nutshell does not support route planning, geofencing, or field-employee scheduling. Route names and assignments are preserved as Nutshell Task records with custom fields (Route_Name__c, Route_Date__c) for reference, but the operational scheduling logic must be rebuilt in a dedicated field-service or routing tool post-migration.

FieldPro attendance and check-in records (clock-in, clock-out, GPS location at check-in) have no Nutshell equivalent. These records are not migrated. If attendance history is critical for compliance, it should be exported from FieldPro as a separate CSV report and stored outside Nutshell.

FieldPro custom properties on any object (Customer, Company, Work Order) require a pre-migration step to create matching Nutshell custom fields in Settings > Custom Fields. FieldPro stores custom field names and types in its schema export; FlitStack generates a Nutshell custom-field creation plan with field names, types (text, number, date, picklist), and pick-list options where applicable. After creation, data migrates directly into the new Nutshell custom fields.

FieldPro invoices and billing records do not map to a native Nutshell object. If invoice data contains meaningful context (e.g., linked deal value, payment status), FlitStack creates a Nutshell Note on the associated Deal record containing the invoice summary (number, amount, date, status). Invoice line items are included as note body text. For full invoice accounting, a separate export to accounting software is recommended.