Migrate from Service Autopilot to Twenty CRM

Service Autopilot Clients (individuals with contact details, addresses, and service history) map directly to Twenty People records. Each Client's email, phone, and address transfer as standard People fields. Original create date is preserved as a custom datetime field since Twenty's CreatedAt is set at migration time.

Service Autopilot's optional CRM Company records map to Twenty Companies. If your Service Autopilot plan stores business account data separately from service-location Properties, the Company record becomes a Twenty Company with name, domain, and industry fields. Company hierarchies (parent/child) map to the Twenty Companies relation field.

Service Autopilot Leads (prospective clients with lead-specific fields like Lead Source, Lead Status, Estimated Revenue) map to Twenty People. Lead-specific fields migrate as custom fields on the People record. A Lead_Status__c custom pick-list field preserves the source stage value for reporting continuity in Twenty.

Service Autopilot Properties (service locations with addresses, property measurements, GPS coordinates, and photos) are a field-service concept with no direct Twenty CRM equivalent. Each Property becomes a Twenty Company record with address fields populated from the Property address, plus custom fields for property measurements and GPS latitude/longitude. Properties linked to a Client map via the Company → People relation.

Service Autopilot Jobs (scheduled work orders linked to a Client and Property, with status, assigned employee, scheduled date, and service details) map to Twenty Opportunities. Job Name becomes Opportunity name. Job status (Scheduled, In Progress, Completed, Cancelled) maps to a custom Opportunity stage field. The linked Client and Property become the Opportunity's linked People and Company via Twenty's relation fields.

Service Autopilot Job Assignments (linking a Job to a specific Employee/technician, with assignment date and status) merge into the Twenty Opportunity record as a custom Assigned_Technician__c field pointing to the Twenty Workspace Member. Individual task-level assignments (e.g., sub-tasks within a multi-stop job) create separate Tasks linked to the Opportunity.

Service Autopilot Invoices (line items, amounts, status, due date, and linked Client/Job) become custom fields on the related Twenty Opportunity: Invoice_Number__c, Invoice_Amount__c, Invoice_Status__c, and Invoice_Due_Date__c. The full invoice detail text migrates as a Note attached to the Opportunity. Invoice history is preserved for financial reporting even though Twenty has no native billing module.

Service Autopilot Payment records (amount paid, payment method, payment date, linked Invoice and Client) become Notes attached to the corresponding Opportunity or Company record. Payment method (credit card, ACH, cash) and transaction status are captured as text in the Note body for reference. We do not recreate payment processing history as a financial object since Twenty lacks a native payments module.

Service Autopilot Employees (technicians, dispatchers, admin staff) resolve to Twenty Workspace Members by email match. Employee fields including name, role, compensation type (Hourly vs. Salary), and labor burden rate transfer as custom fields on the Workspace Member record for job-costing continuity. Employees without an email in Twenty are flagged before migration for manual invitation.

Every custom field defined in Service Autopilot under Settings → Custom Fields must be recreated as a custom field in Twenty under Settings → Data Model before import. Field type mapping: Service Autopilot Text, Number, Date, and Select types map directly to Twenty equivalents. Multi-select fields map to Twenty multi-select. Relation fields in Service Autopilot map to Twenty relation fields. We deliver a custom field creation checklist as part of the pre-migration plan so your Twenty workspace is ready before data lands.

Service Autopilot Sequences (rule → trigger → action chains driving automated client communications, lead follow-ups, and job-triggered SMS/email) have no equivalent in Twenty CRM's workflow model. The sequence definitions must be manually rebuilt in Twenty's Workflow builder. We export your Service Autopilot sequence definitions as a structured reference document for your Twenty admin to use during the rebuild phase.

Service Autopilot file attachments on Jobs, Clients, and Properties (photos, signed documents, measurement files) are downloaded and re-uploaded as Note attachments in Twenty linked to the corresponding People, Company, or Opportunity record. File size limits on Twenty's file storage apply. Inline images in notes are extracted, downloaded locally, and re-hosted as Note attachments.