Migrate from Evatic to Freshsales

Evatic customer records (name, email, phone, address) map directly to Freshsales Contacts. Multi-site customers with multiple Evatic records per entity collapse to one primary Contact in Freshsales, with additional site-specific data stored as custom fields on the related Account for complete visibility.

Evatic contracts — including SLA terms, response-time commitments, contract value, and start/end dates — map to Freshsales Deals. SLA-specific fields (response time, resolution time, contract type) become custom fields on the Deal. One Evatic contract = one Deal in Freshsales with a linked Account.

Evatic company records map to Freshsales Accounts. Company-level fields (name, address, industry, employee count) migrate directly. Evatic's multi-site structure (if the same company has multiple service locations) maps to a primary Account with site-specific data stored as custom fields or in a custom Site object.

Evatic sites represent physical locations with addresses, site contacts, and service scope per location. These map as custom fields on the related Freshsales Account (Site_Address__c, Site_Contact__c, Site_Service_Scope__c) or as a custom Site object if the Evatic setup has complex per-location service histories.

Evatic assets (serial number, model, install date, warranty expiry, service history) have no Freshsales native equivalent. We create Asset__c custom fields on the linked Account for key asset metadata, and map service history as Activity records or Deal notes. Complex asset hierarchies can use a custom Asset object.

Evatic work orders and service jobs — job status, assigned technician, scheduled date, completed work, parts used — map to Freshsales Deal Activities (Tasks with custom fields for job type, parts, and resolution) and Deal notes for narrative summaries. Closed work orders preserve their final status and outcome.

Evatic technician records map to Freshsales Users by email match. Unmatched technicians are flagged — they can be invited to Freshsales or their assignments are migrated as text fields on the related work-order activity. Freshsales User role and profile determine access after migration.

Evatic contract line items with individual service items, quantities, and pricing merge into Freshsales Deal Products (if the line has a product-like structure) or into custom multi-select fields on the Deal capturing scope of service. Pricing details from Evatic lines map to Deal amount or custom currency fields.

Evatic service history entries — site visits, repairs, maintenance calls, parts replaced — map to Freshsales Tasks and Notes. Each entry preserves the original timestamp, technician owner, linked Account/Deal, service date, work summary performed, and final outcome for complete historical traceability.

Evatic custom fields on any object (contracts, assets, sites, work orders) map to Freshsales custom fields using the same field type where available. Pick-list values require value-by-value mapping; text fields map directly; date/datetime fields preserve original timestamps as custom datetime fields.