Migrate from ServicePower HUB to Twenty CRM

ServicePower HUB WorkOrder holds job number, status, scheduled date, assigned technician, service location, labor hours, parts costs, and warranty/COD flags. Twenty has no native work-order object — these map to Twenty Tasks with custom fields for priority, workOrderType, laborHours, partsCost, warrantyFlag, and codFlag. All status string values (e.g., 'Pending_Scheduled', 'InProgress', 'Tech_Dispatched', 'Completed') map to a custom pick-list in Twenty's data model, created in Settings → Data Model before import.

ServicePower HUB Customer stores the primary contact's name, email, phone, job title, and service address. These map directly to Twenty People fields. The customer record may also contain a companyName that routes to a Company record in Twenty. The customer.email field serves as the unique identifier for People import in Twenty.

ServicePower HUB Technician stores firstName, lastName, email, phone, and skill tags. These map to Twenty People records. Technician skills (a comma-separated or multi-value field in ServicePower HUB) migrate to a custom multi-select field (technicianSkills__c) in Twenty. Technician records are imported after Company records so companyId relationships resolve correctly.

ServicePower HUB Company stores business name, website, industry, employee count, and annual revenue. These map to Twenty Companies fields where native equivalents exist. Industry, employeeCount, and annualRevenue do not exist as standard Twenty Companies fields — these become custom fields created in Twenty Settings → Data Model before import. Companies import first because People records in Twenty require a companyId link.

ServicePower HUB WarrantyClaim holds claim number, associated WorkOrder reference, claim status, submitted date, approved amount, and denial reason. Twenty has no native claim object — a custom object named WarrantyClaim is created in Twenty Settings → Data Model before import, with fields for claimNumber, workOrderId, status, submittedDate, approvedAmount, and denialReason. The custom object is imported after both Companies and People to resolve all foreign keys.

ServicePower HUB WarrantyClaim status values (e.g., 'Submitted', 'UnderReview', 'Approved', 'Denied', 'Closed') map to a custom pick-list field on the WarrantyClaim custom object in Twenty. The pick-list options must be created in Settings → Data Model before the WarrantyClaim import runs. Each value maps 1:1 with a note in the mapping document for admin review.

ServicePower HUB Part stores part number, description, cost, list price, and associated WorkOrder reference. Twenty has no native parts or inventory object — a custom object named Part is created in Settings → Data Model with fields for partNumber, description, cost, listPrice, and workOrderId. Parts are imported after WorkOrders since the WorkOrderId foreign key must resolve to an existing Twenty Task.

ServicePower HUB WorkOrder stores service location as a structured address block (street, city, state, postalCode, country). The customer record in ServicePower HUB also holds a billing address. These two address structures merge into the service address on the linked Twenty People record — Twenty stores one address per Person. If both service and billing addresses exist, the service address is prioritized on the Person record and the billing address is stored in a custom field.

ServicePower HUB WorkOrder.assignedTechnicianId references a Technician record. This maps to Twenty People records that were imported as Technicians — the Twenty Task.assignedTo field links to the People record by email match. Unmatched technician IDs are flagged before the migration runs, and a fallback assignee is assigned to prevent orphaned task records in Twenty.

ServicePower HUB Contract stores contract number, customer reference, start date, end date, and contract type (warranty, service-level). A custom object named Contract is created in Twenty Settings → Data Model with these fields plus a companyId link to the associated Twenty Company. Contracts are imported after Companies so the companyId foreign key resolves correctly.

ServicePower HUB WorkOrder holds free-text notes from technicians (job completion notes, parts used, customer signatures). These migrate as Twenty Notes attached to the corresponding Task record. Original timestamps are preserved. Notes are imported after both WorkOrders (as Tasks) and People so the parent record ID resolves correctly.

Any custom objects in ServicePower HUB not covered by the standard mapping (e.g., InventoryItem, ServiceAgreement, CustomerPortalSetting) are assessed individually. Each becomes a Twenty custom object created in Settings → Data Model with equivalent fields. The mapping plan identifies which fields map directly, which need custom fields, and which require value translation — this is delivered before the migration runs so Twenty's schema is ready for import.