Migrate from Trade Service Pro to Twenty CRM

TSP customer records map directly to Twenty People. First name, last name, email, phone, address, and job title migrate as standard People fields. TSP customer records without an email address are flagged during validation — email is required for workspace member matching on owner resolution.

TSP company records (business accounts for which technicians perform jobs) map to Twenty Companies. Company name, domain/website, industry, employee count, and annual revenue migrate as standard Companies fields. TSP stores no native parent-company hierarchy — all company records land flat in Twenty.

TSP jobs are the core sales and service record. Migrate as Twenty Opportunities with a custom select field Job_Type__c capturing the TSP job type, and a custom select field Service_Category__c for industry-specific categories. Opportunity Amount maps from TSP job total. Close date maps from scheduled completion date. Stage name maps via value mapping to a custom Opportunity Stage pick-list.

TSP job statuses (e.g., Scheduled, In Progress, Completed, Invoiced, Cancelled) have no native equivalent in Twenty's Opportunity stages. Each TSP status maps to a custom pick-list value on a custom Opportunities__Stage field. Probability is not automatically derived — reapply forecast assumptions in Twenty after migration.

TSP work orders (line-item breakdowns of a job) have no standard Twenty equivalent. We create a Work_Order__c custom object via Twenty's Settings → Data Model before import, with fields for Work_Order_Number__c, Linked_Job_ID__c (references the Opportunities record), description, and status. Each work order record migrates as a row linked to its parent job.

TSP proposals and estimates migrate as a custom Proposal__c object. Fields include Proposal_Number__c, Linked_Job_ID__c (Opportunity lookup), total_amount__c, valid_until_date__c, and eSign_status__c (if TSP records signature state). Proposal body content migrates as a long-text field; formatting is preserved where TSP exports support it.

TSP invoices migrate as a custom Invoice__c object linked to the Opportunities record. Fields include Invoice_Number__c, invoice_date__c, total_amount__c, balance_due__c, payment_status__c (paid, partial, outstanding), and QuickBooks_ID__c for reconciliation if QB sync is rebuilt. Tax and line-item breakdowns preserved as child records of the Invoice object.

TSP pricebook entries (products, services, and inventory items) migrate as a custom Product__c object. Fields include name, category__c (from TSP categorization), unit_price__c, unit_of_measure__c, and inventory_level__c. TSP inventory status flags (in-stock, low-stock, discontinued) map to a select field on the Product record.

TSP employee timesheet records (clock in/out, job timers, break entries) migrate as a custom Timesheet__c object. Fields include employee_name__c, date__c, hours_worked__c, job_link__c (Opportunity lookup), and timer_type__c (clock, job, break). Twenty has no native timesheet or time-tracking module — this custom object provides historical record continuity.

TSP user accounts and job owners resolve to Twenty workspace members matched by email address. All TSP users must accept their Twenty workspace invitation before the migration import runs, per Twenty's constraint that owner relations require an accepted member record. Unmatched owners are flagged as exceptions — assign to a fallback owner or invite the user before migration commits.

TSP logged calls, emails, and meeting records migrate as Twenty Tasks linked to the relevant Opportunities or People record. Task Subject carries the activity type and description. Original timestamp preserved in the Task's due date or a custom created_at field. TSP does not export calendar-synced meeting data — confirm export availability per TSP account tier.

TSP notes migrate as Twenty Notes attached to the parent record (People, Companies, or Opportunities). Note body carries the full text content. TSP file attachments do not export via CSV — these must be manually re-uploaded to Twenty after migration or migrated via Twenty's GraphQL API if the files are accessible through TSP's storage layer.