Migrate from ServicePower HUB to HighLevel

ServicePower HUB customer records map directly to HighLevel Contacts. Customer name, phone, email, address, and service location transfer as Contact fields. A primary contact record is created per service location; duplicate customer names across locations merge on a per-location basis in HighLevel.

ServicePower HUB business accounts (e.g., property managers, HOA associations, commercial clients) map to HighLevel Companies. Company name, address, and industry classification transfer. Multi-location businesses create one Company record with each service location as a separate Contact record linked to the parent Company.

Work orders are the core migration object. Each work order migrates as a HighLevel Opportunity with a custom pipeline reflecting ServicePower HUB's job-status stages (e.g., Scheduled, Dispatched, In Progress, Completed, Invoiced). The Opportunity Name field concatenates Customer + Job Date for readability. Work-order IDs are preserved in a custom field for traceability.

ServicePower HUB job-status values (Created, Assigned, En Route, On-Site, Completed, Cancelled, On Hold) map one-to-one to HighLevel Opportunity pipeline stages. Each stage requires creation in HighLevel Pipelines before migration. Probability and forecast-category settings in HighLevel are applied per stage during the import run.

Technician records from ServicePower HUB migrate as HighLevel Contacts flagged with a custom field (Technician_Flag__c = true). If technicians also need HighLevel login access, User provisioning is separate — your team invites them after migration. Unmatched technician emails are flagged before migration so your admin can resolve access before go-live.

Each completed service event in ServicePower HUB generates a Task record in HighLevel linked to the corresponding Opportunity. The Task Subject field contains the service type; description captures resolution notes, parts used, and technician comments. Original timestamps and owner assignments are preserved from the source event.

Parts data from ServicePower HUB work orders migrates as a custom object (Parts_Used__c) with a many-to-one association to the Opportunity (work order). Each part record contains Part Number, Description, Quantity, and Unit Price. HighLevel limits custom objects to 10 per location — FlitStack validates part data volume before committing to this mapping strategy.

Warranty claim records and authorization states (Pending Authorization, Authorized, Parts Ordered, Claim Closed) migrate as a custom object (Claim__c) linked to the related Opportunity. Claim status maps as a pick-list field matching the source claim workflow state. Claim number from ServicePower HUB is preserved as the primary key for reconciliation.

ServicePower HUB invoices (COD or warranty-funded) migrate as a custom object (Invoice__c) linked to the Opportunity. Invoice amount, status (Paid, Unpaid, Disputed), and payment date transfer. HighLevel does not have a native accounts-receivable model — invoice records are for reference and reporting continuity, not AR management.

Scheduled appointment windows from ServicePower HUB map to HighLevel Calendar Events. The Event is linked to the related Opportunity and Contact. Capacity band information (e.g., 'Morning Slot 8AM–12PM') is captured in the Event description field as HighLevel Calendar does not natively support capacity-band scheduling.

ServicePower HUB tags (e.g., 'HVAC', 'Emergency', 'Warranty', 'Preferred Customer') migrate as HighLevel Tags. Tags apply to the Contact record and are used to segment lists and trigger workflow conditions in HighLevel. Tags with spaces use hyphens to match HighLevel's tag format.

Job photos and signed forms from ServicePower HUB work orders migrate as HighLevel Files attached to the corresponding Opportunity record. Files are re-uploaded to HighLevel's storage. File size limits (25MB per file in HighLevel) apply — oversized attachments are flagged and can be migrated in batches.

Any ServicePower HUB custom field on a Work Order, Contact, or Company migrates to a corresponding HighLevel custom field on the target object. HighLevel field types (text, number, date, pick-list) are matched to source field types. Pick-list value mappings are created value-by-value when pick-list options differ between platforms.

ServicePower HUB automations — dispatch rules, capacity-band scheduling, claim-authorization triggers, and automated reimbursement workflows — do not have a direct equivalent in HighLevel's Workflow Builder. FlitStack AI exports workflow definitions as a rebuild reference document. HighLevel's Workflow Builder must be used to recreate dispatch logic as conditional actions triggered by Opportunity stage changes.

ServicePower HUB analytics dashboards (KPIs, first-time fix rates, dispatcher utilization, job completion trends) do not migrate. Underlying data does transfer. HighLevel's reporting tools and pipeline analytics must be configured post-migration using the imported data. FlitStack delivers a data dictionary so your admin knows which source fields feed which HighLevel reports.