Migrate from Flash Lead Sales to Pipedrive

Flash Lead Leads are a single object carrying stage, source, tags, owner, and history. We split at migration time: Leads with stage values indicating an open, unqualified status map to Pipedrive Lead; Leads with a closed-won status or with invoice records attached map to Pipedrive Person (contact) with the Organization resolved from the contact's company name. We preserve the original Flash Lead stage in a custom field fls_original_stage__c on both Lead and Person for audit. Owner resolution uses email match against Pipedrive Users.

Flash Lead Contacts with a company name map to Pipedrive Person with the Organization resolved via the company field. If the Organization does not exist in Pipedrive, we create it during the Contacts phase. Contacts without a company name migrate as standalone Person records. Email address is the dedupe key; duplicate emails on import are flagged for manual resolution.

Flash Lead stage names are user-defined and vary by account. We extract the full stage list from the CSV during discovery, map each stage to a Pipedrive Lead Status value, and create a custom field fls_original_stage__c to preserve the exact Flash Lead stage label for reporting continuity. Any stage-specific automation rules cannot be migrated and are listed in the automation inventory handoff document.

Flash Lead pipeline stages map to Pipedrive Deal Stages. We configure a Pipedrive Pipeline before migration, create Stage entries matching the source stage names and ordering, and assign probability percentages from the Flash Lead stage definitions. If the customer uses multiple Flash Lead pipelines, we create multiple Pipedrive Pipelines with distinct stage sets.

Flash Lead Lead Sources (Facebook, Instagram, Referral, Purchased List, etc.) migrate as a custom field on the Pipedrive Lead or Person record. We create the custom field during schema setup with a picklist of the exact source values found in the export. New source values encountered post-migration require manual field-value addition in Pipedrive settings.

Flash Lead tags migrate as a multi-select custom field on Lead and Person. Pipedrive's multi-select picklist supports multiple selections per record. If the number of unique tags exceeds what Pipedrive's picklist can accommodate at the Lite tier (30 fields per company), we recommend the Enterprise tier or advise splitting tags into two fields (e.g., lead_type and segment) during scoping.

Flash Lead Team Members map to Pipedrive Users. We resolve by email match. Any Flash Lead owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before the record migration phase begins. Inactive Flash Lead users map to inactive Pipedrive Users so that historical owner assignments on records are preserved.

Flash Lead Invoices tied to deals migrate as Pipedrive Deals with custom fields capturing invoice number, amount, status, and issue date. Invoice PDFs do not transfer through CSV export; we flag any attachments in the migration report so the customer can re-upload documents manually or through a document management integration post-migration.

Stage transitions in Flash Lead are stored as activity log entries, not discrete fields. The standard CSV export contains only the current stage. We request the full activity log export during discovery and reconstruct stage progression as Note records or custom activity log entries on the Pipedrive Deal, tagging each entry with a fls_activity_type__c value of Stage_Transition and the original timestamp. Time-in-stage metrics are preserved for deal velocity reporting.

Facebook Messenger and Instagram DM threads export from Flash Lead as flat conversation text attached to the contact record. Thread structure, branching, timestamps, and read receipts do not transfer. We attach the full conversation log as a Note on the corresponding Pipedrive Person record and note the limitation in the migration report so the customer can assess whether conversation history is business-critical for their use case.