Migrate from Accruent Vx Field to Odoo CRM

Accruent Work Orders are the primary operational entity — carrying job type, status, priority, scheduling windows, and assigned technician(s) — and must translate to Odoo CRM Opportunities. FSM-specific fields (scheduling priority, preferred time windows) are preserved as Odoo custom fields (x_work_order_number, x_scheduling_priority, x_preferred_start, x_preferred_end). Work order status maps to Opportunity stage via a value-by-value mapping table.

Accruent Work Order Type (e.g., Preventive Maintenance, Emergency Repair, Installation) has no direct Odoo CRM equivalent. Migrates as a custom Char field on crm.lead. If your Odoo setup uses multiple sales teams or tags to segment service types, FlitStack surfaces this in the mapping plan so your admin can configure tag-based filtering in Odoo.

Accruent customer accounts map 1:1 to Odoo Partner records. Site-level and regional location hierarchy data is stored in custom fields on the partner record (x_location_region, x_site_name, x_building, x_floor). Multi-level hierarchy decomposition is applied during the transform step — FlitStack flattens the location path into a custom Char field for Odoo display.

Accruent contacts at a customer site map to Odoo Partner records of type 'contact', linked to the parent customer Partner record via the partner_id field. Phone, email, mobile, job title, and address fields migrate directly. Contacts without an email are flagged in the validation report for manual review in Odoo.

Accruent technicians represent field resources with skills and availability. In Odoo CRM, technicians can map to internal Users (for opportunity assignment) or Contacts (for customer-facing reference). FlitStack matches by email — if a technician email exists in Odoo's user list, records are assigned to that user; otherwise they are stored as a related Contact with the technician name in a custom field (x_technician_name). Multi-technician assignments on a single work order are concatenated into x_technician_list.

Accruent asset hierarchies (equipment with parent-child relationships, attributes, condition data) have no native Odoo equivalent. The equipment name and key attributes migrate as an Odoo Product record; the parent-child hierarchy path is stored as a custom Char field (x_asset_hierarchy_path, e.g., 'Site-A / Building-2 / HVAC-Unit-4'). Odoo's inventory module handles stock tracking if parts consumption is relevant, but the hierarchical asset tree is reference-only in the CRM.

Accruent locations are hierarchical (Region → Site → Building → Floor), each with address and geo-coordinates. Odoo Partner records hold a single address. FlitStack splits each hierarchy level into a separate custom Char field on the partner record. The primary address (street, city, state, zip, country) maps directly to Odoo's standard address fields. Latitude/longitude are stored in custom Decimal fields (x_latitude, x_longitude) for future Odoo map integration.

Accruent logs work order status changes, technician notes, and field observations as an activity history. These migrate as Odoo mail.activity records linked to the target opportunity, with the original timestamp, author (technician), and body text preserved. Timestamps map to Odoo's date_deadline and create_date fields. High-volume activity logs are batched to avoid Odoo mail.thread performance degradation.

Accruent file attachments on work orders (photos, PDFs, inspection reports) are downloaded and re-uploaded as Odoo ir.attachment records linked to the target opportunity. File size limits apply per Odoo's configuration. Inline images in notes are extracted, rehosted in Odoo's filestore, and re-embedded in the chatter thread.

Accruent custom properties on work orders (user-defined fields beyond the standard schema) require pre-creation as custom fields in Odoo before migration. FlitStack generates a custom field creation manifest (field name, type, pick-list values if applicable) from the Accruent schema export. Your Odoo admin creates the fields in Settings > Technical > Database Structure > Models, then FlitStack runs the data load against the newly created fields.

Accruent intelligent scheduling rules and dispatch preferences (e.g., technician skill matching, zone-based routing, priority escalation) have no Odoo CRM equivalent. These are exported as custom fields (x_scheduling_priority, x_dispatch_zone, x_sla_target_date) and provided as a rebuild reference document for your Odoo admin to reconstruct using Odoo Studio automation rules or a custom FSM module.

Accruent integrations with ERP, accounting, parts procurement, or IoT monitoring systems do not transfer to Odoo. Third-party connections must be rebuilt — Odoo's app store has native connectors for common ERP and accounting tools. FlitStack exports integration endpoint documentation from Accruent as a reference for your integration team.