Migrate from Accruent Vx Field to monday CRM

Accruent work orders map 1:1 to Monday deal items. Each work order becomes one board item in the Deals board. Status, priority, and assigned technician map to Monday's column types. Original work-order ID is stored as a custom text column (Work_Order_ID__c equivalent) for traceability and delta-run de-duplication.

Accruent status codes (New, Scheduled, In Progress, On Hold, Completed, Cancelled) map value-by-value to Monday status column options. We create the Monday status options to match Accruent's exact codes so the pipeline view reflects the original service lifecycle stages accurately and operations teams can immediately use familiar status labels without renaming or collapsing any of the original workflow states.

Accruent priority values (Emergency, High, Medium, Low) map to Monday priority column values. These must be created as a Monday label/dropdown column since Monday's native priority column has fixed values that may not match FSM priority tiers. We define the exact label options to preserve the full range of priority classifications from Accruent without any loss of granularity in how work orders are categorized by urgency.

Accruent customers map directly to Monday CRM Organizations. Site-level addresses on Accruent customers become Address columns on the Organization record. If a customer has multiple service sites, each site is evaluated as a separate Organization or as a location tag on the primary Organization depending on your reporting requirements.

Accruent contact records on work orders map to Monday People linked to the Organization. Email address, phone number, and job title transfer directly as discrete fields. When an Accruent customer account has multiple contacts associated with it, each contact becomes a separate Monday People item and is linked to the same parent Organization, preserving the full contact roster for each customer account within Monday's organizational structure.

Accruent assets migrate as items in a separate Monday Assets board linked to the Organization via a link/relation column. Asset make, model, serial number, and install date map to custom columns. The parent-asset relationship is stored as a lookup text column referencing the parent item ID — Monday's flat item model does not support a native asset hierarchy tree.

Accruent's parent-asset tree is flattened into a parent-asset reference column on the child item. We preserve the hierarchy depth as a text field (e.g., 'Level 2 — HVAC Unit → Zone Controller') for reporting. True hierarchical rollup queries are not available in Monday and must be handled in a separate reporting layer if needed.

Each Accruent service history log entry (one visit, one technician, one date) becomes a subitem on the work order item or is posted as an Update with the visit date, technician name, and notes. Parts used during the visit migrate as a text entry or as subitem columns if the Monday plan supports subitems.

Accruent technicians are resolved by email match to Monday workspace members and assigned as item owners. Unmatched technicians are flagged before migration — your team either creates the Monday user first or assigns their work orders to a fallback owner. Accruent skill certifications and dispatch certifications cannot be mapped to Monday fields and are preserved as a custom text column for reference.

If Accruent tracks a formal parts inventory with stock levels, we create a Monday Inventory board with item-level stock columns. Work order parts consumption becomes a text field on the work-order item listing part names and quantities used, since Monday does not have a native parts-consumption ledger.

Accruent custom fields unique to your FSM setup — such as contract type, SLA tier, or technician certification requirements — are created as custom columns on the relevant Monday board. Multi-select custom fields in Accruent are stored as comma-separated text in Monday since Monday does not support native multi-select columns at the item level.