Migrate from Evatic to HubSpot

Evatic customer records map directly to HubSpot Companies. Primary site address migrates to the Company address fields. Multi-site Evatic customers with separate location records are handled as additional Company address properties or associated via HubSpot's company-to-company association model. Any customer record without a valid address is flagged during the sample migration so the team can supply missing location data before the full run.

Evatic contact persons map to HubSpot Contacts. Each Contact is associated to the destination Company by email-domain or explicit company-name match. Multiple contact persons at the same Evatic customer become separate HubSpot Contact records linked to the same Company. We validate email addresses during the sample migration and flag any malformed or duplicate emails for team review before the full load proceeds.

Evatic service contracts map to HubSpot Deals. SLA tier (Gold, Silver, Bronze), contract start and end dates, billing frequency, and auto-renewal flag become custom properties on the Deal. Contract value maps to Deal amount. The Deal is associated to the destination Company record.

SLA response time, SLA resolution time, and SLA escalation contacts have no native HubSpot equivalent. We create custom pick-list and text fields on the Deal object (SLA_Tier__c, SLA_Response_Hours__c, SLA_Resolution_Hours__c, SLA_Escalation_Contact__c) to preserve the full SLA contract context. Custom field names are confirmed with your HubSpot admin during schema setup to avoid conflicts with existing portal properties.

HubSpot has no native work order object. On HubSpot Enterprise plans we create a Work_Order__c custom object with properties for status, priority, assigned technician, site location, work description, and parts used. The object links to the destination Company and Contact records. If the destination is not Enterprise, work order summaries are stored as notes on the associated Deal.

Evatic work order statuses (Open, In Progress, On Hold, Completed, Cancelled) are mapped value-by-value to the custom Status pick-list on the Work_Order__c custom object. Custom pick-list values are created in HubSpot before migration runs. Any Evatic status value not recognised during the sample migration is flagged for explicit mapping before the full load commits.

Evatic equipment records — serial number, model, install date, and warranty expiry — require a Unit__c or Equipment__c custom object on HubSpot Enterprise. The custom object links to the destination Company and optionally to a Work_Order__c record. On non-Enterprise destinations, serial number and model are stored as properties on the Company record.

Evatic locations and sites associated with a customer become additional address properties on the HubSpot Company record or are stored as a structured text property (Site_List__c). Multi-floor or multi-building addresses are concatenated into a single address string. We flag any location without an associated Evatic customer before migration.

Evatic completed tasks and site visit logs migrate as HubSpot Notes linked to the associated Contact or Deal. Original timestamps and technician names are preserved in the note body. The notes carry service-history context so the HubSpot Contact record reflects the full service relationship.

Parts consumed during a work order have no native HubSpot equivalent. We append parts details (part number, quantity, date used) to the associated Work_Order__c record as a structured text property or note attachment. On non-Enterprise destinations, parts summaries are added to the related Deal note.

Evatic technician and owner records are resolved by email match against HubSpot Users. Unmatched technicians are flagged before migration — the team either creates HubSpot user accounts first or assigns records to a designated fallback owner. Technician names without email addresses are stored as text in a custom field on the Work_Order__c record.

Evatic dispatch rules, SLA escalation triggers, and auto-assignment workflows have no equivalent in HubSpot. We export workflow definitions as a structured JSON reference document that documents each rule's trigger conditions, action sequences, and assignment logic. Your team can use this export as a blueprint to rebuild equivalent automations in HubSpot Workflows or a third-party field-service integration, prioritising the highest-impact dispatch rules first for post-migration operational continuity.