Migrate from LeadPrime to Pipedrive

LeadPrime Leads split into Pipedrive based on conversion status. Unconverted Leads with no associated Deal map to Pipedrive Lead via the Lead Inbox. Converted Leads with a linked Deal or Contact map to Pipedrive Person. We preserve the original LeadPrime status, source, owner assignment, and create_date. Any LeadFinder enrichment results already written to the lead (verified emails, phone numbers) migrate as custom fields on the Pipedrive record since enrichment data lives in the record, not in the credit token.

LeadPrime Contacts map directly to Pipedrive Person. Name, email, phone, address, and custom properties transfer 1:1. The parent Company reference resolves to a Pipedrive Organization record that we create before Contact import. If LeadPrime Contact records exist without a linked Company, they import as standalone Persons; the customer admin decides whether to create an Organization retroactively.

LeadPrime Company records map 1:1 to Pipedrive Organization. Company name, domain/website, industry, address, and custom fields transfer directly. Organization is created before Contact import so that the OrganizationId relationship is satisfied at insert time. Duplicate Organizations (same domain) are deduplicated using the company domain as the key.

LeadPrime Pipelines (if multiple exist) map 1:1 to Pipedrive Pipelines. Each LeadPrime pipeline becomes a Pipedrive Pipeline with the same name and stage sequence preserved. Stage order and stage names transfer; probability percentages map to Pipedrive stage probability fields with rounding to the nearest whole number. Pipedrive supports multiple pipelines at all paid tiers.

LeadPrime Pipeline Stages map to Pipedrive Pipeline Stages within the corresponding Pipeline. Stage name, position in sequence, and stage-specific flags transfer. Any stage-level routing triggers in LeadPrime (e.g., auto-assign on stage entry) are flagged as automation items in the handoff document because Pipedrive Workflow Automation handles these at the object level rather than the stage level.

LeadPrime Deals map to Pipedrive Deals. The Deal title, value (weighted or base), expected close date, owner, and linked Contact and Company transfer. The source pipeline stage maps to the corresponding Pipedrive Pipeline Stage within the matched Pipeline. Deals without a linked Organization create a placeholder Organization in Pipedrive during import and are flagged for the customer admin to consolidate.

LeadPrime Users (sales reps, admins, managers) map to Pipedrive Users by email address match. Active/inactive status and role assignments are preserved. Users without a matching Pipedrive account are held in a reconciliation queue and the customer provisions the User in Pipedrive before migration resumes. OwnerId on Deals, Leads, and Persons is resolved to the Pipedrive User id at migration time.

LeadPrime engagement records (calls, emails, meetings, tasks, notes) migrate to Pipedrive Activity records with the correct type field (call, email, meeting, task, note). Activity content, timestamp, duration, and disposition transfer directly. Each Activity is linked to its parent record (Person, Organization, Deal, or Lead) via Pipedrive's polymorphic key fields. If LeadPrime stores activities only against Leads (not Contacts), unconverted Activities attach to Pipedrive Leads; converted Activities attach to Persons and Deals.

LeadPrime custom fields on Leads, Contacts, Companies, and Deals are read during scoping, mapped to Pipedrive equivalent field types (text, number, date, dropdown, multi-select, checkbox), and created in Pipedrive before data import begins. Pipedrive's custom field UI requires admin access. Multi-select picklists in LeadPrime map to Pipedrive multi-select fields. Date fields, numeric fields, and dropdowns map to their Pipedrive equivalents. Any custom field without a Pipedrive equivalent is flagged as a candidate for a label field or custom note.

LeadPrime tags are flat string labels applied across records. Pipedrive does not have a native Tags object; tags map to Pipedrive Labels (an optional org-level feature) or to a custom multi-select picklist field that we create before migration. We export all tag assignments per record and apply them during import. If LeadPrime tags have hierarchical structure, we flatten them to a dot-separated string in Pipedrive. The customer chooses between Labels and custom field during scoping.

LeadPrime's Round Robin, Shark Tank, Hybrid, and territory-based distribution rules are configuration, not data records, and have no equivalent in Pipedrive's object model. We export the full rule definitions during scoping (rule type, participating users, daily caps, territory filters, priority weights) and deliver them as a structured configuration document. The customer's Pipedrive admin rebuilds routing logic using Pipedrive's Workflow Automation (for trigger-based assignment) and manual Round Robin spreadsheet tools if the rule type requires rep rotation. This is explicitly outside data migration scope.