Migrate from ServiceMax to Twenty CRM

ServiceMax Accounts map directly to Twenty Companies. The Account Name, Website, Industry, NumberOfEmployees, and AnnualRevenue fields translate to Twenty's name, domain, industry, employees, and revenue fields. Address fields (Street, City, State, PostalCode, Country) on the Account map to Twenty's address compound field on the Company record.

ServiceMax standard Contacts map directly to Twenty People records. Core fields including FirstName, LastName, Email, Phone, MobilePhone, and job Title migrate without transformation. The Contact's AccountId lookup resolves to a Company ID in Twenty, establishing the Person-to-Company relationship so each contact is properly linked to its parent organization record.

Work Orders are the primary migration object. ServiceMax work orders carry SVMXC__Order_Status__c, SVMXC__Priority__c, SVMXC__Billing_Type__c, SVMXC__Scheduled_Date__c, SVMXC__Completion_Date__c, SVMXC__Work_Performed__c, and SVMXC__City__c/State__c/Country__c. None of these map to native Twenty fields — they all require custom field creation on a custom WorkOrder__c object before migration data lands.

The Work Order's AccountId (service location / customer account) resolves to a Twenty Company record by Account Name match. If no matching Company exists in Twenty, FlitStack creates one from the service address fields on the Work Order before migrating the Work Order itself.

The Work Order's ContactId field resolves to a Twenty Person record by performing an email address match against the migrated Person list. Any contacts that fail to match are flagged in a pre-flight report for manual review; the Work Order itself is not blocked from migrating, but the unresolved Person link is recorded in the migration audit log for post-migration cleanup.

ServiceMax Installed Products (field service assets) migrate to a custom Asset__c object in Twenty. Custom fields capture SVMXC__Serial_Number__c, SVMXC__Status__c, SVMXC__Warranty_Expiration__c, SVMXC__Installation_Date__c, and the linked AccountId. Entitlement and warranty checks that ServiceMax performs automatically must be rebuilt as custom logic in Twenty.

Work Order Line Items (parts consumed, labor lines) migrate to a custom WorkOrderLineItem__c object linked to the WorkOrder__c. SVMXC__Line_Status__c, SVMXC__Quantity__c, and SVMXC__Product__c product name require custom field creation. Each line item links to the parent Work Order via a relation field.

Service Contracts migrate to a custom Contract__c object. SVMXC__Start_Date__c, SVMXC__End_Date__c, SVMXC__Contract_Value__c, and SVMXC__Status__c become custom fields. The contract-to-asset entitlement linkage that ServiceMax uses for warranty validation does not exist in Twenty and must be rebuilt using custom fields and workflow conditions.

ServiceMax-integrated Cases map to Twenty Tasks using a transformed mapping approach. Key fields including Case Number, Subject, Description, Status, and Priority translate directly to corresponding task attributes. Any parent link referencing an associated Work Order or Company record is preserved as a custom relation field on the Task object to maintain the original contextual relationship.

ServiceMax product catalog entries (Product2 records enhanced with SVMXC__ fields) migrate to a custom Product__c object in Twenty. Standard fields like Product Name, ProductCode, Description, and Family translate to custom text and select fields. Inventory levels tracked in SVMXC__Inventory_Location__c require a separate custom inventory object since Twenty lacks native inventory tracking.

ServiceMax activity history encompassing calls, emails, meetings, and notes logged on Work Orders migrates directly to Twenty Tasks. The Subject, Description, Status, ActivityDate, and WhoId/WhatId link fields transfer without transformation. The WhatId reference (Work Order link) resolves to the migrated WorkOrder__c record ID to preserve the activity's association with the parent work order.

ServiceMax technicians who are also Salesforce users match to Twenty Workspace Members by email. Non-user technician records (created as SVMXC__Resource__c without a Salesforce UserId) must be imported as Contacts first, then manually promoted to Workspace Members in Twenty's Settings → Members panel.

Preventive Maintenance Process definitions are not migrated directly but exported as JSON for manual rebuilding. The exported definitions include frequency rules, asset scope parameters, and task templates that define each process. FlitStack maps the asset list and frequency rules to a custom MaintenanceRule__c object, while the automated trigger logic must be reconstructed by your admin using Twenty's workflow builder.

ServiceMax file attachments associated with Work Orders, Installed Products, and Contacts are downloaded from Salesforce storage and re-uploaded to Twenty's file storage system. Each file—ranging from PDF inspection reports and equipment photos to signed service documents—is attached to its corresponding migrated record (WorkOrder__c, Asset__c, or Person) to preserve documentation continuity.