Migrate from Connect Field Service to Twenty CRM

WorkOrder maps to Twenty Opportunity. WorkOrder.Name maps to Opportunity.name. WorkOrder FS-TotalPrice (from price-list lines) maps to Opportunity.amount. WorkOrder jigsaw_address fields are flattened into custom address fields on the Opportunity. Status reason values map via a value-mapping table to Twenty Opportunity stage strings.

ServiceAppointment maps to Twenty Task. The ScheduledStart and ScheduledEnd datetimes become the Task due date. The actual work performed (from WorkOrder) is stored as a note linked to the Task. Latitude/longitude from CFS mapping is stored as custom number fields if needed.

Account maps 1:1 to Twenty Company. Account.Name maps to Company.name, Account.Address maps to the full set of Company address fields (street, city, state, postal code, country), and Account.Phone maps to Company.phone. Primary-contact links from Account to Contact are turned off during migration — instead, rely on the Contact object mapping to establish Person-to-Company relationships independently after the Contact import completes.

Contact maps to Twenty Person. FullName maps to Person.name, Email maps to Person.email, and Telephone maps to Person.phone. The Contact's parent Account is linked via the Person.companyId relation, but this linkage is established only after the Company import completes and the source_account_id foreign key is available for resolution. This dependency order ensures referential integrity across the migrated dataset.

Asset has no native equivalent in Twenty CRM. We create a custom object named 'Asset' in Twenty. Asset.Name, Product.Name, AccountId, InstallDate, and SerialNumber map to custom fields. The parent Account link is preserved as a Company relation on the custom object.

Connect Field Service's product catalog (Product2) has no native destination equivalent in Twenty's base schema. A custom object named 'Product' is created; Name, ProductCode, Description, and BasePrice map to custom fields. The Opportunity.ProductId reference becomes a relation to this custom object.

WorkOrderProduct line items (each price-list entry on a WorkOrder) map to a custom object linked to the Opportunity. Quantity, UnitAmount, and ProductName are stored as custom fields on this object, preserving the per-line pricing that Connect Field Service stores in its price-list model.

BookableResource (field technicians and dispatchers) has no native Twenty equivalent. A custom object named 'Field Resource' is created. Resource.Name, ResourceType, and IsActive map to custom fields. The WorkOrder.OwnerId / ServiceResource映射 to this custom object after users are invited to Twenty.

FSSkill (skill taxonomy used for resource-booking constraints) has no native Twenty equivalent. A custom object named 'Skill' is created with Name and Rating fields. Resource-to-Skill associations (FSSkillAssociation) are stored as junction records linking the Field Resource custom object to the Skill custom object.

Work order summary notes and internal dispatch comments stored in the WorkOrder msdyn_description field are migrated as Twenty Notes attached to the corresponding Opportunity, preserving original timestamps and the user who created the note. The note body is copied verbatim from Dynamics, and the original createdon and modifiedon timestamps are stored in custom date fields on each Note record for audit trail purposes.

Field service product associations (product used on a specific asset at a specific location) are preserved as Notes attached to the Asset custom object, since Twenty has no native asset-product relationship model. The Note body includes the product name, version or model number, and installation date extracted from the FieldServiceProduct record, providing a searchable history of which products have been deployed on each asset without requiring a custom junction object.

Resource territories (geographic regions used for dispatch optimization) are stored as a custom Territory object linked to Field Resource records. TerritoryName and Longitude/Latitude boundaries map to custom fields on the Territory object, enabling reporting on technician coverage areas in Twenty even though Twenty's native data model does not include geographic boundary definitions. Each Field Resource record references its assigned Territory via a relation field, maintaining the dispatch-team-to-region linkage from the original Dynamics configuration.