Migrate from ServicePower HUB to Nutshell

ServicePower HUB's servicer accounts (the service company using HUB) map to Nutshell Companies. Company name, address, contact phone, and billing configuration export from ServicePower HUB and land as the Nutshell Company record. Parent-child servicer hierarchies map via Nutshell's parent company linkage.

End-customer contact records from ServicePower HUB (name, email, phone, address, preferred contact method) migrate as Nutshell People. Original ServicePower HUB create date is stored in a custom datetime field on the Person record since Nutshell's native created date reflects the import timestamp, not the source-system creation date.

ServicePower HUB work orders have no direct Nutshell equivalent. We aggregate work-order summaries (most recent job date, total job count, last service type, warranty flag) and store them as custom fields on the associated Person record. Individual work-order detail can be exported as a JSON blob attached to the Person for audit purposes.

Parts used per work order aggregate into a text field on the Person record listing part numbers and descriptions. Nutshell has no line-item model, so we concatenate the most common parts (top 5 by frequency) into a pipe-delimited string. Full parts history exports as a separate reference file for rebuild in a parts-tracking system.

ServicePower HUB technician and contractor names, IDs, and skill certifications have no Nutshell equivalent. We create a Contractor_Reference__c custom field on Nutshell People to store the primary contractor name and ID for each customer. Multiple contractors attach as a comma-separated list. Nutshell does not have a native user-equivalent for field technicians — they are data, not Nutshell users.

Warranty claim data from ServicePower HUB includes claim status (approved, denied, pending), claim number, coverage type, claim amount, and claim date. ServicePower HUB's third-party administrator (TPA) integration details also migrate as text fields. We store these as custom fields on the Nutshell Person record: Warranty_Claim_Number__c, Warranty_Claim_Status__c, Warranty_Coverage_Type__c, and Warranty_Claim_Amount__c. Claim outcome dates preserve for warranty expiry auditing and historical reference. This data is read-only in Nutshell with no automatic status updates.

ServicePower HUB payment transactions (COD payments, warranty reimbursements) export as Nutshell Notes on the Person record. Transaction amount, date, and payment method serialize into the note body. Nutshell has no native accounting or payment object — this is reference data, not financial reconciliation.

ServicePower HUB schedule blocks and appointment windows cannot map to Nutshell Tasks, which lack scheduling engine context (capacity, technician availability, geographic dispatch). We export schedule data as a CSV reference file. Teams that need scheduling must use a dedicated FSM tool post-migration.

Parts ordering history from ServicePower HUB's distributor API includes part numbers, quantities ordered, unit costs, and estimated arrival dates. Since Nutshell has no purchase-order or procurement module, this ordering history migrates as Nutshell Notes attached to the Person record. Each note captures the distributor name, part specifics, quantity, cost, and fulfillment status. This is purely historical reference data with no procurement functionality in Nutshell.

ServicePower HUB equipment records include model numbers, serial numbers, installation dates, and warranty expiration dates. This equipment data migrates as custom fields on the Nutshell Person record: Equipment_Model__c, Equipment_Serial__c, Equipment_Install_Date__c, and Equipment_Warranty_Expiry__c. When customers have multiple assets, the values concatenate into pipe-delimited strings to preserve all records. A separate equipment service history export preserves the full maintenance log per asset.

ServicePower HUB lead records (prospective customers not yet converted to active service accounts) map 1:1 to Nutshell Leads with name, contact info, source, and status. Lead scoring or qualification data from ServicePower HUB migrates as a custom integer field on Nutshell Lead.

ServicePower HUB service contracts or recurring service agreements that function as sales pipeline items map to Nutshell Deals. Deal name, value, stage (Active, Completed, Cancelled), expected close date, and owner migrate directly. Nutshell Deal custom fields store contract-specific terms such as contract duration, renewal dates, and service-level agreements that align with the original ServicePower HUB contract configuration.