Migrate from CRM Service to Twenty CRM

CRM Service Accounts map directly to Twenty CRM Company records. The Account Name field becomes Company Name, Industry maps to Twenty's industry select, Annual Revenue maps to the revenue fields, and billing/shipping addresses map to the address fields. We use Account Name as the dedupe key during import. Company is created before any People import so that the relationship is satisfied at the moment of Contact insert.

CRM Service Contacts map to Twenty CRM People records. The Contact's AccountId lookup resolves to the Twenty Company record already imported. Email, phone, title, and department fields map directly. We preserve the original Salesforce Contact ID in a custom field as a reference back to the source system for audit and reconciliation.

CRM Service Opportunities map to Twenty CRM Opportunities. StageName maps to Twenty's stage property, Amount maps to the amount field, CloseDate maps to the close date, and Probability migrates as a percentage field. Note that Reddit users have flagged that Twenty v2.0 lacks an automated incremental numbering system for Opportunity or project IDs; we flag this during scoping and the customer's admin sets up a manual naming convention or external ID system before go-live.

CRM Service Leads do not have a direct Twenty equivalent because Twenty CRM does not ship a separate Lead object. We handle this in two ways based on customer preference: either convert all Leads to Twenty People records with a custom type field set to Lead, or create a separate custom object in Twenty called Lead to mirror the source. We preserve the Lead Status and any lead scoring values in custom fields on the destination record.

CRM Service custom objects with the __c suffix migrate to Twenty CRM Custom Objects. Twenty requires all custom fields to be created in Settings → Data Model before CSV import begins. We pre-create the destination schema including all custom fields, their types, and any lookup relationships during the schema design phase. Custom object naming conventions differ: Salesforce uses __c suffix; Twenty uses clean API names that we define during mapping.

CRM Service Tasks migrate to Twenty CRM Tasks. Subject, Status, Priority, ActivityDate, and Description fields map directly. Owner assignments resolve via email matching against the Twenty Members list, which must be provisioned before Task import (Twenty documentation explicitly requires inviting team members before importing data with owner references).

CRM Service Events (meetings, calendar entries) map to Twenty CRM Notes because Twenty does not have a native Event object equivalent. We preserve the event Subject as the Note title, the StartDateTime and EndDateTime as text in the Note body, and Location as a separate line. The Note is linked to the related Company or People record via Twenty's relationship system.

CRM Service Attachments and Files (ContentDocument/ContentVersion) require separate export via Salesforce ContentDocument or Attachment objects. File sizes and storage limits in Twenty depend on the customer's self-hosted PostgreSQL storage allocation. We export files to a staging location, then upload to Twenty's attachment system linked to the parent record. Very large files may require the customer to provision additional storage.

CRM Service Campaigns track marketing initiatives with member status and response data. Twenty CRM does not have a native Campaign object. We map Campaigns to Twenty Companies with a tag applied for segmentation, or we create a custom Campaign object during schema setup. Campaign-to-Contact associations migrate as custom relationship records.

CRM Service Cases from Service Cloud do not have a direct Twenty CRM equivalent. For teams migrating both sales and service data, we create a custom Case object in Twenty during schema setup, mapping Status, Priority, Origin, and the Contact association. For teams only migrating sales data, Cases map to Notes on the related Company or People record.

CRM Service Users map to Twenty CRM Members. We match by email address. Twenty's documentation explicitly requires inviting all Members and waiting for acceptance before importing data that references owners or assignees. We extract every distinct Owner referenced on Contacts, Accounts, Opportunities, and Tasks and match against the provisioned Twenty Members list. Any Owner without a matching Member goes to a reconciliation queue for the customer's admin to provision.

CRM Service Products (Product2 records) do not have a native Twenty CRM equivalent. We map Products to a custom Product object in Twenty, creating the schema during setup and importing Product Name, Product Code, and Description fields. Price book entries require a custom pricing configuration in Twenty.