Migrate from Handyman to Twenty CRM

Handyman customers (contact records with name, email, phone, and service address) map directly to Twenty's People object. Service address fields that don't exist as standard Twenty fields are stored in custom fields on the People record. If a customer has multiple service locations, each location becomes a separate People record with a custom ServiceLocation custom field to differentiate them.

Handyman business accounts (commercial customers with company name, industry, and billing address) map directly to Twenty's Company object. Company records are imported first because Twenty's People object links to Company via the companyId relation field — the 'one' side of the relationship must exist before the 'many' side is loaded.

Handyman jobs are work orders with status (scheduled, in-progress, completed, cancelled), assigned technician, service type, service address, scheduled date, and completion notes. Twenty has no native work-order object. We create a WorkOrder custom object via Twenty's metadata API at Settings → Data Model before migration, with fields for jobId, status, technicianOwnerId, serviceTypeId, scheduledDate, completedDate, and completionNotes. The WorkOrder links to the People record representing the customer.

Handyman job line items (labor hours, material costs, and service codes) translate to a WorkOrderLineItem custom object linked to the WorkOrder by a relation field. Each line item includes description, quantity, unit price, total, and lineType (labor vs. material). This custom object is created alongside the WorkOrder object in Twenty's data model setup phase.

Handyman invoices map to a custom Invoice object in Twenty, linked to the People record (customer) and optionally to the related WorkOrder. The custom Invoice object holds invoiceNumber, invoiceDate, dueDate, totalAmount, status (draft, sent, paid, overdue), and paymentMethod. Invoice line items are stored in a related InvoiceLineItem custom object.

Handyman service types (e.g., plumbing repair, electrical, HVAC maintenance) with their pricing rules become a custom ServiceType object in Twenty linked to WorkOrder records. Alternatively, for simpler setups, a custom pick-list field on WorkOrder (Service_Type__c) is used. Which approach is chosen depends on whether service types have additional metadata (descriptions, default pricing) that warrants a full object.

Handyman tracks customer equipment (HVAC units, water heaters, appliances) as Assets linked to the customer record. In Twenty, we create a custom Asset object with fields for assetId, name, equipmentType, manufacturer, model, serialNumber, installDate, and linkedPeopleId (relation to the People record). If the business only tracks equipment on closed deals, Opportunity records can store this in a custom field instead.

Handyman users (technicians and office staff) are matched to Twenty Workspace Members by email address. Twenty requires all workspace members to be invited and to accept their invitation before user lookups on records can resolve. We flag any Handyman users without a matching Twenty member and assign their records to a fallback member or leave the owner field blank for manual assignment after migration.

Handyman file attachments (photos, signed forms, inspection reports) are downloaded and re-uploaded to Twenty's file storage, then linked back to the parent People, WorkOrder, or Invoice record by ID. Handyman does not expose attachments via a public API in all tiers, so the export method (direct download vs. manual export) is confirmed in the data audit phase before the migration plan is finalized.

Handyman job notes and internal comments map to Twenty's standard Note object. Notes are linked to the parent record (People or WorkOrder) via the noteTargetId relation. Original timestamps and note authors are preserved. Rich-text formatting in Handyman notes is flattened to plain text during migration to ensure compatibility with Twenty's Note field type.

Handyman follow-up tasks and reminders map to Twenty's standard Task object. Tasks are linked to the parent People or WorkOrder record via the taskTargetId relation. Status (open, completed), due date, and assignee are preserved. Completed tasks retain their completion timestamp for historical completeness in Twenty's activity view.

Handyman tags on customers and jobs are mapped to a custom Tag__c multi-select field on the relevant Twenty object. Each unique Handyman tag value is created as an option in the pick-list. If there are more than 50 unique tags, a custom Tag object with a many-to-many relation to People and WorkOrder is created instead to avoid pick-list overflow.