Migrate from erxes to Twenty CRM

erxes Contacts migrate directly to Twenty CRM People records. Standard fields (name, email, phone, primaryAddress) map to the corresponding Twenty Person fields. We extract custom field values from erxes' property system and map them to Twenty custom fields, validating type compatibility (text, number, date, select) against Twenty's field definitions before insert. Any erxes Contact without an email receives a generated placeholder and a custom flag for manual review.

erxes Company records map 1:1 to Twenty CRM Companies. The company domain, industry, size, and address fields migrate directly. We resolve the linked Contacts to associate them with the migrated Company record using the companyId reference preserved in the erxes data model. Company is created before Person import so the lookup relationship is satisfied at insert time.

erxes Deals map to Twenty CRM Opportunities with the deal amount, stage, and custom fields preserved. We translate the erxes dealstage property to Twenty's Opportunity stage values. Any erxes Deals without a linked Company are imported with a placeholder Company record to satisfy the lookup requirement, and we flag these for the customer's admin to reconcile after migration.

erxes Pipelines define the sales workflow stages and map directly to Twenty CRM Pipelines. Stage order, names, and probability mappings migrate as configuration. We create the Twenty Pipeline first, then create the stage definitions with the correct sort order before importing Deals so that stage lookups are available at insert time.

erxes Tasks migrate to Twenty CRM Tasks with title, description, due date, status, and priority preserved. Task ownership migrates by resolving the erxes userId to the Twenty WorkspaceMember via email match. Tasks linked to specific Contacts or Deals maintain their association through the appropriate lookup fields in Twenty's data model.

erxes multi-channel Conversations (email, SMS, chat, WhatsApp) migrate to Twenty as Activity records with Comment records for the message thread. We preserve the conversation metadata (channel type, direction, customer identifier) and the message body, author, and timestamp. Message ordering depends on erxes' server-side createdAt timestamps which we preserve during import. Channel credentials (API keys, webhook URLs) do not migrate and are flagged for manual reconfiguration in Twenty's workspace settings.

erxes custom fields on Contacts map to Twenty custom fields on the Person object. We validate erxes' schema-less values against Twenty's typed field model before import and flag any type mismatches. For example, if an erxes date custom field contains a text string (which erxes allows), we flag the record and either correct the value or exclude it from that field with a reconciliation note.

erxes custom fields on Deals map to Twenty custom fields on the Opportunity object. Same type-validation approach applies: erxes allows any value to be written to any custom field regardless of UI-defined type, so we validate against Twenty's field schema and flag mismatches. Complex custom field structures (multi-select, relational) are documented separately for the customer's admin to verify in Twenty's data model.

erxes Users map to Twenty WorkspaceMembers via email match. Role and permission configurations are documented for manual review because Twenty's role model differs from erxes' plugin-based permission system. We extract all distinct users referenced on records (Contacts, Companies, Deals, Tasks, Conversations) to build the user mapping table, and flag any erxes user without a matching Twenty WorkspaceMember for the customer's admin to provision before record import.

erxes Automation Workflows are not migrated as code. We extract the full workflow structure including triggers, conditions, and actions from the erxes plugin configuration and deliver a written inventory document. Each automation is documented with its name, trigger type, conditions, action sequence, and a recommended Twenty equivalent or note that the workflow pattern is not supported. The customer's admin rebuilds automations in Twenty post-migration.