Migrate from Dynamics 365 Field Service to Twenty CRM

Work orders map to Opportunities in Twenty with the work order number as Opportunity name, total amount from price calculation, and booking status (Scheduled, In Progress, Completed, Cancelled) as a custom select field. Original work order created-on and resolved-on timestamps migrate as custom datetime fields to preserve service timeline for reporting continuity.

Bookable resources map to People records in Twenty, with the resource name as the person's display name and email as the primary identifier. Resource type (User, Contact, Account, Equipment, Generic) migrates as a custom select field on the People record. For User-type resources, email matching against Twenty workspace members resolves ownership automatically.

Individual bookings attach to Twenty Tasks linked to the relevant Opportunity (work order) and the assigned People record (bookable resource). Booking start/end times become task due dates, and booking status (Held, Committed, Cancelled) maps to task completion status. Multiple bookings for the same work order generate multiple Tasks with resource attribution.

Customer assets require a custom Field Asset object in Twenty, linked to the related Company record. Asset name, serial number, product, installation date, and parent asset hierarchy migrate as custom fields on the Field Asset object. Installed products on the asset become linked records or custom fields depending on the relationship complexity.

Work order incidents migrate as Notes attached to the related Opportunity (work order). Incident type, symptom, cause, and resolution text populate the Note body. Primary incident flag migrates as a custom field on the Note if multiple incidents exist per work order.

Service tasks on a work order become Tasks linked to the Opportunity. Task type (field inspection, testing, repair) maps to a custom task-type field. Duration and actual duration migrate as numeric fields. Nested task hierarchies in Dynamics flatten to a flat task list with a parent-task custom field for structure preservation.

Service agreements require a custom Service Agreement object in Twenty linked to the Company. Agreement name, start/end dates, service frequency, and invoicing method migrate as custom fields. Active/inactive status preserves the agreement lifecycle. Recurring work order generation rules do not migrate — those scheduling patterns must be rebuilt via Twenty's workflow builder or API-driven automation.

Products added to work orders migrate as a custom field group on the Opportunity: product name, quantity, unit price, and line total. Dynamics 365 product inventory data (warehouse, stock quantity) does not map to Twenty's flat data model — inventory tracking requires a separate inventory management tool or custom object implementation.

The parent account in Dynamics 365 Field Service maps directly to a Company record in Twenty. Account name, address, industry, and number of employees map to the corresponding Twenty Company fields. For organizations with nested account hierarchies, parentId resolves to the top-level Company in Twenty's flat structure.

The primary customer contact on a Dynamics 365 work order maps to a People record in Twenty, linked to the corresponding Company via companyId. Contact name, email, phone, and job title migrate as standard People fields. Secondary contacts on the same work order attach as additional linked People records.

Work order type (Maintenance, Inspection, Installation, Emergency) migrates as a custom select field on the Opportunity. Stage probability and forecast category are not natively set by this field in Twenty — those must be configured manually or via workflow based on work order type and booking status.

Priority levels (Critical, High, Normal, Low) map to a custom Priority__c select field on the Opportunity. Each Dynamics 365 priority value maps to the corresponding Twenty value. Priority-based SLA timers in Dynamics do not have a direct equivalent in Twenty — those rules must be rebuilt as workflow triggers or external automation.