Migrate from Prospects CRM to Pipedrive

Prospects Contact maps to Pipedrive Person. The contact's name fields, email, phone, and address fields migrate directly. The primary company link maps to a Person-Organization relationship in Pipedrive — if no company is set in Prospects, the Person lands unlinked and can be associated manually or via deal linkage.

Prospects Company maps to Pipedrive Organization. Company name, domain, industry, employee count, and address fields migrate directly. Prospects' parent-company hierarchy maps to Pipedrive's linked Organization field. Multi-company associations on a single contact in Prospects collapse to one primary Organization link in Pipedrive with additional associations surfaced via the Organization's Persons list.

Prospects Deal maps directly to Pipedrive Deal. The deal name, value (amount), stage, expected close date, owner (resolved by email), notes, and associated contact/company links all transfer. Pipedrive Deal requires a linked Organization or Person — orphaned Prospects deals without a primary company are flagged before migration so your team can decide whether to create a placeholder Organization or skip the deal.

Each Prospects pipeline stage maps to a Pipedrive pipeline stage by value. Stage names are preserved as stage labels. Probability percentages associated with stages in Prospects transfer as custom fields in Pipedrive since Pipedrive stages do not carry probability by default — your Pipedrive admin sets stage probabilities per pipeline in Settings.

Prospects owner IDs resolve to Pipedrive users by email match. All Prospects users must have a corresponding Pipedrive user account created before migration — FlitStack flags unmatched owners and either creates a fallback assignee or pauses for your team to invite the missing user. Unresolved owners default to the migration-admin user.

Prospects activity records — calls, meetings, tasks — map to Pipedrive Activities with the original timestamp, owner, and subject preserved. Activity type (call, meeting, task) maps to Pipedrive's activity_type field. Email activities from Prospects migrate as Task activities with type='email'. Activity completion status maps to Pipedrive's done flag.

Prospects notes migrate to Pipedrive Notes attached to the parent Person, Organization, or Deal record. Rich-text formatting from Prospects notes is preserved where technically feasible during the transfer. In cases where HTML formatting cannot be reliably rendered within Pipedrive's note field, a plain-text fallback is automatically applied to ensure content legibility and prevent display issues in the destination system.

Prospects products migrate to Pipedrive Products — name, SKU, unit price, and description transfer. Pipedrive Products are a separate module not directly linked to Deals unless you use Pipedrive's deal-product association feature. Prospects' stock-quantity and inventory-level data has no Pipedrive equivalent and is not migrated.

Prospects quotes and orders do not have a native Pipedrive equivalent. Quote data (line items, totals, status, PDF URL) merges into the linked Deal record using custom fields on the Pipedrive Deal — FlitStack creates the custom fields during setup and populates them from Prospects quote records. You will need to rebuild quote templates in Pipedrive's Smart Docs (Professional+) or a third-party document tool.

Every Prospects custom field migrates to a corresponding Pipedrive custom field on the equivalent object (Person, Organization, Deal). Pipedrive auto-creates fields during import if the name and field type match — FlitStack pre-creates all custom fields in Pipedrive before migration so data lands in the correct schema. Pick-list custom fields require value-by-value mapping between Prospects options and Pipedrive options.

Prospects file attachments linked to contacts, companies, or deals download and re-upload to Pipedrive Files, maintaining the original file name and attachment link. File size limits apply — Pipedrive's default maximum file size is 50MB; files exceeding this are flagged and require manual handling or compression before upload.

Prospects stock-level and inventory-quantity data has no equivalent in Pipedrive's data model. This data is not migrated. If you need inventory context in Pipedrive, you would need to build a separate inventory lookup (via a custom object or an external tool linked through Pipedrive's API).