Migrate from Zendesk Sell to Twenty CRM

Zendesk Sell Contacts where is_organization equals false map to Twenty People. Standard fields (first name, last name, email, phone, address) migrate directly. The contact owner maps to a Twenty workspace Member, requiring that the Member record exists before import. We resolve owner by email match and flag any owner without a matching Twenty Member for the admin to provision.

Zendesk Sell Contacts where is_organization equals true map to Twenty Company. Organization name maps to Company name. We also migrate the organization domain as the Company website for deduplication reference. Company records must be created before any related People records so that the People-to-Company relationship is satisfied at insert time.

Zendesk Sell Organizations (a distinct object from Contacts) map to Twenty Company with the same treatment as organization-type Contacts. The Organization name becomes the Company name and the domain becomes the Company website. Any address data on the Organization migrates to the Company address fields.

Zendesk Sell Deals map to Twenty Opportunity. Deal fields (amount, expected close date, loss reason, deal source) migrate directly. The Deal's associated pipeline and stage assignment become the Opportunity stage value in Twenty. Loss reasons from Sell become a custom field on Opportunity rather than a native loss reason, since Twenty's Opportunity model uses a stage picklist for status.

Zendesk Sell Pipelines are custom workflow containers with ordered Stages inside them. Twenty does not support multiple independent pipelines. We map each Sell Pipeline to a distinct set of stage values prefixed with the pipeline name (e.g., PipelineA__StageName) and consolidate into a single Opportunity stage picklist. Stage order and win/loss flags are preserved as stage value metadata. Customers with very different pipeline models need to decide during scoping which pipeline becomes the primary and which stage sets get merged.

Zendesk Sell Leads are a first-class object with their own sources and unqualified-reason fields. We assess lead quality at migration time: unqualified or stale Leads map to Twenty People; Sales Qualified Leads with an associated Deal map to both People and a linked Opportunity. We preserve the original lead_source as a custom field on the People record and flag any territory assignments for admin reconfiguration.

Zendesk Sell Tasks migrate to Twenty Task. Due date, assignee (resolved by email to Twenty Member), completion status, and priority migrate directly. Task notes migrate as a Task body or as a linked Note. Task assignments to Contacts, Deals, or Organizations carry the parent record reference, which we resolve after parent records exist in Twenty.

Zendesk Sell Notes are free-text records that attach to Contacts, Deals, Organizations, or Companies. We migrate Notes with the parent reference intact so conversation context links to the correct People or Company record in Twenty. Notes are inserted after parent records are created to satisfy the relationship.

Sell custom fields on Contacts, Deals, Leads, and Organizations map to Twenty custom fields created in Settings before import. We resolve the Sell custom field key (required for API calls) during scoping and create a lookup table. Field types are mapped: Sell text becomes Twenty text, Sell number becomes Twenty number, Sell date becomes Twenty date. Twenty requires all custom fields to exist before CSV import; we create them during the schema setup phase.

Zendesk Sell Line Items attach to Deals and represent products or services with quantity and price. Twenty does not have a distinct Line Item object as of the current release. We map Line Item data (product name, quantity, unit price, total) to a custom field set on the Opportunity record, or flag the customer to decide whether to denormalize as a text summary or split into separate Opportunity records per product.

Zendesk Sell Users (sales reps, admins) export with email, role, and territory. We map Users to Twenty Members by email match. Territory assignments are flagged as a configuration step since Twenty's workspace Members do not have a native territory field. The admin re-creates territory-based routing in Twenty's filters or custom fields after migration.

Tags in Zendesk Sell are labels applied to Contacts, Deals, and Leads. We migrate Tags as-is onto the equivalent Twenty record. Note that Twenty handles tag-based filtering through its standard filter and view system, which may differ from Sell's tag segmentation UX.