Migrate from FRONTU to Nutshell

Frontu Workers map 1:1 to Nutshell People. First name, last name, email, phone, and role transfer directly. Worker type (Technician, Admin, Manager) is preserved as a Role__c custom field on the Person record since Nutshell has no native role classification for People.

Frontu Customers map directly to Nutshell Companies with company name, address fields, phone, website, and industry transferred on a field-for-field basis. Customer type (Commercial, Residential, Industrial) is preserved as a Customer_Type__c custom pick-list field on the Nutshell Company record. The Frontu customer ID is stored as Source_System_ID__c for delta-run reconciliation and audit traceability.

Frontu Locations store site name and GPS coordinates. The primary service address transfers to the Company address fields. Site-specific names (e.g., Warehouse A, Branch Office) map to Location_Name__c on the Company. When a Customer has multiple Locations, each location name becomes a separate Company record with a shared parent relationship.

Frontu Tasks translate to Nutshell Activities (Task type). Task name becomes the Activity subject. Task status, priority, type, and technician assignment are stored as custom fields on the Activity: Work_Order_Type__c, Priority__c, Task_Status__c, Technician_Name__c. Original creation timestamps and work-order IDs are preserved as custom fields for audit continuity.

Frontu process templates define standardized task checklists and routing logic. Nutshell has no native process-template object. Template names and step descriptions are captured as Process_Template__c and Process_Steps__c custom fields on the Activity for reference, but the automation logic must be rebuilt as Nutshell workflow rules or sequence steps.

Work orders in Frontu aggregate multiple tasks under a single job. Nutshell has no work-order object — we create a primary Activity record per work order with a Work_Order_ID__c custom field linking to the source system. Individual tasks under the work order become linked Activity records. Total work-order value, if tracked, becomes Estimated_Value__c on the primary Activity.

Frontu asset registers track equipment linked to customers and locations. Nutshell has no native asset object. We create a custom Asset__c object with fields for name, serial_number__c, equipment_type__c, install_date__c, and a lookup to the linked Company record. The asset-to-location relationship is preserved via the Company link.

Frontu worker records are matched to Nutshell Users by email address. Any Frontu worker without a matching Nutshell user email is flagged before migration — those records are assigned to a fallback Nutshell user or left unassigned pending admin action. Original Frontu owner ID is preserved as Source_Owner_ID__c on migrated records.

Files attached to Frontu tasks — including photos, signatures, and job-site documents — are downloaded from Frontu storage and re-uploaded as attachments on the corresponding Nutshell Activity record. Each file is validated against Nutshell's supported file types and size limits before upload, with any oversized files flagged for external storage and URL linking.

Frontu custom fields on any object (Worker, Customer, Task, Location) are created as matching custom fields in Nutshell on the target object. Field type is mapped: text → text, number → number, date → date, pick-list → pick-list. Frontu pick-list values are preserved as Nutshell pick-list options so no data is lost during the type translation.