Migrate from Twenty CRM to Pipedrive

Twenty Companies map to Pipedrive Organizations using domain as the dedupe key. The Twenty domain field becomes Pipedrive's Website field. Organization is imported first because People records in Twenty carry a companyId foreign key, and Pipedrive's Person (Contact) model similarly requires an Organization lookup. We pre-validate domain values in Twenty to avoid silent failures when domain is missing or malformed.

Twenty People map to Pipedrive Persons using email as the unique reference key. First name, last name, phone, job title, and companyId (resolving to the Organization record inserted in the prior phase) migrate directly. We match companyId to Pipedrive's linked_organization_value field during import. Any People record missing a companyId is imported as a Person without an Organization link for the customer's admin to resolve post-migration.

Twenty Opportunities map to Pipedrive Deals. The pipeline and stage names from Twenty become Pipedrive pipeline stages, which we pre-create before migration. Close date, amount, and probability migrate to Pipedrive's close_date, stage_id (resolved by stage name match), and success_probability fields. The Opportunity's linkedCompanyId resolves to the Organization's Pipedrive ID, and the linkedContactsIds resolve to Person IDs.

Twenty Tasks map to Pipedrive Activities. Pipedrive stores all activities (calls, emails, meetings, tasks) in a unified activity object with a type field. We classify Twenty Tasks by their title or type indicator and write them as Pipedrive Activities with the corresponding type (call, email, meeting, task). Due date, assignee (resolved by owner email match), and completion status migrate. Task relations to People, Companies, or Opportunities resolve to Pipedrive's deal_id and person_id reference fields.

Twenty Notes migrate to Pipedrive Activities with type=note. Note body content maps to the Pipedrive Activity's note field. We link Notes to their target record (Person, Organization, or Deal) via the appropriate Pipedrive reference field by resolving the target record ID from the prior import phases. Note creation timestamps preserve the original activity date for timeline ordering.

Twenty Custom Objects have no native Pipedrive equivalent — Pipedrive supports custom fields on Person, Organization, and Deal but not custom record types. We handle this gap by cataloging every Twenty custom object during scoping: for single-value attributes we design Pipedrive custom fields mapped to the source field, and for structured data (related records, multi-value fields) we propose a lookup approach using note-linked references or Pipedrive's custom field JSON storage pattern. The customer chooses the strategy during scoping and validates that the resulting custom field setup serves their reporting needs.

Twenty Owner references on People, Companies, and Opportunities map to Pipedrive Users resolved by email address. We extract every distinct owner email from the source records, match against the destination Pipedrive Users table, and flag any owner with no corresponding Pipedrive User for the customer's admin to provision before the main migration phase. OwnerId references on Deals and Activities resolve through the same User lookup.

Twenty Opportunities can link to multiple People records, while Pipedrive Deals link to a single primary Person plus additional linked contacts stored as Deal-Person relationship records. We handle this by importing the primary linked contact as deal.person_id and writing additional contacts as Pipedrive DealPerson records (the deal_id + person_id relationship entity) for each additional Twenty linked contact on the same Opportunity.

Each Twenty pipeline and its stage values map to a Pipedrive Pipeline with corresponding stage names. We pre-create Pipedrive pipelines and stages before migration so that Opportunity.stageId resolves correctly at import time. Closed-won and closed-lost stages from Twenty map to Pipedrive stage status values.

Twenty Tasks with an assignee map to Pipedrive Activities with an assigned_user_id resolved from the owner email. Tasks without an assignee in Twenty are imported as Pipedrive Activities with no assigned user for the customer's admin to route. Recurring task patterns in Twenty (if configured) are flagged as non-migratable since Pipedrive's automation handles recurring tasks rather than a native recurring flag.