Migrate from EverPro to Twenty CRM

EverPro contacts — including customers, leads, and dispatch contacts — map directly to Twenty's People object. Each People record receives the contact's name, email address, phone number, job title, and company link. The original EverPro contact_id is stored as Source_System_ID__c on the Twenty People record for delta-run de-duplication, traceability back to the source system, and support for incremental sync operations after the initial migration batch completes.

EverPro company records — including business customers, site locations, and service accounts — map to Twenty's Company object. Fields that transfer directly include company name, domain, industry classification, employee count, and annual revenue. Parent-child company hierarchies in EverPro map to Twenty's parentCompany lookup relation field, preserving organizational structure across the migration. If multiple location records exist under a single parent, each migrates as a separate Company record with its parent link intact.

EverPro service tickets have no direct Twenty equivalent — Twenty has no native service-ticket or field-service object. FlitStack creates a Service_Ticket custom object in Twenty with fields for ticket ID, status, technician, service type, site address, and service date. The custom object links to the People record of the customer and the Company record of the service location.

EverPro's Customer Loyalty module stores points balance and redemption history per contact. These values migrate as custom number fields on Twenty's People object: Loyalty_Points_Balance__c and Last_Redemption_Date__c. The loyalty program logic (rules, tiers, expiry) is not portable — it must be rebuilt in Twenty's workflow builder or as a custom extension.

Some EverPro deployments track sales deals or service agreements as Opportunity records. These map directly to Twenty's Opportunity object. Fields include deal name, amount, stage, expected close date, and associated Company. If EverPro uses a custom pipeline model, stage values map via value_mapping to Twenty's Opportunity Stage pick-list.

EverPro stores activity history (service call logs, customer interactions, dispatch notes) as free-text records. These migrate as Twenty Notes attached to the corresponding People or Company record. Original timestamps and creator information are preserved. Dispatch notes with structured fields (technician name, job duration) may be split into a Task record plus a Note for full context.

EverPro custom fields on contacts — such as service_preference, site_access_code, or technician_primary_zone — create equivalent custom fields on Twenty's People object. Each EverPro field's data type (text, select, number, date) is matched to the corresponding Twenty field type during the schema setup phase. Select-list values undergo value_mapping if the source pick-list values differ from the destination pick-list values, ensuring consistent data representation across both systems.

EverPro company-level custom fields (service_contract_type, number_of_service_locations, contract_renewal_date) create equivalent custom fields on Twenty's Company object. The same data-type matching and value-mapping rules apply as for contact-level custom fields.

EverPro users (dispatchers, technicians, service managers) are not contacts but internal records. They resolve against Twenty workspace members by email match. FlitStack generates a mapping report showing matched and unmatched owners; unmatched owners are flagged for manual assignment before migration runs so no record lands without an owner.

EverPro file attachments on contacts, companies, or service tickets are downloaded and re-uploaded to Twenty Files, associated with the corresponding People, Company, or Service_Ticket record. File size limits follow Twenty's storage configuration. Inline images in notes are extracted and hosted as separate file attachments.

EverPro workflows, sequences, and contact-center automation rules do not migrate. These have no equivalent in Twenty and must be rebuilt in Twenty's workflow builder. FlitStack exports EverPro workflow definitions (trigger conditions, actions, recipients) as a structured JSON document that your Twenty admin uses as a rebuild reference.