Migrate from Accruent Vx Field to Twenty CRM

Billable or recurring service contracts from Vx Field migrate as Opportunities in Twenty. The Work Order number becomes the Opportunity name, the service type or contract value maps to Amount, and the work order status (Open, In Progress, Complete) maps to a corresponding Opportunity stage. For one-off service records without revenue, Tasks are the preferred destination.

Non-billable service records from Vx Field route to Twenty Tasks. FlitStack maps the work order status to Task status (Open → Todo, Complete → Done), preserves the original scheduled date as the Task due date, and links the Task to the corresponding Company or People record via the service location field.

Vx Field assets with customer locations or installed equipment migrate as Companies in Twenty. Asset name maps to Company name, the asset's site or location address maps to the Company address fields, and asset category or type maps to the industry field. Parent-child asset hierarchies resolve to Company hierarchies via the Parent Account relationship.

Equipment-specific asset records that are not customer accounts migrate as a custom 'Equipment' or 'Asset' object in Twenty. The custom object stores serial number, model, warranty status, and last service date. This requires pre-creating the custom object in Twenty's Data Model before migration runs.

Vx Field accounts representing end customers map 1:1 to Twenty Companies. Company name, address, phone, and industry map directly with no transformation. The account's primary contact from Vx Field becomes a separate People record linked via the companyId field. The original Vx Field account ID is preserved as source_system_id for audit trail and reconciliation purposes.

Vx Field technicians are internal resources without counterparts in a CRM context. FlitStack maps them as inactive or archived People records for service history attribution purposes, but they do not function as contacts in Twenty. Assignee and dispatch data from work orders preserves the technician name in the service history Notes.

Vx Field contacts attached to accounts migrate as Twenty People records. Name, email, phone, and job title map directly. The people record links to the corresponding Company via companyId. Multiple contacts per account collapse to individual People records with the same companyId.

Work order completion summaries, technician notes, and parts consumed from Vx Field attach as Notes in Twenty. Notes link to the Company record (for customer-level history) or the Opportunity record (for deal-specific service records). Original timestamps and technician names are preserved in the Note body or as metadata fields.

Parts and line items from Vx Field work orders have no direct Twenty equivalent. FlitStack captures this data in a Note attached to the corresponding Opportunity or Task, preserving part number, quantity, and cost. If parts tracking is critical, a custom 'Service Line Item' object can be created in Twenty before migration.

Vx Field scheduling and dispatch data (technician assignments, route order, time windows) is a field-service-native concept with no CRM equivalent. FlitStack preserves the scheduled date as a Task due date and the assigned technician name in a custom field, but route optimization and dispatch logic must be rebuilt in Twenty's calendar or a dedicated scheduling tool.

Vx Field custom fields on work orders migrate as custom fields on the corresponding Twenty object. Custom fields on billable work orders attach to Opportunity; custom fields on non-billable records attach to Task. All custom fields must exist in Twenty's Data Model before import — FlitStack delivers a field creation plan as part of the migration preparation.

File attachments from Vx Field work orders (photos, signed forms, invoices) do not migrate as native Twenty files. FlitStack downloads attachments and re-uploads them as Notes with a link reference, or exports them to a connected storage location and embeds the URL in the corresponding Company or Opportunity record.