Migrate from Oracle Field Service Cloud to Nutshell

OFSC activities map to Nutshell Tasks. The activity description becomes the task name, the OFSC status and priority map to custom choice fields in Nutshell, and the technician (resource) assignment becomes a custom Person link or text field. OFSC's activity date becomes the task due date. Routing plan names and work zone codes are stored in custom text fields since Nutshell has no routing context.

OFSC resources (technicians, dispatchers) map directly to Nutshell People records. The resource name, email, phone, and status fields translate straightforwardly. Skill certifications and work zone assignments are preserved as Nutshell custom fields since no native equivalent exists in Nutshell's Person object.

OFSC customer data linked to activities is merged into Nutshell Company and Person records. When OFSC stores a customer with both company name and contact name, both are created — company as the Account and the person as the primary contact. When only a customer name exists with no company, it lands as a Nutshell Person with the company name in a custom field.

OFSC location addresses map to the address fields on the linked Nutshell Company or Person record. The full street, city, state, postal code, and country fields transfer directly. If a location has multiple contacts at the same address, the address is stored once on the Company and shared.

OFSC work zones define geographic clustering for technician assignment and route optimization. Nutshell has no native zone concept or geographic clustering model. FlitStack creates a custom text field (Work_Zone__c) on the Nutshell Task and stores the OFSC work zone code for reference, reporting filters, and team visibility into the original FSM geographic context.

OFSC skills and certifications assigned to resources (technicians) are stored as Nutshell custom fields on the Person record. A multi-select custom field captures all certifications for each migrated resource. If OFSC uses a structured pick-list, the corresponding Nutshell custom field is created as a choice field with the same options.

OFSC custom properties on activities — such as job type classification, customer property type, or parts used — are created as Nutshell custom fields on the Task object. Each custom property in OFSC is evaluated for type parity: text maps to Nutshell text, numeric maps to number, choice maps to choice.

OFSC activities can record parts consumed and inventory used during a service visit. Nutshell has no parts or inventory tracking. FlitStack captures this as a long-text custom field (Parts_Used__c) on the Task, concatenating the parts list from OFSC into a readable string for reference. If parts tracking is critical, this is surfaced as a manual-rebuild candidate.

OFSC technician time-clock entries map to Nutshell Task duration. The elapsed time from OFSC becomes the estimated duration field in Nutshell, preserving the work duration for scheduling and reporting purposes. For time entries that include technician notes or comments, those details are appended to the task as a note for future reference and audit trail continuity.

OFSC routing plan names represent the optimized route configuration used for a day's dispatch. Nutshell has no routing model. FlitStack stores the routing plan name in a custom text field (Routing_Plan__c) on the Task as a reference attribute — useful for managers reconciling which OFSC plan generated a given set of tasks.

OFSC capacity and quota configurations govern technician availability windows and booking interval limits. Nutshell has no native capacity management. This OFSC configuration is documented in the migration plan as a manual-rebuild candidate — if capacity management is needed in Nutshell, it requires a third-party integration or custom development.

OFSC attachments — including before/after photos, customer signatures, and inspection images — are downloaded and re-uploaded to the linked Nutshell Task as file attachments. Nutshell's file size limits are applied; images over 25MB are flagged before migration for manual handling.