Migrate from Evatic to Twenty CRM

Evatic stores customer contact records with name, email, phone, and address fields. These map 1:1 to Twenty's People object. The primary contact's email is used as the unique identifier for owner resolution against Twenty workspace members. Multi-contact accounts are preserved by importing all contacts with the same companyId reference.

Evatic company records map directly to Twenty's Companies object. Company name, industry, website, address, and employee count fields translate directly. Parent-company hierarchies in Evatic are preserved via a custom parentCompanyId field or by importing in dependency order — parent records first, then children.

Evatic service agreements track SLA terms, contract start/end dates, billing cycles, and coverage scope. Twenty has no native contract-management object. FlitStack creates a ServiceContract custom object in Twenty with fields for contract type, SLA tier, start date, end date, and billing frequency. Contract records import after Companies so the companyId lookup resolves correctly.

Evatic stores equipment and unit records with serial numbers, model numbers, install dates, warranty expiration, and maintenance schedules. These map to a custom EquipmentAsset object in Twenty with fields for serial number, model, manufacturer, install date, warranty expiry, and a relation back to the owning Company. Equipment hierarchies (parent unit → sub-assembly) use a self-referential parentUnitId field.

Work orders are the central Evatic entity — tracking status, priority, scheduled date, assigned technician, site location, description, parts used, and time spent. These map to a custom WorkOrder object in Twenty. Key fields include workOrderNumber (unique), status, priority, scheduledDate, assignedTechnicianId (lookup to Twenty workspace member), companyId (lookup to Companies), equipmentId (lookup to EquipmentAsset), description, partsUsed (text area), and timeLogged.

Evatic work orders can contain multiple line items — parts consumed, labor entries, and travel charges. These translate to a WorkOrderLineItem custom object with a relation to WorkOrder. Each line has a type (part/labor/travel), description, quantity, unit cost, and total. If Evatic stores line items as nested fields rather than separate records, FlitStack denormalizes them into individual WorkOrderLineItem rows per work order.

Evatic logs technician activities — site visit reports, call summaries, email threads — as structured event records with timestamps and owners. These map to Twenty's Tasks (for action items and call logs) and Notes (for site-visit reports and longer narrative entries). Original activity timestamps are preserved in a custom activityLoggedAt field on both Task and Note records so historical sequence is intact.

If Evatic stores pre-contract sales opportunities alongside service records, those map directly to Twenty's Opportunities object. Opportunity name, amount, stage, expected close date, and owner map to the equivalent Twenty Opportunity fields. If Evatic does not track opportunities separately from service contracts, this object mapping is omitted and the pipeline is handled via custom ServiceContract status fields.

Evatic files attached to work orders (photos, signed forms, PDF reports) are downloaded and re-uploaded as Twenty Notes with the file attached. The Note body links back to the parent record (WorkOrder or EquipmentAsset) via Twenty's standard relation mechanism. File size limits are respected per Twenty's storage configuration.

Evatic custom fields on any entity — service agreements, equipment, work orders — require a corresponding custom field in Twenty's Settings → Data Model before import. FlitStack audits the Evatic custom field inventory, creates all required fields in Twenty first, then maps values during the import run. Field types are translated: Evatic text fields map to Twenty TEXT, pick-lists to SELECT, dates to DATE, numbers to NUMBER.

Evatic technicians and work-order owners are user records with email addresses. Twenty requires workspace members to be invited and active before owner lookups can resolve. FlitStack matches Evatic technician emails against Twenty workspace members by email — unmatched owners are flagged before migration and assigned to a fallback Twenty user or a dedicated 'Unassigned' technician record.

Evatic SLA escalation rules, automated technician dispatch triggers, and contract-renewal alerts do not have a direct equivalent in Twenty's workflow builder. FlitStack exports Evatic workflow definitions as a structured JSON rebuild reference document. Twenty's workflow builder supports trigger-based automations (record create, field update, status change) but SLA countdown and routing logic must be rebuilt using Twenty workflows or an external automation layer.