Migrate from Accruent Vx Field to Salesforce Sales Cloud

Accruent customer records map to Salesforce Accounts with address fields, industry classification, and primary contact preserved during migration. Accruent's customer type field (internal vs. external) is translated to a custom pick-list on Account since Salesforce's Type field may not capture the full nuance of Accruent's customer classification system.

Assets migrate as Salesforce Asset records with product reference, install date, status, and parent asset hierarchy preserved from the source system. Accruent's operational status values (Active, Inactive, Under Maintenance) are mapped to Salesforce Asset Status pick-list via value-by-value translation to ensure status consistency across the migrated dataset.

Salesforce Sales Cloud does not include a native Work Order object — teams use Cases with custom fields or license Salesforce Field Service. FlitStack maps Accruent work order fields to Case (Subject, Description, Status, Priority, AccountId) plus custom fields for skill requirements, labor hours, and cost.

Accruent's hierarchical site structure (parent site, sub-site, zone, bin) maps to Salesforce Location with parent LocationId establishing the hierarchy chain. GPS coordinates migrate as custom decimal fields since Salesforce Location stores lat/long natively only when Salesforce Maps is enabled and configured for your org.

Accruent technicians and dispatchers resolve to Salesforce Users by email match. User must exist in Salesforce before migration — unmatched technicians are flagged for admin to create or assign to a fallback owner. Field Service licenses (FSL) required for technician scheduling functionality.

Parts catalog from Accruent migrates as Salesforce Product2 records with standard price book entries for pricing. Bin-level stock tracking requires a custom Inventory_Bin__c object since Product2 stores stock status but not bin location — FlitStack surfaces this gap in the migration plan for your admin to configure before go-live.

PM schedules containing frequency, interval type, and next due date have no direct equivalent in Salesforce's standard object model — FlitStack migrates these as a custom Maintenance_Schedule__c object related to Asset with fields for frequency, interval type, and next due date to preserve your preventive maintenance program.

Accruent attachments including images, PDFs, and inspection documents re-upload to Salesforce Files linked to the target record (Asset or Case) via ContentDocumentLink. Salesforce's 25MB per-file limit applies to all uploaded files — any attachment exceeding this threshold is flagged in the pre-migration report for manual handling.

Accruent asset parent-child relationships migrate using Salesforce's ParentAssetId lookup field on the Asset object. Parent assets must be migrated before child assets to ensure the lookup resolves correctly — any circular reference chains in the Accruent data are flagged and resolved during the pre-migration data audit phase.

Accruent work order status-change history migrates as custom Work_Order_History__c records related to the Case, or as standard CaseHistory for basic status transitions. Timestamps and the technician who made each change are preserved in the custom fields to maintain full audit trail in Salesforce.

Accruent custom properties on any object (assets, locations, work orders, customers) map to Salesforce custom __c fields. Each custom property requires a corresponding field created in Salesforce before migration; FlitStack generates a pre-migration checklist specifying field type, pick-list values, and default values for each property to be migrated.

Technician skills and certifications stored in Accruent map to a custom Skill__c object related to User, or as a multi-select pick-list on the User record. Your Salesforce admin chooses the implementation approach based on how skills drive work order assignment in Salesforce Field Service or Flow-based matching rules.