Migrate from Field Service Trakker to Twenty CRM

Field Service Trakker contacts map directly to Twenty's People object. Contact name, email, phone, and address fields align by convention. Technician-flag and service-territory properties that exist in Field Service Trakker require custom fields on the Twenty People object — we create these before migration and populate them from the corresponding source fields.

Field Service Trakker companies map to Twenty's Companies object. Company name, domain, industry, and address fields map directly. Multi-location companies in Field Service Trakker collapse to one Companies record with the service-location records handled as custom address fields or a linked custom object depending on your schema preference.

Field Service Trakker work orders translate to Twenty Opportunities with a custom 'Work Order' stage group. We add a Work_Order_Number__c custom field to preserve the original Field Service Trakker work order ID, and map work order status (Open, In Progress, Completed, Cancelled) to Opportunity stage values that you define in Twenty's pipeline setup.

Each Field Service Trakker work order status maps to a corresponding Twenty Opportunity stage value. We apply a value-by-value mapping during migration: 'Open' → 'Prospecting', 'In Progress' → 'Value Proposition', 'Completed' → 'Closed Won', 'Cancelled' → 'Closed Lost'. You specify the stage names in Twenty before migration so the mapping aligns with your pipeline view.

Field Service Trakker assigns a technician or worker to each work order. In Twenty, Workspace Members represent system users. If the technician is already a Twenty user, we link the Opportunity to that Workspace Member via the assignee field. If not, we preserve the technician name in a custom text field (Assigned_Technician__c) and surface it in your migration report for manual resolution.

Field Service Trakker work order notes migrate as Twenty Notes attached to the corresponding Opportunity. If the notes contain structured data (parts used, resolution steps), we split them into a Note record and a custom text field (Resolution_Details__c) to keep the CRM structured and filterable.

Field Service Trakker tracks parts used on work orders. Twenty has no native line-item object, so we create a custom 'Parts_Used__c' multi-select text field or a linked custom 'Parts_Used' object with a relation to Opportunity, depending on the complexity of your parts data. We assess your parts schema during discovery and recommend the approach.

Field Service Trakker stores service locations separately from customer company records. We link service addresses to the parent Company record in Twenty using Twenty's address fields. If you have multiple service locations per company, we create a custom 'Service_Location__c' object with a many-to-one relation to Companies.

Field Service Trakker custom fields — such as service-type pick-lists, priority levels, warranty-expiry dates, or equipment-serial-number fields — migrate as Twenty custom fields. Twenty supports text, number, date, select, multi-select, and relation field types. We create each custom field in Twenty's data model before migration and apply type-aware transformation where the data type differs.

Field Service Trakker file attachments on work orders re-upload to Twenty. Files attach to the corresponding Opportunity record as Twenty Files. Inline images in notes are extracted and rehosted as separate file attachments. File size limits in Twenty apply — we chunk large files and flag anything exceeding the limit for manual handling.

Field Service Trakker scheduling rules, route-optimization triggers, and dispatch automations are FSM-layer constructs with no equivalent in Twenty CRM. These do not migrate. We export your scheduling rule definitions as a structured JSON reference file so your Twenty admin or developer can rebuild the logic using Twenty's workflow builder or an external scheduling tool.