Migrate from Salesforce Field Service to Twenty CRM

Salesforce Account maps directly to Twenty Company. Account.Name becomes Company.name, Account.Website maps to domainUrl, and Account.Industry maps to industry. Multi-address accounts collapse to one primary address in Twenty's single address field, with secondary addresses preserved as custom fields if needed. Parent Account hierarchies map via Company.parentId where available.

Salesforce Contact maps to Twenty People with direct field-name equivalents for firstName, lastName, email, and phone. Contact.Title maps to jobTitle. The Contact's primary AccountId becomes People.companyId — the company must be imported before the contact so the foreign key resolves. N:N contact-to-account relationships in Salesforce are not represented in Twenty's standard People model; secondary company links require a custom junction object.

Salesforce WorkOrder has no native equivalent in Twenty — we create a custom Work_Order__c object in Twenty's Settings → Data Model. Fields map: WorkOrder.Status to Work_Order__c.status (value mapping: In Progress→In Progress, Completed→Closed, etc.), WorkOrder.Priority to priority picklist, WorkOrder.Description to description, WorkOrder.SlaStartDate/WoDate to scheduledDate. OwnerId (technician User) resolves to Twenty workspace member by email match.

ServiceAppointment maps to a custom Service_Appointment__c object linked to Work_Order__c. Appointment status (FSM states: Scheduled, Dispatched, In Progress, Completed, Cancelled) maps to a custom status__c pick-list. Schedules and FSL window times migrate to scheduledStartDate__c and scheduledEndDate__c datetime fields. The parent WorkOrderId becomes a relation field in Twenty's custom object.

WorkOrderLineItem (parts and labor on a work order) maps to a custom Line_Item__c object with a relation to Work_Order__c. LineItem.Quantity maps to quantity__c, UnitCost to unitCost__c, and LineItem.TotalPrice to totalPrice__c. Product2 reference in Salesforce becomes a text Product__c field or a custom Product relation in Twenty, depending on whether a Products custom object is created.

Salesforce Asset (installed products linked to accounts and contacts) maps to a custom Asset__c object in Twenty. Asset.Name, SerialNumber, InstallDate, Status, and Product2 reference all migrate to corresponding fields. Asset.AccountId becomes Asset__c.accountId relation. Asset.ContactId becomes an optional Asset__c.contactId relation. The asset's relationship to WorkOrderLineItem requires a custom junction design in Twenty since there is no native many-to-many link.

Salesforce Skill (technician certifications and proficiency levels) maps to a custom Skill__c object in Twenty. Skill.SkillName maps to name__c. If Salesforce stores skill levels as separate pick-list values, these migrate to a proficiency__c pick-list on the custom object. Linking Skills to People (technicians) requires a custom Skill_Assignment__c junction object in Twenty, since Twenty's standard relation model does not support many-to-many person-to-skill links natively.

Salesforce ServiceContract (warranty and SLA terms) maps to a custom Service_Contract__c object linked to Account and Asset. Contract.StartDate, EndDate, and Status migrate to contractStartDate__c, contractEndDate__c, and status__c. Line items (ContractLineItem) on the contract migrate to separate contractLineItem__c records linked to the contract, capturing covered products and pricing terms.

Salesforce Entitlement (service entitlement linked to contact/account with business hours) maps to a custom Entitlement__c object in Twenty. Entitlement.Name, Status, StartDate, and EndDate migrate to corresponding fields. The BusinessHours reference migrates as businessHours__c text. Entitlement.IsPerIncident and remaining service credits migrate to a custom remainingIncidents__c number field. Since Twenty has no native BusinessHours object, service-level response windows are stored as text or recreated as workflow triggers.

Salesforce Users who own WorkOrders or ServiceAppointments are resolved by email match against Twenty workspace members. Unmatched owners are flagged before migration — your team either invites them to Twenty first or assigns records to a fallback member. Active/Inactive Salesforce User status does not translate to Twenty directly; inactive users in Salesforce are preserved as name/email in an ownerAudit__c field on migrated records but do not become active Twenty members.

Work Order StatusHistory (stage-transition audit log) is not a standard child object in Salesforce Field Service — it is queryable via WorkOrderHistory. We extract the most recent status transitions and load them as Task records in Twenty linked to the Work_Order__c custom object, preserving original transition timestamps and the prior/new status values as task description content.

Salesforce Files attached to WorkOrders, ServiceAppointments, and Assets (photos, signed forms, PDFs) do not migrate automatically. We export them to a ZIP archive and provide a file re-upload guide for your team — Twenty's UI supports file attachment on records but requires manual re-upload or API reconstruction. Attachments on standard Salesforce objects (Contact, Account) are similarly preserved as a downloadable archive with filename-to-record mapping.