Migrate from PipelinePRO to Pipedrive

PipelinePRO Contact records export as CSV with name, email, phone, and custom field columns. We map these to Pipedrive Person records. The email address serves as the dedupe key during import. Custom properties need explicit field-by-field mapping before import; any PipelinePRO custom columns without a Pipedrive equivalent are created as custom fields in Pipedrive before migration begins.

PipelinePRO Company records map to Pipedrive Organization records. Company quality depends on how consistently users populated the company field on contacts; we flag sparse organizations for review before import. Organization is imported before Person so that the organization_id can be resolved and linked when Persons are inserted.

PipelinePRO Deal records export with name, value, stage, owner, and expected close date. We map stage names between PipelinePRO and Pipedrive using a customer-reviewed mapping table before bulk record migration. The deal owner resolves by email match against Pipedrive Users provisioned before migration.

PipelinePRO Lead records function as early-stage contacts with their own status field. We preserve lead status as a custom property on the Pipedrive Lead record because Pipedrive maintains a separate Lead object distinct from Person. The original PipelinePRO lead status migrates as a custom text or picklist field.

PipelinePRO uses customizable pipeline boards with drag-and-drop stage definitions. We extract the pipeline name and stage list and configure the equivalent pipeline structure in Pipedrive before any Deal records import. Pipedrive allows multiple pipelines from Essential tier, matching PipelinePRO's multi-board capability.

Stage names and order are configurable per pipeline in PipelinePRO. We map source stages to destination stages using a customer-reviewed mapping table. Stage probability percentages are set on Pipedrive stages to match the original deal close likelihood. Stage configuration happens before Deal migration to prevent import failures from missing stage values.

PipelinePRO custom fields exist per object but have no bulk schema export. We ask customers to provide a screenshot or list of custom field names and their types before migration so we can create matching fields in Pipedrive. Field types map from PipelinePRO text, number, date, and picklist to their Pipedrive equivalents. Custom field creation is validated before Person and Deal imports begin.

Tags on PipelinePRO contacts and deals export as comma-separated values in the CSV. We parse these and apply them as native Labels in Pipedrive. Labels in Pipedrive attach to Persons, Organizations, Deals, and Leads, providing equivalent categorization across the migrated record types.

PipelinePRO user accounts with names and email addresses export as a simple list. We map these to Pipedrive User records and reassign owned deals and contacts accordingly. Owner resolution happens by email match; any PipelinePRO owner without a matching Pipedrive User is flagged in a reconciliation queue before Deal migration.

Static notes attached to PipelinePRO contact or deal records export as text fields in the CSV. We preserve these as Pipedrive Note records linked via ContentDocumentLink to the parent Person, Organization, or Deal. Rich-text formatting from PipelinePRO is simplified to plain text during import.

Uploaded files attached to PipelinePRO deals or contacts export via download links if accessible. We retrieve accessible files and upload them to Pipedrive attached to the corresponding Deal or Person record. Any documents we cannot retrieve due to access restrictions are flagged for manual handling during the migration scoping call.