Migrate from PipelineManager to Pipedrive

PipelineManager Pipelines map directly to Pipedrive Pipelines. We extract the Pipeline name, ordered Stages, and stage probability values from PipelineManager during discovery and configure matching Pipelines in Pipedrive before Deal migration begins. Stage order is preserved by setting the PipelineManager stage sequence index as the Pipedrive stage order field. If PipelineManager has more Pipelines than the destination Pipedrive plan supports, we prioritize active Pipelines and flag archived ones for review.

PipelineManager Deals map to Pipedrive Deals. We migrate deal title, value, stage (resolved to Pipedrive Pipeline stage by name match), owner (resolved by email to Pipedrive User), expected close date, created date, and modified date. Closed-Lost and Closed-Won status maps directly to Pipedrive's closed won and closed lost stage values. Any PipelineManager custom fields on Deals transfer to Pipedrive custom fields created before import.

PipelineManager Stages within a Pipeline map to Pipedrive Stages by name. We preserve stage order using PipelineManager's sequence index. Stage probability percentages transfer to Pipedrive's stage probability field. If PipelineManager stages do not have exact name matches in Pipedrive, we flag them for the customer to confirm before migration runs, avoiding silent stage mismatches.

PipelineManager People records map to Pipedrive People. We migrate name fields (first_name, last_name), email address, phone number, job title, and any PipelineManager custom fields as Pipedrive custom fields. People records without a last_name are flagged for the customer's admin to complete before import because Pipedrive requires a name value on Person records. A duplicate detection pass runs on email before import to prevent duplicate Person records.

PipelineManager Companies map to Pipedrive Organizations. We migrate the company name, website, phone, address fields, and custom fields. Organization is created before Person import so that the Organization lookup is satisfied at Person insert time. If a PipelineManager Company has no name, we use the domain from any associated People records as a fallback name and flag it for admin review.

PipelineManager Activities map to Pipedrive Activities grouped by type (Call, Meeting, Task, Email, Note). We preserve the activity type, timestamp, duration, notes body, and any linked Deal or Person association. Pipedrive API rate limits require activity migration in batches of 500 records per request with exponential backoff on 429 responses. Activity history is migrated after Deals and People to ensure the parent record lookup succeeds.

PipelineManager file attachments map to Pipedrive Files attached to the corresponding Deal or Person record. We preserve original filenames and file type during transfer. Files without an associated Deal or Person are attached to the most recently modified related record or flagged for the customer's admin to assign. Pipedrive's file storage limits vary by plan tier; we confirm storage capacity before migration and flag oversized file sets for the customer to address.

PipelineManager custom fields on People, Companies, and Deals map to Pipedrive custom fields on the equivalent object. We create all custom fields in Pipedrive before migration begins, using the same field label and compatible field type (text, number, date, dropdown). If PipelineManager uses a field type that has no direct Pipedrive equivalent, we store the value as a text field and note the original type in the mapping workbook. Custom field names must match exactly (case-insensitive) for import mapping to succeed.

PipelineManager Users map to Pipedrive Users by email address. We extract every distinct owner email from Deals, People, and Activities and match against the destination Pipedrive User list. Users without a matching Pipedrive account go to a reconciliation queue; the customer's admin provisions any missing Pipedrive Users before record migration proceeds. Inactive PipelineManager users are mapped to inactive Pipedrive Users if deal history attribution must be preserved.

PipelineManager allows Deals to be linked to People records independently of Company linkage. In Pipedrive, a Deal's Person association is managed through the Person on a Deal record. We resolve the association by matching the PipelineManager People reference to the migrated Pipedrive Person by email and create the Pipedrive Person-Deal link during migration. If a PipelineManager Deal has no linked People, we import the Deal as a standalone Pipedrive Deal and flag it for the customer to link a Person manually.

PipelineManager Deals linked to Companies map to Pipedrive Deals linked to Organizations. We resolve the PipelineManager Company reference to the migrated Pipedrive Organization by company name match and set the OrganizationId on the Pipedrive Deal. If PipelineManager has a Deal linked to a Company that does not exist in Pipedrive, we import the Deal first and note the orphaned OrganizationId for post-migration resolution.

PipelineManager tags on Deals and People map to Pipedrive Labels. Labels in Pipedrive exist independently per entity type (People, Organizations, Deals). We create Labels matching the PipelineManager tag names and apply them to the corresponding migrated records. If PipelineManager uses a single tag taxonomy across all record types, we replicate the same label set per Pipedrive entity and note the multi-entity scope in the mapping workbook.