Migrate from eZnet CRM to Twenty CRM

eZnet CRM Accounts map directly to Twenty CRM Companies. The Account Name becomes Company name, Website maps to Company website, and any Account-level custom fields (industry classification, employee count, annual revenue) map to equivalent Company custom fields. Account-Contact associations are preserved by creating the Company record first in migration order so that Person records can reference it via the companyId field. We use Account name as the dedupe key during import.

eZnet CRM Contacts map to Twenty CRM Person records. Standard fields (firstName, lastName, email, phone, address) transfer directly. The Contact-Account association resolves to the Company record via companyId. Contact custom fields (department, title, preferred contact method) map to Person custom fields. If the Contact has an associated email integration record from eZnet CRM Professional tier, we preserve that as a note attached to the Person.

eZnet CRM Leads are distinct from Contacts and carry lead status, source, and custom lead fields. Twenty CRM currently uses a unified Person model without a separate Lead object. We map Leads to Person records and flag them with a custom status field (e.g., lead_status__c = 'Lead') to preserve the original lead lifecycle. The customer's admin reviews and converts these Person records to opportunity-ready status post-migration. Lead source and score fields transfer to custom Person fields.

eZnet CRM Opportunities map directly to Twenty CRM Opportunities. Pipeline stage names, deal amounts, expected close dates, and probability percentages transfer. The Opportunity-Account and Opportunity-Contact associations resolve to CompanyId and PersonId respectively during migration. Stage names map from eZnet pipeline stages to Twenty Opportunity stage values, with a stage mapping table reviewed and approved by the customer before import.

eZnet CRM pipeline and stage configuration (stage names, order, win/loss definitions) is captured from source and mapped to Twenty's Opportunity stage values. We create a stage mapping table as part of the migration scope document. The customer reviews and approves the mapping, then we configure Twenty's opportunity stages to match the business logic of the source pipeline. Probability percentages migrate from eZnet to Twenty stage probability fields.

eZnet CRM Activities (calls, emails, tasks, events) map to Twenty CRM Notes and Tasks. Activity type distinguishes between note entries (mapped to Note) and action items (mapped to Task with Task status). Activity date, owner, and notes text transfer directly. The Activity-Contact and Activity-Account associations resolve to PersonId and CompanyId via the parent-record lookup we performed during scoping. Meeting-type activities become Event records in Twenty's activity model.

eZnet CRM Document Library records contain file metadata (name, type, creation date, associated Contact or Account). We export the document metadata and link it to the parent Person or Company record in Twenty. Actual file blobs (PDFs, images, spreadsheets) require separate handling: we flag them as a manual step during scoping, provide the customer with a file list and attachment procedure, and note that the files need to be uploaded to Twenty's attachment system post-migration.

eZnet CRM custom fields (available on Standard tier and above) include data type, picklist values, and visibility settings. We capture the full custom field schema from the source system during scoping, then reconstruct it in Twenty CRM using Twenty's field creation interface or API. Picklist values map as-is; validation rules do not transfer and must be recreated manually in Twenty. The customer's admin reviews the custom field schema reconstruction before migration begins.

eZnet CRM Users with role-based assignments map to Twenty CRM workspace Users. Owner associations on Opportunities, Activities, and Contacts transfer by matching on user email. We reconcile owners by email against the Twenty workspace user list; missing users go to a provisioning queue for the customer's admin to create before record import resumes. Inactive users in eZnet CRM are preserved as historical owners in Twenty with inactive status where supported.

eZnet CRM Marketing Campaign records and associated campaign member associations to Contacts are exported. Campaign member status and engagement data transfer to Twenty as Campaign records linked to Person records. We note that marketing automation logic (email sequences, lead scoring triggers) does not migrate and must be rebuilt. The campaign metadata provides a record of what marketing programs existed for audit and attribution purposes.

eZnet CRM Inventory Items (Professional tier and above) include item records, stock levels, and pricing. We export inventory metadata as a custom data set. In Twenty CRM, there is no native inventory object, so inventory data is mapped to a custom object or linked as note-attached data on the relevant Company or Person. The customer's admin determines whether inventory data is relevant for their Twenty use case and how to structure it.

eZnet CRM Enterprise tier supports Custom Modules and Custom Related Lists. These map to Twenty CRM custom objects. We capture the full module schema including related list definitions, field types, and inter-object relationships, then reconstruct them in Twenty before the main record migration begins. Custom object naming follows Twenty conventions. Lookup relationships to standard objects (Company, Person, Opportunity) are re-established using the IDs resolved during parent-record import.