Migrate from Accruent Vx Field to Microsoft Dynamics 365 Sales

Accruent customer records map directly to Dynamics 365 Sales Accounts. The customer name, primary address, and contact information translate to Account.Name, primary Address fields, and the primary Contact link. Parent-child customer hierarchies in Accruent map to the Account.ParentAccount relationship, preserving organizational structure and reporting hierarchies during the migration. This direct mapping ensures accounts load into Dynamics 365 with complete contact details and without requiring data entry by your team.

Accruent work orders map to Dynamics 365 Sales Cases as the closest structural equivalent. The Case.Title carries the work order number, Case.Description carries the service summary, and Case.CustomerId links to the Account. Original work order status, priority, and type are preserved as custom fields on the Case since Dynamics 365 Sales doesn't natively track FSM work order categories.

Accruent site records with multiple locations per customer merge into the Account record's address fields. If a customer has multiple service sites, we create a primary Account with the main address and add secondary addresses using the Address Number concept or a custom Site junction entity in Dynamics 365 Sales.

Accruent asset records have no native equivalent in Dynamics 365 Sales. We create a custom Asset table in Dataverse to store asset ID, name, serial number, manufacturer, model, install date, and linked Account. Asset hierarchies from Accruent are preserved as parent-child relationships in the custom table.

Accruent technician records map to Dynamics 365 Sales SystemUser entities by email match. Certification, skill set, and zone/territory data from Accruent migrates as custom fields on the SystemUser record. Unmatched technicians are flagged before migration; inactive or contractor technicians are flagged for manual assignment to a fallback owner.

Accruent service history entries — including completed work, parts used, labor hours, and technician notes — map to the Case's activity timeline in Dynamics 365 Sales. Each history entry becomes a Note or Post on the Case, preserving the original timestamp and technician name for audit continuity.

Accruent parts and inventory records require a custom table in Dynamics 365 Sales because the standard CRM has no inventory object. We create a custom InventoryItem table linked to the Account or Asset record, storing part number, description, quantity on hand, and reorder level from Accruent.

Accruent dispatch board scheduling data — daily assignments, route sequences, and time windows — has no equivalent in Dynamics 365 Sales. We create a custom DispatchAssignment table linked to the Case and SystemUser to preserve the scheduling record. Note that active real-time scheduling cannot be migrated; only historical completed schedule records transfer.

Accruent custom objects and user-defined fields on any standard object map to Dynamics 365 Sales custom tables or custom columns on existing tables. Custom column names follow the new_ prefix convention in Dataverse. We surface all Accruent custom fields in the migration plan before data moves so the Dynamics 365 schema is ready.

Accruent file attachments on work orders, assets, or sites re-upload to Dynamics 365 Sales Notes with a Documentbody or to SharePoint if the environment uses SharePoint integration. File size limits per Dynamics 365 apply (default 128MB per file in Dataverse). Inline images in notes are downloaded and rehosted in the target environment.