Migrate from Leadfwd to Pipedrive

Leadfwd Contacts map directly to Pipedrive People records. The Salesforce Contact ID stored in Leadfwd is not reusable in Pipedrive; we use email address as the primary deduplication key. Any Leadfwd custom Contact fields that synced through the Salesforce pipeline map to Pipedrive custom fields on the Person object. Custom field mapping depends on Salesforce field-level visibility—if a field was hidden from the Leadfwd connected app profile, it will not appear in our extraction and must be added manually in Pipedrive post-migration.

Leadfwd treats Leads and Contacts as equivalent enrollment targets via Salesforce. We extract Lead records from Salesforce using the standard Salesforce Lead object fields. When imported into Pipedrive, Leads with email addresses will automatically generate linked Person and Organization records if Pipedrive's duplicate detection is configured accordingly. The original Salesforce Lead ID is preserved in a custom field for audit traceability.

Leadfwd Company records synced from Salesforce map to Pipedrive Organizations. The Company ID is preserved in a custom field for cross-reference. Any custom Company properties that passed through the Salesforce API pipeline map to Pipedrive Organization custom fields. Parent-company hierarchy from Salesforce maps to Pipedrive's Organization parent relationship if present in the source data.

Leadfwd does not natively manage Deals; Deals in this migration context originate from Salesforce Opportunities synced into Leadfwd for enrichment and enrollment context. We map Salesforce Opportunities to Pipedrive Deals, preserving stage, value, close date, owner, and any linked custom fields. Pipeline and stage mapping requires a pre-migration configuration step in Pipedrive where the customer defines their Deal stages to match the source pipeline structure.

Leadfwd Sequences define automated outreach journeys across email, LinkedIn, and SMS steps. Pipedrive has no native sequence enrollment engine. We export the full sequence structure including step order, delay rules, action types, and channel metadata as a written inventory document. The customer's admin rebuilds Sequences in Pipedrive using Pipedrive Workflows and Tasks or a third-party sales engagement tool. Sequence metadata is preserved for documentation purposes only and does not constitute a transferable automation.

Enrollment records track which Contact is enrolled in which Sequence at what step. We export enrollment status (active, paused, completed, bounced), current step index, last activity date, and enrollment start date. Each enrollment is written as a note on the Person record in Pipedrive indicating the sequence name, status at time of export, and a flag stating 'requires re-enrollment in destination platform.' Enrollments cannot resume in Pipedrive because the execution context is Leadfwd-specific.

Icebreakers are personalized conversation openers generated per Contact using LinkedIn profile data and ChatGPT. We export the generated text, source LinkedIn URL, and generation timestamp as a Note attached to the Person record in Pipedrive. The AI-generated variants are Leadfwd-specific and do not represent a transferable data format; they serve as historical context for sales reps rather than active personalization tokens. Icebreaker generation does not replicate in Pipedrive.

Leadfwd engagement events (opens, clicks, replies, bounces) are logged as engagement events in Salesforce and synced to Leadfwd. We extract engagement events from Salesforce EmailMessage and Activity records and write them as notes or activity entries on the corresponding Person in Pipedrive. Deep event details such as which exact email body variant was opened are not preserved; engagement metadata (channel, timestamp, outcome) migrates. Call recordings associated with engagement calls cannot be exported from either platform and are explicitly scoped out.

Call engagements logged in Leadfwd and synced to Salesforce map to Pipedrive Call activities attached to the Person record. Call disposition, duration (CallDurationInSeconds), and outcome from Salesforce Activity records migrate to Pipedrive's call logging fields. Caller ID and recording URLs are not transferable and are scoped out of migration deliverables.

Meeting engagements from Leadfwd's calendar sync to Salesforce Events. We map Salesforce Events to Pipedrive Meeting activities attached to the relevant Person and linked Organization. Start time, end time, location, and attendees migrate. Meeting content, shared files, and video call links are not preserved.

Leadfwd creates Tasks for manual sales actions linked to Sequence steps. We export Task records with status, due date, assignee, and subject from Salesforce Activity records. Task logic (automated vs. manual trigger) does not transfer and must be reconstructed in Pipedrive. Overdue task flags migrate as Pipedrive task priority indicators.

Sender rotation configuration, mailbox authentication credentials (OAuth tokens, IMAP/SMTP credentials), and mailbox warming progress (warmth scores, daily send curves) are stored in Leadfwd's own infrastructure. These cannot be exported or replicated in Pipedrive. We clearly scope mailbox infrastructure out of migration deliverables. The customer must configure their email accounts fresh in Pipedrive's Settings > Email before sending from the new platform.