Migrate from Data Team DDS to Pipedrive

Data Team DDS contacts migrate to Pipedrive People. Pipedrive's Person object stores first name, last name, and a primary email address in a dedicated field; additional email addresses are stored in an emails array. All standard contact properties map directly to Pipedrive Person fields or custom fields created during schema setup. Duplicate detection in Pipedrive uses email as the primary matching key.

Data Team DDS company records map to Pipedrive Organizations. Pipedrive Organizations do not have a native parent-child hierarchy — if your Data Team DDS instance uses hierarchical company structures, the child companies migrate as separate Organizations and you choose whether to link them via custom fields or relationship notes. Multi-company contacts in Data Team DDS map to one primary Organization and additional Organizations linked via Person records.

Data Team DDS deals map to Pipedrive Deals with a direct pipeline-to-pipeline and stage-to-stage value mapping. Pipedrive allows multiple currencies per account with a default set at account level and per-deal currency override on Professional and above plans. Close date, deal value, and owner ID migrate directly; probability is calculated from Pipedrive stage settings unless a custom probability field exists in Data Team DDS.

Each Data Team DDS pipeline creates a corresponding Pipedrive pipeline. Pipedrive pipelines can be reordered and renamed in the UI post-migration. Stage names in Pipedrive are stored as free-text strings tied to the pipeline_id — stage order and win/loss flags are set per stage in Pipedrive's pipeline settings and must be configured there as well as mapped from Data Team DDS stage definitions.

All Data Team DDS engagement types — calls, emails, meetings, and notes — map to Pipedrive Activity objects. Pipedrive uses a single Activity entity with a type enum field to distinguish between call, email, meeting, and task. Original timestamps, owners, and subject lines are preserved. Notes without a specific activity type map to Pipedrive Notes attached to the parent Person, Organization, or Deal via the activity's parent_id field.

All Data Team DDS custom fields must be pre-created in Pipedrive before the migration run. Pipedrive generates a unique 40-character hash key per custom field per account — the mapping references these keys, not field names. Field type mapping is type-aware: Data Team DDS pick-list fields map to Pipedrive select custom fields, date fields to date custom fields, and numeric fields to number fields. Custom field values on records are loaded after field definitions are in place.

Pipedrive does not store files natively. Files attached to Data Team DDS records migrate as external file references stored in a custom URL field on the related Person, Organization, or Deal, or as Pipedrive Notes containing links to the source files. You can connect a cloud storage integration in Pipedrive post-migration and re-link files. If Data Team DDS provides direct file download URLs, FlitStack can re-upload files to your connected cloud storage and update the links.

Data Team DDS owner IDs are resolved to Pipedrive users by email address match. Unmatched owners are flagged before the migration run — you can invite those users to Pipedrive first or assign their records to a fallback owner. Inactive Data Team DDS users become inactive Pipedrive users unless you choose to reassign their open records before migration.

Data Team DDS leads without an associated deal may map to Pipedrive's dedicated Lead object (available on Advanced and above plans). If your Data Team DDS instance uses a single contact model without a separate lead concept, all contacts land as Pipedrive People and you use Pipedrive's Activity log to track pre-conversion engagement history rather than a separate Lead record.

Tags from Data Team DDS migrate as Pipedrive Tags. Pipedrive Tags are stored as an array on each entity (Person, Organization, Deal) and can be searched and filtered in list views. Tags with special semantic meaning in Data Team DDS — such as segmentation tags used in automations — should be reviewed post-migration as Pipedrive Tags do not trigger automations by themselves.