Migrate from X2CRM to Twenty CRM

X2CRM Accounts represent companies and organizations linked to Contacts. We map Accounts to Twenty's Company object using the company name or domain as the dedupe key during import. Associated tags, industry classification, website URL, employee count, and annual revenue migrate to their corresponding Twenty Company fields. If X2CRM uses a custom industry picklist, we create the matching options in Twenty's Data Model before import. Company is created before any Person import so that the company-person relationship is satisfied at Person insert.

X2CRM Contacts store name, email, phone, address, and job title as standard properties. We map Contacts to Twenty's Person object using email as the dedupe key. First name, last name, email, phone, and address fields migrate directly. Job title and department map to custom fields that we create in Twenty's Data Model before import. We preserve the X2CRM assignedTo owner reference by resolving it against the Twenty Members list, flagging any unmatched owners in a reconciliation report for your admin to provision before Person import resumes.

X2CRM Deals track sales opportunities with stage, value, probability, expected close date, and pipeline association. We map Deals to Twenty's Opportunity object. The X2CRM deal stage maps to a Twenty Opportunity stage value that we configure in Data Model during scoping. Deal amount and probability migrate directly. If X2CRM tracks multi-stage pipelines as separate deal types, we create a corresponding Opportunity field or Record Type in Twenty before migration. Closed-Lost and Closed-Won status from X2CRM maps to Twenty's Opportunity stage with probability and close date preserved.

X2CRM Products catalog items with pricing, SKU, and description. We map Products to Twenty's Product object. Product name, SKU (mapped to productCode), and unit price migrate directly. If X2CRM has associated price books or price lists, we consolidate them into a single price book in Twenty since Twenty's current API does not expose multi-price-book functionality.

X2CRM Services track recurring service contracts or subscriptions linked to Accounts. Twenty CRM has no native Services object, so we create a custom object named ServiceContract in Twenty's Data Model during discovery. The custom object includes fields for contract name, account link, status, renewal date, and monthly or annual value. We create the custom object and all its fields before any X2CRM Service data is exported.

X2CRM Campaigns store campaign name, type, status, and associated mailing lists. Twenty CRM has no native campaign management object. During scoping we determine whether the customer's campaign records contain historical performance data (open rates, click rates, revenue attribution) that requires a custom Campaign object in Twenty, or whether campaign names and status values are sufficient to migrate as Note records attached to the associated Company or Person. The customer's RevOps lead makes this decision before migration begins.

X2CRM Activities include calls, meetings, and tasks with timestamps, owners, and related Contacts or Deals. We map X2CRM Activity records to Twenty Tasks and Notes. Call activities with disposition and duration migrate as Notes with the call details in the body. Meeting activities with location and attendees migrate as Notes or Tasks with date and description preserved. Task activities migrate directly to Twenty Tasks with status, priority, and due date. Activity timestamps and owner assignments are preserved by resolving the owner against the Twenty Members list.

X2CRM Tags are standalone label records applied across object types. We export all Tags and reapply them to their target records post-import. For Person and Company records, Tags migrate to a multi-select custom field in Twenty's Data Model that we create before import. For activity-level tagging, we evaluate whether to attach tags as Note text or to a separate tagging strategy based on the customer's reporting needs. The customer chooses the tagging approach during scoping.

X2CRM custom fields added via module builder vary by module and require field-level mapping during discovery. We inspect the X2CRM field schema via API discovery, map each custom field to an equivalent Twenty custom field type (text, number, date, select, multi-select, currency, checkbox), create the field in Twenty's Data Model before any data arrives, then map the values during the import transform phase. Fields with picklist values require matching option sets created in Twenty first.

X2CRM User accounts include name, email, role, and assignment permissions. We export all Users and match them to Twenty Members by email during import. Any X2CRM User without a matching Twenty Member is placed in a reconciliation queue; your admin provisions the missing Members before record import resumes. Role and permission configurations in X2CRM (viewer, editor, admin) are documented for your admin to configure in Twenty's Members and Roles settings post-migration.

X2CRM attachments are stored as file references or blobs linked to records. On cloud-hosted X2CRM, we extract attachment URLs from the API response and re-upload via Twenty's GraphQL file upload mutation, linking the file to the target Company, Person, or Opportunity record. On self-hosted X2CRM, the attachment storage may use local disk paths requiring SSH or admin panel access to expose the upload directory — we coordinate with your IT team during discovery to confirm the attachment backend and access method before scoping.