Migrate from ServicePower HUB to HubSpot

ServicePower HUB customers map to HubSpot contacts for the primary person and HubSpot companies for the organization. Physical address, phone, and email transfer as standard HubSpot contact properties. Customer type (commercial/residential) maps to a custom contact property. The company association links the contact to the correct organizational account in HubSpot for proper deal and ticket attribution.

ServicePower HUB work orders become HubSpot tickets with all standard ticket properties populated from the source record. Job type (COD/Warranty) migrates as a custom pick-list property on the ticket. Original ServicePower HUB work order number is preserved as Ticket_ID__c for traceability back to the source system, allowing support teams to reference the original record if needed.

ServicePower HUB invoices become HubSpot deals with deal name matching the invoice number, amount matching total, and close date matching payment due date. Payment status (pending/paid/cancelled) maps to a custom deal property since HubSpot's native deal stages are sales-stage-oriented rather than accounting-focused, requiring a custom field to track actual payment state accurately.

ServicePower HUB jobs carry technician assignment, job type, capacity band, parts used, and warranty claim details that don't fit neatly into HubSpot tickets. We create a custom Service_Event__c object in HubSpot with fields for sp_job_type, sp_technician_email, sp_capacity_band, sp_warranty_claim_id, and sp_parts_used as a multi-select or custom object.

ServicePower HUB technician records (whether employed or contracted) become HubSpot contacts with a custom type property set to 'Technician'. Employee status, capacity band, service zone, and skill certifications map to custom contact properties. Contractor rate and payment terms become custom properties if present in ServicePower HUB.

ServicePower HUB's capacity band model (defining how many jobs a technician can handle per day by service type) has no HubSpot native equivalent. We migrate the active capacity band as a custom pick-list property (sp_capacity_band__c) on the technician contact. Scheduling rebuild requires HubSpot Meetings or a third-party field service app.

Warranty claim ID, OEM/TPA reference, and claim status (submitted/approved/denied/paid) migrate as custom properties on both the HubSpot ticket and the associated deal. ServicePower HUB's warranty job routing logic does not transfer — rebuild in HubSpot Flow with conditional branches based on warranty claim status.

Cash-on-demand job classification is preserved as a custom pick-list value on the ticket. COD job flags like customer_payment_status and COD_invoice_number migrate to custom properties on the associated deal. Payment processing logic (COD Pro in ServicePower HUB) requires rebuild via HubSpot payments integration or a third-party payment processor.

ServicePower HUB parts linked to work orders map to a custom Parts_Used__c object with fields for part_number, description, quantity, and distributor. Parts_Used__c is associated to the ticket via a lookup relationship. Native inventory tracking is not available in HubSpot — consider Sortly or a custom integration for ongoing parts management.

ServicePower HUB's self-service portal logs customer-initiated job scheduling and status checks. These activities become notes or tasks on the HubSpot ticket. The portal functionality itself requires Service Hub Enterprise configuration, which is available only on the Enterprise tier. Customers lose self-service access unless the organization upgrades or builds a custom portal solution.

File attachments and technician photos linked to ServicePower HUB work orders re-upload to HubSpot Files and attach to the corresponding ticket. All uploaded files are subject to HubSpot's file size limits, supported format restrictions, and inline image handling constraints for display within ticket records.