Migrate from Sales Flow Technologies to Pipedrive

Sales Flow Contacts map to Pipedrive Person records as the primary contact object. Company data from the Contact record (company name, domain, industry) splits into a separate Pipedrive Organization record with a Person-Organization link. Email, phone, LinkedIn profile URL, and custom fields migrate as Person fields. This split is necessary because Pipedrive separates individual contacts from the business entities they belong to, and creating the Organization first resolves the lookup dependency at Person insert time.

Sales Flow Prospect Lists are named groupings of Contacts used for targeted outreach campaigns. We export list membership as a structured CSV with Contact email and list name, then create Pipedrive Tags corresponding to each list name. When Persons are created during migration, tag assignment is resolved by email match so the grouping is immediately available for filtering and segmenting in Pipedrive's pipeline view. List ordering within Sales Flow does not transfer as Pipedrive does not support ordered tags.

Sales Flow Sequences define the cadence and channel steps (LinkedIn connection request, follow-up email, InMail, delay intervals) for a group of Contacts enrolled in a campaign. Sequence step ordering and timing data migrate as structured activity notes on the related Pipedrive Deal or Person. Each step becomes a chronological note entry with step type, template reference, and days-since-previous-step preserved. The step ordering provides rep context on prospect engagement history without replicating the cadence as an active Pipedrive automation.

Sales Flow Campaigns bundle multiple Sequences under a single outreach objective. We map Campaign names to Pipedrive Deal names, Campaign-level date ranges to Deal expected_close_date or custom date fields, and Campaign status to Deal stage. The Deals represent the business outcomes (a deal, a project, a renewed contract) that the outreach sequences were designed to move. Channel routing logic and A/B testing configurations do not transfer as Pipedrive does not model these concepts natively.

Sales Flow Workflows define conditional branching logic for prospect responses and follow-up actions (e.g., 'if no reply after 3 days, send template B'). The workflow builder configuration is not exposed via CSV or API and cannot be extracted programmatically. We produce a written Workflow Migration Summary documenting every conditional rule, step order, delay interval, and trigger condition from the source system so the customer's admin can manually reconstruct equivalent automation in Pipedrive's Workflow Automation builder. This is the most significant scope item that does not result in migrated data.

Sales Flow email engagement records migrate as Activity records in Pipedrive linked to the Person or Deal. Email subject, body content, and sent timestamp transfer as structured activity entries. Inbound email content may be incomplete if the thread is stored on a connected email provider rather than Sales Flow. We flag any engagement records where email_body is null or truncated in the source export as partial records requiring manual review.

Sales Flow call engagement records migrate as Pipedrive Activities with activity type set to Call. Call duration, disposition, and any notes logged in Sales Flow transfer to corresponding fields on the Pipedrive Activity. We resolve the Person link by email match and the Deal link by the enrollment record associated with the call.

Sales Flow meeting engagement records migrate as Pipedrive Activities with activity type set to Meeting. Meeting title, date and time, duration, and location transfer to the corresponding fields. Attendee information from Sales Flow migrates as a note entry on the Activity if the attendee email addresses can be resolved to existing Person records in the destination.

Sales Flow note engagements migrate as Pipedrive Note records linked to the Person, Organization, or Deal. Note content, author, and timestamp transfer directly. We resolve the parent record link using the email address and company name fields on the source note record. Notes without a resolvable parent record are held in a reconciliation queue for the customer's admin to resolve before final import.

Sales Flow provides per-sequence and per-step open rates, reply rates, and connection acceptance rates. These metrics have no native equivalent in Pipedrive's standard object model. We export the metrics as a structured CSV and import them as custom fields on the Person object (e.g., sequence_open_rate__c, sequence_reply_rate__c) and Deal object (e.g., campaign_connection_rate__c). These custom fields appear in Pipedrive's reporting for reference but do not drive any native Pipedrive automation or scoring logic.

Sales Flow User accounts define who on the team is running outreach and are mapped to Pipedrive User records by email address match. Role labels (Admin, Standard) from Sales Flow do not transfer as Pipedrive role and permission set assignments are a separate administrative configuration step. We flag any Sales Flow User without a matching email in the destination for the customer's admin to provision before the final import phase.

Sales Flow Inbox messages represent the conversation thread between the rep and the prospect across LinkedIn and email. These messages are stored in LinkedIn's infrastructure and are not accessible via Sales Flow export. LinkedIn conversation history cannot be retrieved through any export path. We document this gap in the migration scope and advise the customer to retain access to the original LinkedIn account for reference during a defined transition window. No equivalent import is possible in Pipedrive.