Migrate from ServiceTitan to Twenty CRM

ServiceTitan customer records map directly to Twenty's People object. Each customer has a primary name, email, phone, and address fields that map to Twenty's standard contact fields. ServiceTitan allows multiple contact points per customer; Twenty stores one People record per individual contact.

ServiceTitan service locations represent physical addresses where jobs occur — distinct from the customer record itself. These map to Twenty's Company object, with the location address as the company address and the customer name stored for reference. ServiceTitan allows multiple locations per customer; Twenty's Company object represents each location as a separate account record.

ServiceTitan jobs have no direct Twenty CRM equivalent. We create a Job custom object in Twenty with fields for job type, status, scheduled date, assigned technician, and service location link. Job history and timestamps migrate as records in this custom object. The dispatch board and route optimization logic cannot migrate and must be designed as a manual process in Twenty.

ServiceTitan invoices carry line items, tax, payments, and QuickBooks sync status. Twenty has no native invoicing module. We create an Invoice custom object capturing invoice number, date, total amount, status (paid/unpaid/void), and a relation to the service location Company. Payment history and invoice attachments migrate as file links or notes.

ServiceTitan custom fields on customer records — such as preferred technician, customer type, or membership status — require corresponding custom fields in Twenty's People object. We identify all active custom fields during audit, create them in Twenty's Settings → Data Model before import, then map values during the migration run.

ServiceTitan allows custom fields on job records for trade-specific data like equipment model, warranty status, or permit number. These map to custom fields on the Job custom object we create in Twenty. Every custom field must exist in Twenty before the migration CSV is uploaded — we surface this as a pre-migration setup step.

ServiceTitan Pricebook entries store service items, parts, labor rates, and pricing tiers. Twenty has no native product catalog. We create a Product custom object with fields for name, SKU, unit price, and category. Pricing tiers and discount rules require manual rebuild in Twenty or external pricing tools.

ServiceTitan technician and employee records hold certifications, service areas, and work schedules. Twenty's WorkspaceMember object represents users who access the CRM. Technician-specific attributes (trade certifications, service zones) must be stored as custom fields on the WorkspaceMember record or in a separate Technicians custom object.

ServiceTitan marketing campaigns track lead sources and campaign performance tied to job referrals. Twenty has no native campaign object. We create a Campaign custom object capturing campaign name, type, start/end dates, and target lead count. Campaign membership (which customers came from which campaign) migrates as a custom field on the People record.

ServiceTitan service agreements and membership programs (annual maintenance plans, prepaid service tiers) have no Twenty CRM equivalent. We create a Membership custom object linked to the People record, storing membership type, start date, renewal date, and status. Membership benefits and auto-renewal logic must be rebuilt as a manual process or external tool.

ServiceTitan files attached to customers, locations, or jobs (photos, signed documents, equipment manuals) migrate as Twenty Notes attached to the corresponding People or Company record. We download the files, re-upload to Twenty's file storage, and link them to the parent record. File size limits and inline image handling apply.

ServiceTitan call notes, communication history, and internal messages map to Twenty Notes for free-form text or Tasks for action items with due dates and assignees. Original timestamps and created-by-user references preserve audit trails. Call disposition codes become Task status or a custom select field on the Task.