Migrate from Evatic to HighLevel

Evatic customer records (name, phone, email, address) map directly to HighLevel Contact records. FlitStack resolves the primary contact per customer account and imports all additional contact details. Email addresses are used to detect duplicates and match against existing HighLevel contacts.

Evatic companies (business name, industry, address, primary contact) map to HighLevel Company records. FlitStack links each Company to its primary Contact record and surfaces any secondary contacts as additional Contact entries associated with that Company. Industry classification values are mapped using a value table where Evatic and HighLevel share options; unmatched industry values are preserved as custom text fields.

Evatic work orders map to HighLevel Opportunities, with the pipeline stage representing the work order status (e.g., 'Scheduled' → a custom pipeline stage, 'Completed' → 'Closed Won'). Work order number migrates as Opportunity name with a prefix, and the original work order total migrates as the Opportunity value amount.

Work order line items that represent billable services split across two destinations: service descriptions migrate as Opportunity custom text fields, and line-item amounts aggregate into the Opportunity value. HighLevel's Products feature can be used if the line items represent repeatable service products rather than one-off job charges.

Evatic contracts with SLA terms, start/end dates, and billing frequencies do not have a native equivalent in HighLevel. FlitStack creates a Contract custom object in HighLevel linked to the Company record, populating fields for contract type, effective dates, renewal date, and SLA tier. If the contract count is small, contract terms may instead attach as structured custom fields on the Company record.

Evatic equipment records — serial number, model, location, maintenance schedule, and linked customer — migrate as a dedicated Equipment custom object in HighLevel. A lookup relationship links each Equipment record to the associated Company (and optionally to the Contact at that location). Maintenance schedules migrate as custom date fields for reference.

Evatic technician and staff records resolve by email match against HighLevel user accounts. Technicians who are also sales or account managers get HighLevel user accounts; support-only technicians become Contacts in HighLevel so they can be referenced in work order history. Unmatched staff records are flagged before migration for manual assignment.

Evatic location records with service-site addresses map to HighLevel Company address fields. For multi-site customers, each location can be represented as a separate Company record with a custom 'Parent Company' field linking it to the primary account, mirroring Evatic's location hierarchy.

Evatic work order notes, technician comments, and completed-work descriptions migrate as Notes attached to the corresponding HighLevel Opportunity record. Timestamps and technician attribution are preserved in the Note metadata. Completed work orders also generate a HighLevel Opportunity Activity entry for audit continuity.

Evatic file attachments on work orders and equipment records (photos, signed forms, diagnostic reports) are downloaded and re-uploaded to the corresponding HighLevel Contact, Company, or Opportunity record. FlitStack respects HighLevel's file size limits and preserves the original filename for traceability.

Evatic work order statuses (e.g., Created, Assigned, In Progress, On Hold, Completed, Cancelled) map to HighLevel pipeline stage values. FlitStack builds a value-map table during planning and applies it consistently across all work orders. Teams can customize pipeline stage names in HighLevel to match their service process language.

Every Evatic custom field on work orders, contracts, and equipment creates a corresponding custom field in HighLevel on the mapped object (Opportunity, Contract custom object, or Equipment custom object). Field types are translated: Evatic pick-lists become HighLevel drop-down custom fields, date fields map directly, and text fields map to text custom fields.