Migrate from Pipedrive to Twenty CRM

Pipedrive Persons map directly to Twenty People records. We extract name, email, phone, address, and any custom field values, then resolve the custom field hash keys to human-readable labels for correct destination field assignment. Person-Organization links are preserved as relations in Twenty, and any Person-level tags migrate as Twenty tag strings attached to the People record.

Pipedrive Organizations map to Twenty Companies. Domain, industry, size, address, and custom field values transfer directly. Multi-person organizations are resolved by maintaining the People-to-Company relation established in Pipedrive.

Pipedrive Deals map to Twenty Opportunities. Deal title becomes Opportunity name, monetary value transfers directly, and expected close date maps to the due date. Stage assignment is resolved by matching the Pipedrive stage name to the equivalent stage in Twenty's target pipeline. Loss reason and won reason from Pipedrive custom fields migrate to Twenty custom fields.

Pipedrive Leads are a separate pool from Persons. In Twenty's model, unqualified prospects live as People records with a Pipeline Stage assigned. We merge Pipedrive Leads into Twenty People records, preserving all Lead-level custom fields and tags. The customer's admin sets the target pipeline stage for unqualified records during scoping.

Pipedrive Activities (Tasks, Calls, Meetings) map to Twenty Task records and timeline events. We preserve the activity type, due date, assigned owner, and any note body. Call duration and disposition migrate to custom fields. Activity records are linked to the parent People or Opportunity record by resolving the Pipedrive person_id and deal_id references to their migrated Twenty IDs.

Pipedrive Notes with optional person, organization, or deal attachments map to Twenty Comment records linked to the corresponding People or Opportunity. We preserve note body text and attachment references, re-linking to the migrated parent record by resolved ID.

Pipedrive Products (standalone items with SKU, pricing, and unit) map to Twenty Products. Product pricing, currency, and unit information transfer directly. Deal-Product associations migrate as Opportunity-line-item relations in Twenty, preserving quantity and price against each opportunity.

Pipedrive Pipelines become Twenty Pipelines. We read the pipeline definition (stage names, order, probabilities) from Pipedrive and create matching Pipelines in Twenty before migrating any Deals. If the customer uses multiple Pipelines in Pipedrive, each becomes a separate Twenty Pipeline, and Deal assignments are preserved by name match.

Pipedrive Stage names and positions map to Twenty Stage values within the target Pipeline. Stage probabilities transfer as percentages, and the stage order is preserved for correct pipeline visualization in Twenty.

Pipedrive custom fields exist on Persons, Organizations, Deals, and Products. Pipedrive assigns each custom field a 40-character hash key unique per account. We read the hash-to-label mapping from the source account, resolve the human-readable field name, and create or map to the corresponding custom field in Twenty by label and data type. This prevents custom field data from landing in wrong columns or being dropped silently.

Pipedrive Users who own records, activities, and deals map to Twenty Users. We resolve by email address. The customer's Twenty admin provisions matching Users before migration begins; any Pipedrive Owner without a corresponding Twenty User is held in a reconciliation queue for admin action.

Pipedrive Tags are string labels applied to Persons, Organizations, Deals, and Products. We migrate tags as string arrays and apply them to the corresponding records in Twenty by exact name match. Tagged records re-link to the correct People, Company, or Opportunity by resolved ID.