Migrate from The Service Program to Twenty CRM

TSP's customer record holds both company-level data (business name, billing address) and contact-level data (primary contact name, phone, email). We split this into a Twenty Company record for the business entity and a Person record for the primary contact, linking them via the company's domain or name match.

TSP supports multiple service locations per customer — each with its own address and equipment list. In Twenty, these can map as secondary Company records linked via a custom ServiceLocation relation field, or as a Custom Object with a companyId relation depending on whether the team treats locations as sub-accounts or standalone entities.

A TSP Service Request captures the customer's issue or recurring service need — analogous to an Opportunity in Twenty representing a deal or service engagement. We map the request's description, priority, and estimated value to Twenty's Opportunity name, stage, and amount fields. Recurring service requests map to Opportunity records with a custom recurrence flag.

Each TSP Work Order contains line items, labor estimates, and status. We map the work order header to a Twenty Opportunity record capturing the service type, estimated amount, and stage. Individual line items and labor entries become Twenty Tasks linked to that Opportunity, preserving the item-level detail that drives service billing.

TSP scheduling records — which technician is assigned, when, and at which location — map to Twenty Tasks with due dates, assignees (matched to Workspace Members by email), and Notes capturing dispatch context. Completed schedule entries retain their original timestamps as a custom datetime field for historical reporting.

TSP technicians are matched by email address to Twenty Workspace Members. If a TSP technician has no corresponding Twenty user, we flag the record for admin action — either inviting the technician to Twenty or reassigning their work orders to an existing Workspace Member before migration.

TSP time entries (clock-in, clock-out, duration) have no native Twenty equivalent. We migrate these as Tasks with custom duration fields (Time_Entry_Hours__c, Clock_In__c, Clock_Out__c) linked to the parent Work Order Opportunity. The task name reflects the service performed; the duration fields preserve billable hour data for QuickBooks sync reconstruction.

TSP tracks equipment at each service location (make, model, serial number, service history). This becomes a Twenty Custom Object named Equipment with fields: name, serialNumber, make, model, serviceLocationId (relation to Company), and lastServiceDate. Equipment is linked to the relevant Service Location Company record.

TSP invoicing lives inside its QuickBooks integration. We do not migrate invoice records — those remain in QuickBooks. Instead, we link the migrated TSP invoice number as a custom read-only field (Original_Invoice_Number__c) on the relevant Opportunity record so teams can cross-reference billing history via QuickBooks.

TSP's sync relationship with QuickBooks — customer IDs, invoice IDs, chart-of-accounts mappings — has no direct Twenty equivalent. We preserve the QuickBooks customer reference ID as a custom field (QB_Customer_Ref__c) on the Company record for reconnection after migration. During post-migration setup, your team can map this reference ID to QuickBooks via a third-party integration, ensuring that new transactions stay synchronized across both platforms.

TSP work order notes migrate as Twenty Notes on the linked Opportunity record. File attachments (photos, signed forms) are downloaded and re-uploaded via Twenty's file storage, then linked to the parent Opportunity record. All attachments retain their original file names and timestamps, which are stored in custom metadata fields to preserve audit trails and facilitate future reference.

TSP setups for specific trades (pool chemistry readings, HVAC refrigerant levels, lawn treatment zones) add industry-specific fields. These map to either custom fields on the relevant object or a Custom Object — we audit the TSP schema before migration and present the mapping plan for admin approval.