Migrate from Accruent Vx Field to Freshsales

Work orders map to Freshsales Deals. Job name becomes Deal name. Job status (Open, In Progress, Completed, Cancelled) maps to a custom Deal status field since Freshsales Deal stages are pipeline-driven. Original work order ID is preserved in a custom Source_Work_Order_ID__c field for traceability.

Accruent service locations map 1:1 to Freshsales Accounts. Location name becomes Account name. Address, city, state, and postal code map to the standard Freshsales Account address fields. Industry field is set from a mapping rule based on location type (Commercial, Industrial, Residential).

The primary customer record in Accruent maps to the Freshsales Account that owns the service location. If the customer has multiple service locations, each location becomes a separate Freshsales Account, and the top‑level customer can be linked as a Parent Account. Parent‑account hierarchies in Accruent map to Freshsales Parent Account relationships where applicable, preserving the corporate structure. FlitStack validates Account name uniqueness and flags duplicates for admin review.

Technicians become Freshsales Contacts with a Role custom field set to 'Field Technician'. First name, last name, email, and phone map directly. If a technician has a Freshsales login, their Contact is linked to User record using email for matching. Email is used for user‑match resolution against Freshsales users. Unmatched technicians are flagged before migration, and your admin can create a Freshsales user or assign records to an owner.

Assets with serial numbers, manufacturer, model, and install date map to a Freshsales custom Asset object. High-volume equipment that is part of a service contract may map to the Freshsales Product Catalog if your team uses Products to track billable items. Asset hierarchy (parent-child equipment relationships) requires a custom Parent_Asset__c field in Freshsales.

Parts and inventory items migrate as Freshsales Products. Part number becomes Product code. Unit price maps to Product price. Stock quantity is stored in a Quantity_in_Stock__c field since Freshsales Products do not track on‑hand inventory. If a part is used on a work order, it appears as a Deal Product line item, preserving the link to the work order. Product description, category, and vendor information map to Freshsales Product fields.

Parts consumed on a work order merge into the Freshsales Deal's product line items. The work order reference is preserved in a custom field on the Deal Product so the job-part relationship is traceable back to the original Vx Field record.

Scheduled technician appointments become Freshsales Tasks with Type='Field Visit'. Start and end time, technician contact link, and related Account/Deal are preserved. Dispatch notes and route information map to the Task description field for technician reference. If the appointment includes a site address, the address is stored in the Task location field, and checklist items are added as subtasks. Time zones are normalized to Freshsales default zone to ensure accurate scheduling.

Work order status changes, technician check‑ins, and completion notes load into Freshsales Deal timeline as activity events. Timestamps and technician owner are preserved, keeping the service history visible on each Deal record. Activity is tagged with the source object (Work Order) and the technician Contact, allowing users to filter the timeline by role. If a work order includes items, each part usage appears as an activity linked to Deal Product.

Service‑level agreements, contract dates, and SLA tier (Gold, Silver, Bronze) migrate as custom fields on the Account. SLA level maps to a SLA_Tier__c pick‑list on Account record. SLA response time and resolution time targets are stored in number fields, and breach flags are transferred as checkbox fields. Each Account’s SLA configuration is linked to related Deals via a custom SLA_ID__c lookup, allowing reps to view service terms on the deal.

Accruent custom fields on any object (Work Order, Asset, Location) are recreated in Freshsales as custom fields on the equivalent object. Field type is mapped: text→text, number→number, date→date, pick-list→pick-list with values preserved. Validation rules and required-field flags are applied per Freshsales field settings.

Accruent user records are matched to Freshsales users by email address. If a technician email has no corresponding Freshsales user, their records are assigned to a fallback owner and the technician is flagged for account creation before go-live. User role and permission-level mapping is outside FlitStack's scope and must be handled in Freshsales Admin settings.