Migrate from ServicePower HUB to Freshsales

ServicePower HUB Customer Location records represent service addresses (homes or businesses where work is performed). We map these to Freshsales Accounts — the street address, city, state, and zip code fields transfer directly. Customer Location type (residential/commercial) migrates as a custom pick-list field on the Account record for segmentation.

Each contact linked to a Customer Location (homeowner, tenant, authorized representative, property manager) maps directly to a Freshsales Contact. The contact's name, phone, email, and role on the service event transfer as Contact fields. Multiple contacts per Customer Location collapse to multiple Contact records, all linked to the same Account.

ServicePower HUB work orders have no direct Freshsales equivalent — Freshsales has no native service-event object. We create a custom module in Freshsales named 'Service Events' to hold work order data. This module stores job status, service type, description, scheduled date, actual completion date, and original ServicePower HUB work order ID for traceability.

Parts used, labor entries, and sublet charges attached to a ServicePower HUB work order transfer as line-item records within the Service Events custom module. Each line item stores part number, description, quantity, unit cost, and total — mapped to custom fields on the Service Events module or as related custom child records if the FSM scope requires separate tracking.

ServicePower HUB technicians and dispatch-eligible contractors resolve to Freshsales Users by email match. If a technician email matches an existing Freshsales user, the service-event record is assigned to that user. Unmatched technicians are flagged and assigned to a fallback Freshsales user — the original technician name and skill certifications are preserved in a custom field on the Service Event record.

ServicePower HUB service event lifecycle statuses (Scheduled, Dispatched, In Progress, Completed, Cancelled, No Fix) map to a custom pick-list field on the Service Events module. Each ServicePower HUB status value has a corresponding Freshsales pick-list value created during schema setup.

Warranty claims submitted through ServicePower HUB carry OEM authorization numbers, coverage type, claim status, and payout amounts. We create a second custom module (Warranty Claims) linked to Service Events via a lookup field. OEM authorization numbers, coverage type, and claim status become custom fields on this module; payout amounts store as currency fields.

ServicePower HUB parts catalog entries (part number, description, list price, applicable model numbers) map directly to Freshsales Product Catalog records. The part number maps to the product's SKU field, description to product name, and list price to unit price. This enables Freshsales quotes to reference service-part pricing if the team rebuilds a quoting workflow.

Cash-on-demand payment records from ServicePower HUB (payment method, amount collected, authorization code, payment date) transfer as custom fields on the Service Events module. Payment status (Collected, Pending, Refunded) maps as a custom pick-list. Full payment transaction history is preserved as JSON-serialized data in a long-text custom field for audit continuity.

Photos and documents attached to ServicePower HUB work orders — before/after photos, signed service agreements, parts receipts — are downloaded and re-uploaded to Freshsales as file attachments on the corresponding Service Events record. File size limits are enforced per Freshsales storage plan.

ServicePower HUB technician capacity bands and scheduling rules (skill criteria, geographic zones, availability windows) have no native Freshsales equivalent. We preserve the configuration as an exported JSON reference file for a Freshworks developer or admin to rebuild using Freshsales workflow conditions and Freshservice scheduling modules.

ServicePower HUB's third-party administrator (TPA) links and contractor network assignments (relationships to external service networks) have no direct Freshsales equivalent. We preserve the TPA contract reference and network ID as custom fields on the Account or Service Events record for rebuild reference.