Migrate from EspoCRM to Twenty CRM

EspoCRM Contact records map directly to Twenty CRM People records. Email, phone, address, title, and all custom fields transfer 1:1. Multi-email fields in EspoCRM (where a Contact can have multiple email addresses) map to a primary email on the Twenty People record with secondary emails stored in a custom text field. Owner resolution uses email match against Twenty Members.

EspoCRM Account records map to Twenty CRM Company records. Website, industry, address, employee count, and annual revenue transfer. The domain field in EspoCRM becomes the website field in Twenty. Company is created before any People import so that the People→Company relationship is satisfied at import time.

EspoCRM Lead records have a status field that indicates whether the lead is new, assigned, in process, converted, or junk. Leads with status converted carry an ID pointing to the target Contact or Account and are migrated as People or Company records. Unconverted leads migrate as People with the original lead status preserved in a custom field for audit.

EspoCRM Opportunity records map to Twenty CRM Opportunity with amount, stage, probability, expected close date, and description fields preserved. The opportunity stage names are recorded in a custom field since Twenty uses its own stage vocabulary. We create the Opportunity records after Company to satisfy the CompanyId lookup.

EspoCRM pipeline stages map to Twenty Opportunity stages. We configure the Twenty opportunity pipeline with stages matching the EspoCRM stage names during setup. Probability values transfer as custom fields if the customer requires exact probability mapping for reporting.

EspoCRM Cases (support tickets) have no direct Twenty CRM equivalent. Cases migrate as Tasks with the case number, priority, and resolution stored in custom fields, and the case conversation thread migrates as Notes attached to the Task record. The customer chooses whether to preserve Cases as Tasks or as a custom Case object created in Twenty's Data Model.

EspoCRM Activities (Meetings, Calls, Tasks) map to Twenty Task records. Meeting details (title, start time, end time, location) store in Task custom fields. Call duration and disposition store in custom fields. ActivityDate is set to the original EspoCRM timestamp to preserve timeline ordering.

EspoCRM Email activities migrate to Twenty Task records with the email body stored in the Task description field, sender and recipient stored in custom text fields, and the original timestamp preserved. Email threading and header metadata do not transfer as structured data.

EspoCRM Documents are stored as Attachment records linked to parent entities. On self-hosted instances, the actual file lives in data/files/ on the server filesystem. We extract referenced files during discovery, copy them to the migration staging environment, and re-upload them to Twenty via API after the parent record is created. CSV export alone does not capture file attachments; this is a parallel workflow to the database migration.

EspoCRM User records map to Twenty Members. We resolve by email match. Any EspoCRM User without a matching Twenty Member is held in a reconciliation queue; the customer provisions the missing Member in Twenty before record migration resumes. Role and team memberships do not migrate and require manual reconfiguration in Twenty's settings.

EspoCRM custom entity types created via Entity Manager map to Twenty CRM custom objects. We export the entityDefs metadata first to capture all field definitions and their types (multi-enum, currency, link-multiple, etc.), create the matching Twenty custom object and fields in Settings → Data Model before import, then migrate records using ID remapping tables to resolve any cross-entity lookups. Multi-enum fields exceeding 20 options in EspoCRM must be split into multiple multi-select fields or a single multi-select with a higher option cap set in Twenty.

EspoCRM Campaign records track marketing campaign metadata and target lists. Twenty CRM has no native Campaign object. Campaign metadata migrates as a custom object or as Tasks with campaign name, type, and status stored in custom fields. Target list membership (Leads and Contacts) does not migrate as structured relationships; we deliver a CSV of campaign-target mappings for the customer to rebuild manually in Twenty.