Migrate from Field Services Workflow and Logistics to Nutshell

WorkOrder is the primary FSM record and maps directly to Nutshell Deal. FlitStack AI preserves the WorkOrder subject as the Deal name, WorkOrder status as a custom picklist field, and original create/update timestamps as custom datetime fields. The WorkOrder's AccountId resolves to a Nutshell Company record before the Deal is created — foreign-key ordering is handled automatically by the migration sequencing.

WorkOrderLineItem has a parent-child relationship under WorkOrder with line-type, quantity, unit price, and product-service description. Nutshell has no native line-item child object, so FlitStack AI collapses line-item data into a JSON-serialized custom text field on the Deal or attaches a formatted note listing all line items with quantities and amounts. The most-complete line (by total price) becomes the primary Deal amount; remaining lines are preserved in the serialized field.

ServiceAppointment stores the scheduled date, duration, status, and address for each field visit. FlitStack AI maps ServiceAppointment to a Nutshell Task with the original appointment date as the due date, appointment status as a custom picklist, the service address as a note on the Task, and the assigned technician's email resolved to a Nutshell user. The Task is linked to the parent Deal that resulted from the WorkOrder.

AssignedResource links a Resource (technician) to a ServiceAppointment or WorkOrder. Nutshell has no native many-to-many assignment object, so FlitStack AI creates a Person record for each technician (if one does not already exist) and stores the assignment relationship in a custom field on the Deal or as a tagged note referencing the ServiceAppointment. The technician's email is matched to an existing Nutshell user for owner resolution.

SkillRequirement stores the skill type and proficiency level required for a ServiceAppointment. Nutshell has no native skill or certification object, so FlitStack AI maps skill names to a multi-select picklist custom field on the Person record (technician) and appends a note listing all skills with their proficiency levels and associated ServiceAppointment references. Skills are searchable in Nutshell via the custom field.

The Salesforce Account representing the customer maps to a Nutshell Company. FlitStack AI preserves the Account name as Company name, the billing address as the primary address, industry as a picklist (value-mapped where FSM industry codes differ from Nutshell's defaults), and annual revenue as a number field. The original Salesforce AccountId is stored in a custom field on the Nutshell Company for traceability.

Contact records on the Salesforce Account map to Nutshell Person records. FlitStack AI maps first name, last name, email, phone, and job title directly. If a Contact record has no email address (common for technical contacts on service accounts), it is imported with the phone and name fields; a warning is logged for manual review. The original Salesforce ContactId is stored in a custom field on the Nutshell Person.

Entitlement defines service contract coverage (SLA type, entitlement number, business hours). Nutshell has no native entitlement object, so FlitStack AI maps entitlement data to a custom field on the relevant Company record (contract type, expiry date, business hours reference) and optionally links it to the Deal via a custom Deal field referencing the entitlement number. Contract expiry dates are preserved as date fields for renewal tracking.

ResourceAbsence tracks technician vacation, sick days, and training blocks with start and end timestamps. Nutshell lacks a native absence calendar, so FlitStack AI stores absence ranges as custom date-pair fields on the technician's Person record and attaches a formatted note listing all historical absence records with dates and reasons. Active or upcoming absences are surfaced in the migration report for scheduling coordination in Nutshell.

Salesforce Field Service adds custom fields to WorkOrder using the __sf_fsl namespace — these include service-type codes, priority tiers, dispatch windows, and SLA flags. Nutshell requires each FSM custom field to be manually recreated as a Nutshell custom field on the Deal object before migration. FlitStack AI generates a custom-field creation plan listing every FSM __sf_fsl field with its Nutshell type equivalent (text, number, date, picklist) so your Nutshell admin can pre-create the fields before the migration run.

Custom fields on ServiceAppointment (such as travel-time estimates, signature-capture flags, or service-result codes) do not have a Nutshell equivalent and must be created as custom fields on the Task object. FlitStack AI documents every ServiceAppointment custom field and its type, providing your Nutshell admin with the exact field name, type, and picklist options to create before the migration runs.

Salesforce Files attached to WorkOrder or ServiceAppointment records are downloaded and re-uploaded to the corresponding Nutshell Deal or Task. FlitStack AI handles file type detection, preserves the original file name and content version metadata, and logs any files exceeding Nutshell's attachment size limits (typically 25MB per file) for manual handling. Inline images embedded in rich-text fields are extracted and rehosted separately.