Migrate from Service Suite FSM to Twenty CRM

Service Suite FSM customers map to Twenty CRM Companies. Customer addresses, contact information, and billing details consolidate into Twenty's Company record. When a Service Suite FSM customer has multiple service locations, each location can migrate as a separate Company record linked by a parent-company relation in Twenty.

Service Suite FSM contact records map 1:1 to Twenty CRM People. Each contact's name, email, phone, job title, and role transfer directly. The contact's primary customer link becomes the Person's companyId relation to the corresponding Twenty Company record. Additional FSM fields such as contact type and department are preserved as custom fields, and the original FSM contact ID is stored in a custom Source_System_ID__c field for traceability.

Service Suite FSM work orders map to Twenty Opportunities if teams track jobs as deals with stage progression. If FSM work orders have FSM-specific statuses (dispatched, in-progress, completed, invoiced) that do not map to standard opportunity stages, we create a custom WorkOrder object in Twenty with Stage pick-list mirroring FSM statuses and relations to Person, Company, and WorkspaceMember records.

FSM work order statuses map value-by-value to Twenty opportunity stages or a custom pick-list. Common FSM statuses (Scheduled, En Route, In Progress, Completed, Cancelled) map to corresponding stage names in Twenty. Stage-entered timestamps preserve original FSM status-change dates as custom datetime fields.

Service Suite FSM technician records map to Twenty CRM workspace members. Technician skills, certifications, and service regions migrate as custom fields on the WorkspaceMember record. Users must be invited and accept before records reference them as assignees; we flag unresolved technicians before migration.

Service Suite FSM assets—installed equipment linked to customers with serial numbers, warranty dates, and service history—require a custom Asset object in Twenty. The custom object includes fields for customer link (companyId), location, serial number, warranty expiry, and asset type. Service history attaches as related Task records.

Service Suite FSM tasks map directly to Twenty CRM Tasks. Task title, description, due date, assignee (workspace member), and status transfer. Tasks linked to work orders relate to the corresponding Opportunity or custom WorkOrder record in Twenty via a relation field.

FSM scheduling and dispatch assignments—technician-to-job mappings with time windows and route data—migrate as Twenty Tasks with custom datetime fields for scheduled start/end and a relation to the assigned WorkspaceMember. Route optimization data not natively supported in Twenty is preserved as a custom text field.

FSM service history entries (completed jobs, maintenance visits, parts used) migrate as completed Tasks related to the corresponding Asset__c and Opportunity records in Twenty. Original completion timestamps and technician assignment are preserved for service reporting continuity. The Task title reflects the service type (e.g., ‘Preventive Maintenance’ or ‘Repair’), the description captures notes and parts consumed, and fields store service type, work order reference, and skill used, ensuring audit trail.

Service Suite FSM custom objects created for FSM-specific modules (e.g., inventory items, parts catalogs, certification records) map 1:1 to Twenty custom objects. Custom object relationships in Service Suite FSM that use N:N associations need junction objects in Twenty; we surface these in the pre-migration mapping plan.

FSM file attachments on work orders, assets, or customers re-upload to Twenty as Notes with attached files. File size limits apply (Twenty's import size constraints); large files may require chunking or external storage links. Inline images in notes are downloaded and rehosted.

Service Suite FSM workflow rules for scheduling triggers, dispatch logic, and automated notifications do not have a direct equivalent in Twenty CRM. Twenty's workflow builder supports basic automation but lacks FSM-specific sequencing. We export workflow definitions as a rebuild reference document for your team to recreate in Twenty's Settings → Workflows.