Migrate from Accruent Vx Field to HubSpot

Vx Field work orders map 1:1 to HubSpot Tickets. Work order status (Open, Dispatched, In Progress, Closed) maps to HubSpot Ticket status and pipeline stage values. Priority, description, and timestamps carry over. The Vx Field work order number is stored as a custom text field on the HubSpot Ticket.

Parts used on a work order are not native HubSpot Ticket fields. FlitStack serializes each parts-used entry (part number, quantity, cost) as a JSON array stored in a custom multi-line text property on the Ticket. Your team can display this in a custom ticket card or expand it via HubSpot's custom card API.

Vx Field customer accounts map to HubSpot Companies. Service locations associated with an account map to Company properties (address fields, site name). Primary contact at the location maps to a HubSpot Contact linked via the Company. N:N customer-to-location relationships in Vx Field translate to one primary Company record with additional Company associations.

Vx Field assets (equipment at customer locations) map to a HubSpot custom object named 'Asset'. Parent-child asset hierarchies are preserved using a self-referential parent_asset_id field on the Asset custom object. Asset make, model, serial number, install date, and warranty expiration migrate as custom properties on the Asset record.

Historical work orders performed on an asset are extracted as Note records and associated to the Asset custom object in HubSpot. Original work order date, technician, and resolution notes are preserved. This gives service teams a complete maintenance history attached to the equipment record.

Vx Field inventory records (part number, description, warehouse location, quantity on hand, reorder point) map to a HubSpot custom object named 'Inventory Item'. Warehouse location and bin information migrate as text properties. Current stock quantity is a number field; replenishment alerts are surfaced as Workflow triggers in HubSpot.

Vx Field technician records map to a HubSpot custom object named 'Technician' for reference data (certifications, territories, skills). The technician's HubSpot login is matched by email to the HubSpot User record so Tickets can be assigned to the correct user. Technicians without HubSpot accounts are flagged for team provisioning before migration.

Vx Field route definitions (stop sequence, estimated drive time, territory) map to a HubSpot custom object named 'Route' for record-keeping. Active route-optimization logic cannot migrate — it must be rebuilt using HubSpot Workflows with geo-conditions or a third-party routing app. We preserve route names, assigned technicians, and stop lists as static reference data.

Vx Field file attachments on work orders (photos, PDFs, signatures) are downloaded and re-uploaded to HubSpot Files. Each file is linked to the corresponding Ticket or Asset record via HubSpot's object association model. File size limits apply (HubSpot default 25MB per file; inline images in notes are extracted and re-hosted).

Vx Field invoice records (line items, totals, payment status) map to a HubSpot custom object named 'Service Invoice' associated to the Ticket. Invoice amounts and payment status are preserved as custom fields. HubSpot does not natively handle accounts-receivable; integration with QuickBooks or Stripe is recommended post-migration.

Any custom fields defined on Vx Field work orders (e.g., custom pick-lists, dispatch region codes, SLA timers) are reviewed by FlitStack. Standard types (text, number, date, pick-list) are created as HubSpot custom properties on the Ticket object. Complex FSM-specific field types that have no HubSpot equivalent are preserved as custom text fields for reference.

Vx Field supplier records (vendor name, contact, parts supplied) map to a HubSpot custom object named 'Supplier'. This is a lightweight reference object — not a HubSpot native Company, since vendors are not customers. Supplier records can be associated to Inventory Item records for parts-sourcing traceability.