Migrate from Accruent Vx Field to Nutshell

Accruent service sites map directly to Nutshell company records. Site name becomes Company name, site address maps to the company's address fields, and the primary on-site contact becomes a Person record linked to that company. Multi-site customers appear as separate Nutshell company records with a shared parent identifier in a custom field.

On-site contacts stored in Accruent map to Nutshell person records. The person's name, phone, email, and title fields map directly. The person is associated with the corresponding Nutshell company that represents the service site. Multiple contacts at one site become separate Person records linked to the same company.

Work orders are the primary migration challenge. We map each work order to a Nutshell deal, using the work order number as the deal name and the service description as the deal notes. Work order status (Open, In Progress, Completed, Cancelled) becomes a custom pick-list field on the deal. Priority level maps to a custom priority field. The associated service site company and on-site contact link the deal to the right Nutshell company and person records.

Parts and materials consumed per work order have no native Nutshell equivalent. We create a custom text field (Parts_Used__c) storing pipe-delimited part numbers and quantities for each deal. If the organization needs granular line-item tracking, we surface this as a separate custom object with a lookup to the deal, which the Nutshell admin configures after migration.

Equipment installed at a service site is central to FSM but has no CRM equivalent in Nutshell. We migrate assets as a custom Asset object with fields for asset name, serial number, model, install date, warranty expiration, and a lookup to the Nutshell company representing the service site. Alternatively, for simpler setups, asset reference numbers are stored as a custom text field on the company record.

Accruent technicians are mapped to Nutshell users by email address match. Unmatched technicians are flagged for the admin to create Nutshell user accounts before migration. Note that Accruent technician skills, certifications, and availability rules do not translate to Nutshell — those attributes would need to be documented as a rebuild reference for any FSM tool the organization adopts separately.

Work order completion activities map to Nutshell activities. The activity subject includes the work order number, the description captures service notes, and the original completion timestamp is preserved. The activity is linked to the deal representing the work order and the person who was the on-site contact.

PM schedules define recurring service intervals per asset or site. Nutshell has no native scheduling engine for preventive maintenance. We migrate PM schedule details (frequency, last completed date, next due date) as custom fields on the asset or company record. The organization rebuilds the trigger logic in Nutshell's automation tools or adopts a dedicated FSM integration.

File attachments and photos uploaded to work orders in Accruent are downloaded and re-uploaded as attachments on the corresponding Nutshell deal record. File size limits apply (Nutshell's attachment limit per record). Inline images in work order notes are extracted and stored as separate file attachments linked to the deal.

Any custom properties defined on Accruent work orders, assets, or service sites are created as custom fields in Nutshell on the corresponding object (Deal for work order fields, Company for site fields, Asset custom object for asset fields). Field data type is preserved — pick-lists become Nutshell choice fields, dates become date fields, numbers become number fields.

Parts inventory, warehouse stock levels, and van stock are FSM-specific constructs with no Nutshell CRM equivalent. This data is exported as a reference CSV for manual use or integration with a separate inventory or parts management tool. It is not imported into Nutshell as part of the standard migration scope.

Accruent dispatch rules, geographic routing logic, technician skill matching, and SLA window configurations are FSM automation constructs that do not exist in Nutshell. These are exported as documentation for the organization to use when evaluating Nutshell integrations or dedicated FSM tools post-migration.