Migrate from MobileWorker to Nutshell

MobileWorker Workers map directly to Nutshell People, preserving name, email, and phone on a one‑to‑one basis. The worker's GPS coordinates (latitude and longitude) and availability status are stored as Nutshell custom fields Latitude__c, Longitude__c, and Worker_Status__c on the Person record. The original worker identifier is also retained for cross‑system reference.

Workers marked as inactive or archived in MobileWorker are routed to Nutshell Leads rather than People. This preserves the archive without cluttering your active contact list. The Worker_Status__c field on the Lead carries the original MobileWorker status value for reference.

Work Assignments that carry a revenue value, estimated cost, or billing reference convert to Nutshell Deals. The assignment's status pick-list maps to Nutshell's pipeline stage values, and Nutshell's Sales Processes control which stage options are available per Deal. The estimated_value field populates the Deal value, the due_date becomes the close_date, and any custom work_category field is migrated as a Work_Category__c custom pick-list on the Deal.

Routine Work Assignments that represent site visits, check-ins, or service calls without a revenue figure map to Nutshell Tasks (for one-off items) or Activities (for logged interactions). This prevents the activity log from being polluted with zero-value deals. The mapping also includes the assignment description mapped to the Task notes field, and the original MobileWorker assignment identifier preserved as a custom field for audit trail.

The customer or client referenced on a Work Assignment maps to a Nutshell Company (Account). FlitStack creates the Company record first so the Deal can reference it via the accountId field. Multi-location customers are stored as multiple address fields on a single Company.

MobileWorker's GeoJSON coordinate pairs are decomposed into separate Nutshell custom number fields: Location_Latitude__c and Location_Longitude__c. The street address component of the assignment location is mapped to the standard address fields on the related Company record. The decomposition follows the GeoJSON convention where the first element is longitude and the second is latitude. After extraction, the latitude is written to Location_Latitude__c and the longitude to Location_Longitude__c on the Company record.

MobileWorker's worker availability and status pick-list (Available, On Assignment, Off Duty, On Leave) has no direct Nutshell equivalent on the Person object. FlitStack creates a Worker_Status__c custom pick-list field on Nutshell People to preserve this status history at migration time.

MobileWorker Activity Log entries (call records, check-in timestamps, site visit notes) map to Nutshell Activities with the original timestamp, activity type, and linked Person preserved. The Activity Type field in MobileWorker populates the Subject line in Nutshell. If the activity includes a notes field, that text is copied into Nutshell Activity notes property. Person reference is resolved using the worker's email address to ensure activity appears on contact timeline.

MobileWorker custom fields defined on the Worker object (certification types, vehicle ID, territory assignment) migrate to Nutshell custom fields on the Person object. Custom field type (pick-list, text, number, date) is preserved to avoid data type conflicts in Nutshell. Including any default values and field labels that are carried over to maintain consistent data entry across systems.

Assignment-level custom fields (work category, service type, customer PO reference) migrate to equivalent custom fields on the target Nutshell object (Deal for revenue assignments, Task for service items). Field type mapping is preserved. The migration preserves pick-list values, default values, and validation rules from MobileWorker so same constraints apply in Nutshell. Cross-references to other MobileWorker objects are stored as text strings in Nutshell fields until a manual link is created.

Files attached to Work Assignments in MobileWorker are downloaded and re-uploaded as Nutshell Notes attached to the corresponding Deal or Task. Nutshell's attachment model uses its own file storage; inline images in notes are re-hosted during migration. File name and upload timestamp are preserved in the note description. The re-hosting process uses Nutshell's API file upload endpoint, and GIS layer references are skipped because Nutshell does not support spatial overlays.

The MobileWorker owner or manager ID on a Worker record is resolved against Nutshell user email addresses. Unmatched owners are flagged before migration. You can assign them to a Nutshell user or a default owner before the full run commits.

MobileWorker assignment priority values (Emergency, High, Normal, Low) map to Nutshell's deal priority pick-list or a custom Priority__c field on the Deal object. The value mapping is applied per pick-list item during the migration run. If the Nutshell account uses Sales Processes, the process can have its own priority pick-list; FlitStack applies the mapping based on the process. Unmapped priority values default to the low priority option and are logged.

MobileWorker's ArcGIS map overlays, routing polygons, and geofencing data are GIS-specific constructs with no equivalent in Nutshell's data model. These are not migrated. FlitStack exports the GIS layer definitions as a reference document for teams that need to rebuild routing logic in ArcGIS Workforce separately.