Migrate from ServiceTracker to Nutshell

ServiceTracker Customer records map directly to Nutshell Companies. The primary company name, billing address, and phone fields transfer as-is. If the ServiceTracker Customer has multiple active Sites, we create one Nutshell Company per Site and link them using a Parent Company custom field — your admin chooses whether to flatten to one Company or keep the split.

ServiceTracker Site records carry address, GPS coordinates, access instructions, and site-specific contact info. We store the primary site address on the Nutshell Company address fields. Additional site addresses, GPS coordinates, and access notes migrate as custom text fields (Site_Address_2__c, GPS_Lat__c, GPS_Lng__c, Access_Notes__c) so the full location data is preserved for reference even though Nutshell displays only one address by default.

ServiceTracker Work Orders are complex records with status, priority, scheduled date, assigned technician, parts used, and service notes. We split Work Order data across two Nutshell objects: billable engagements become Nutshell Deals (so they appear in the pipeline), and non-billable service visits become Tasks attached to the linked Company. The original Work Order number is stored as a custom field (ST_Work_Order_Number__c) for traceability.

ServiceTracker Work Order status values (New, Scheduled, In Progress, Completed, Cancelled, On Hold) map to Nutshell Deal stage values. The mapping is configured before migration — common patterns map 'Completed' to a 'Closed Won' stage and 'Cancelled' to 'Closed Lost'. Stage entered timestamps are preserved as a custom datetime field since Nutshell does not track stage history on Deals by default.

ServiceTracker Assets carry serial numbers, make/model, warranty expiration, and maintenance history. Nutshell has no native asset object. Serial number and make/model data migrate as custom text fields on the linked Company record (Asset_Serial_Number__c, Asset_Make__c, Asset_Model__c). Maintenance history migrates as a formatted note or series of Tasks rather than a structured asset history record.

ServiceTracker Service Request records (non-dispatched issues, inbound support calls logged as records) map to Nutshell Tasks attached to the relevant Company. Original create date and owner are preserved. If the Service Request is linked to a specific Asset, we store the asset reference in a custom text field on the Task.

ServiceTracker Technicians are user-level records with name, email, phone, certification, and crew assignment. We resolve each Technician to a Nutshell user account by email address. Unmatched technicians are flagged before migration — your team either creates Nutshell user accounts first or assigns those records to a fallback Nutshell user. Crew assignment data migrates as a custom text field (Crew__c) on the resolved user's tasks.

ServiceTracker parts and inventory line items attached to Work Orders have no direct Nutshell equivalent. We preserve this data as a formatted note attached to the associated Deal, capturing part number, quantity, and cost. Nutshell's product catalog is not used because it is designed for sales products, not service parts.

ServiceTracker custom fields (Salesforce __c fields) on any object map to Nutshell custom fields on the equivalent object. Text, number, date, and dropdown types map directly. Picklist values require a value-by-value review since Nutshell dropdown options are managed in settings and must be pre-created before the migration run.

ServiceTracker file attachments on Work Orders, Sites, and Assets are downloaded and re-uploaded as files attached to the equivalent Nutshell Company or Deal record. File size limits follow Nutshell's platform constraints. Inline images in notes are extracted, rehosted, and re-embedded in the note body.

ServiceTracker routing data, scheduled time blocks, and dispatch logic are built on ServiceTracker's scheduling engine and have no equivalent in Nutshell. This data is not migratable. We provide a reference export of active routes and schedule data in CSV/JSON format that your team can use to rebuild routing in a scheduling tool of your choice.

ServiceTracker service contracts with terms, renewal dates, and coverage scope migrate as a formatted note on the Nutshell Company. Contract end dates and coverage type are extracted into custom date and text fields (Contract_End_Date__c, Coverage_Type__c) for renewal tracking, but the contract document itself becomes an attached file.