Migrate from Sales Journey to Pipedrive

Sales Journey Contact records map directly to Pipedrive Person objects. Standard fields (name, email, phone, company association) transfer with direct field mapping. The HubSpot-style company link on Contact resolves to a Pipedrive Organization record using the company name as the dedupe key. Any Sales Journey contact without an associated company creates a Person without an Organization link; we flag these for manual review before final import.

Sales Journey Company records map to Pipedrive Organization. Standard address, industry, and size fields map to Pipedrive's address block and label fields. The Organization is created before Person import so that the Organization ID is available as a lookup reference at Person insert time. If Sales Journey stores multiple contacts per company, each Person gets the same Organization ID after dedupe resolution.

Sales Journey Deal records map to Pipedrive Deal with stage, value (amount), and owner preserved. Pipeline stage names differ between platforms so we build a stage mapping table during scoping before migration. Close date and probability percentage transfer to Pipedrive's close_date and probability fields. If Sales Journey stores deal loss reason or custom fields on Deals, these map to Pipedrive custom fields created in the destination account before import.

Sales Journey Lead records may represent a different lifecycle state than Pipedrive expects. We assess the Lead model during discovery. If Sales Journey uses Leads for unqualified prospects, we map them to Pipedrive Leads. If Sales Journey treats Leads as a simple flat list of contacts, we may merge them into Person records. The decision depends on the customer's use of Lead-specific fields like lead source, score, or status. We preserve any lead score or status values as Pipedrive custom fields if the customer's Pipedrive tier supports them.

Sales Journey email engagement records migrate to Pipedrive Email activity entries. Email subject, body, sender, recipient, and timestamp transfer directly. We link each Email to the corresponding Person and optionally to the related Deal if the Sales Journey email record includes a deal association. If Sales Journey engagement history includes email open or click behavioral signals, we capture these in a Pipedrive custom field rather than expecting Pipedrive's native tracking to preserve the source signal.

Sales Journey call engagement records map to Pipedrive Call activity entries. Duration, call outcome, phone number, and timestamp migrate. We link calls to the Person record via the WhoId and to any associated Deal or Organization via the WhatId. Call disposition from Sales Journey maps to a custom field or label in Pipedrive if the platform supports it on the current tier.

Sales Journey meeting records migrate as Pipedrive Activities with a meeting type indicator. Start time, duration, title, location, and attendee list transfer. Attendees map to Person records in Pipedrive using email as the dedupe key. We preserve the chronological order of meetings by setting the Activity timestamp to match the original Sales Journey value.

Sales Journey note records map to Pipedrive Notes attached to the relevant Person, Organization, or Deal. Note content transfers as plain text. If the Sales Journey note includes any formatted content or attachments, we handle attachments as a separate file export step (see Attachments below) and flag formatted content for manual review if rich text formatting cannot be preserved through the import format.

Sales Journey custom fields on any standard object map to Pipedrive custom fields of the matching type. We audit every custom field discovered during discovery export, including any that are not immediately obvious during the initial scoping conversation. Pipedrive supports custom field types including text, number, date, dropdown, multi-checkbox, and address. We create the equivalent custom fields in the destination Pipedrive account before record import begins.

Pipeline stage configuration from Sales Journey, including stage names, stage order, and win/loss definitions, maps to Pipedrive Pipeline stages. Each Sales Journey pipeline becomes a Pipedrive Pipeline. Stage-level probability percentages transfer to Pipedrive stage probability settings. We configure Pipedrive pipelines during the setup phase before any Deal records are imported.

Owner assignment on Sales Journey records (Contacts, Companies, Deals, Activities) exports as a user reference. We map Sales Journey owner IDs to Pipedrive User IDs using an email-based cross-reference table. Any Sales Journey Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner lookup must resolve before Deals and Activities import because Pipedrive requires an OwnerId on those records.

File attachments stored within Sales Journey records may require a separate export step if they are not included in the standard record export. We identify attachment storage location and file count during scoping. If attachments are exportable as files, we import them into Pipedrive using the Files feature linked to the relevant Person, Organization, or Deal record. If attachments cannot be extracted from Sales Journey via export or API, we flag this in the scoping report and recommend a manual export from the Sales Journey UI as a parallel activity.