Migrate from ServicePower HUB to Pipedrive

ServicePower HUB customer records merge contact information with company data. We split these into Pipedrive Person records for primary contacts and Organization records for the service company, preserving the customer identifier as a custom field on both for traceability back to ServicePower HUB.

Each ServicePower HUB service location becomes a Pipedrive Organization with custom address fields to store the physical service address separately from the customer's billing address. Multiple locations per customer create multiple Organization records linked to the same Person record. Each location also receives a Source_Location_ID__c custom field to preserve the original ServicePower HUB identifier, enabling downstream reporting to roll up all locations under a single customer view.

ServicePower HUB work orders map directly to Pipedrive Deals. The work order status (Scheduled, In Progress, Completed, Invoiced) maps to Pipedrive Deal stage values, with each ServicePower HUB pipeline requiring a corresponding Pipedrive pipeline. Work order value maps to Deal value.

ServicePower HUB parts and labor line items map to Pipedrive Deal Products. Each line item becomes a product entry on the Deal with quantity, unit price, and total — preserving the itemized service revenue structure from the original work order.

ServicePower HUB technician records resolve to Pipedrive Users by email match. Each technician assigned to work orders appears as a Task owner or Deal co-owner in Pipedrive. Contracted vs. employed distinction is preserved as a custom field on the User record.

ServicePower HUB warranty claim status and authorization codes migrate as custom fields on the Pipedrive Deal. The warranty flag is preserved as Warranty_Claim__c and the authorization number as Warranty_Auth_Number__c for downstream billing reconciliation. Additional claim metadata such as claim date, OEM reference, and reimbursement amount can also be added as Deal custom fields during migration if required for reporting or integration with third‑party claim administrators.

ServicePower HUB parts catalog entries map to Pipedrive Products, transferring part number, description, and unit cost into Pipedrive’s product pricing structure. Product images and descriptive attributes are also preserved for use in Pipedrive’s quoting and proposal workflows. If your organization tracks reorder thresholds or vendor codes, those can be added as custom fields on the Product object during migration to maintain inventory‑level visibility.

ServicePower HUB payment collected records have no direct Pipedrive equivalent. Payment history migrates as Note activities attached to the Deal, preserving the payment date, amount, and method. For full payment accounting, Pipedrive's accounting integration or a linked QuickBooks/Xero connection must be configured post-migration.

ServicePower HUB custom fields on work orders — such as service type codes, customer reference numbers, or dispatch notes — migrate to Pipedrive Deal custom fields with matching field types. Field names are preserved exactly; Pipedrive's hash-key system is handled internally for API mapping.

ServicePower HUB custom fields on customer records map to Person or Organization custom fields in Pipedrive based on whether the attribute belongs to the individual contact or the company entity. Text, number, date, and pick‑list fields transfer with matching types; customer‑specific pricing tiers become Organization pick‑list fields for tier‑based pricing visibility. All destination custom fields are created in Pipedrive before migration for stable API mapping.

ServicePower HUB work order status history — timestamps for scheduling, dispatch, arrival, and completion — migrates as a series of Note activities on the Pipedrive Deal, each tagged with the original status, technician name, and exact timestamp. This preserves a complete audit trail in Pipedrive so users can review every transition that occurred in the original system without losing context.

ServicePower HUB attachments on work orders — such as photos, signed forms, and invoices — are re‑uploaded to Pipedrive Files linked to the corresponding Deal record. Pipedrive enforces a 50 MB per‑file limit; any file exceeding this threshold is split or linked via an external reference. Inline images embedded in ServicePower HUB notes are extracted, downloaded, and re‑hosted as Pipedrive Deal attachments, preserving file name and upload date for audit compliance.