Migrate from Flash Lead Sales to Salesforce Sales Cloud

Flash Lead Sales Lead records map directly to Salesforce Lead. Each record carries source, tags, current stage, owner assignment, and contact profile data. We extract all standard fields (first name, last name, email, phone, company) and preserve the original Flash Lead source label and tag list as custom properties on the Salesforce Lead record. Owner assignment resolves by matching the Flash Lead owner email to a Salesforce User record.

Flash Lead Sales Contact records map to Salesforce Contact. Contacts in Flash Lead carry customer profile data, purchase history, location, and conversation threads. We preserve the contact's related lead associations, phone, email, address, and any custom properties. Salesforce Contact requires an AccountId lookup, so we create an Account from the Contact's company name first, then attach the Contact to it during import.

Flash Lead pipeline stages are user-defined per account with no enforced schema. Stage names and probabilities from the platform extract to a mapping table that we produce during discovery. Each Flash Lead stage maps to a Salesforce Opportunity StageName value within a configured Sales Process. Stage-specific automation rules (e.g., triggers on entry to a specific stage) cannot migrate and are documented in the handoff report for the customer's admin to rebuild in Salesforce Flow.

Stage transitions in Flash Lead Sales are stored as activity log entries rather than a discrete stage-history table. Only the current stage is guaranteed to appear as a discrete field in the export. We extract the full activity log during discovery and denormalize the stage progression into a JSON blob stored in a custom Salesforce field on the Opportunity record (e.g., stage_history__c), preserving the sequence, timestamp, and owner of each transition. Deal velocity and time-in-stage metrics are therefore reconstructable in reports even though Salesforce does not have a native stage-history object.

Flash Lead Pro invoice records (amount, status, related deal, line items) map to Salesforce Order objects if the destination org includes Salesforce Orders. Invoice formatting and custom invoice fields require field-level mapping per the customer's template. If the destination Salesforce edition does not include Orders, we map to Opportunity with a custom invoice flag and store invoice metadata in a custom Opportunity field set. PDF attachments on invoices migrate as ContentDocument linked to the Order or Opportunity.

Flash Lead Sales team members with role-based access controls map to Salesforce User records by email match. Role hierarchy (owner, sales manager, sales rep) maps to Salesforce Role and Profile assignments, which the customer's admin configures in the destination org before migration begins. Any Flash Lead user without a matching Salesforce User email goes to a reconciliation queue for manual provisioning.

Flash Lead Sales tags are unlimited per lead and serve as a segmentation and filtering mechanism. Tags export as a comma-separated list per lead. We store the full tag list in a Salesforce custom text field on the Lead object (lead_tags__c) and optionally as a multi-select picklist if the tag count is below Salesforce's 500-value limit per field. Tag-based segmentation logic in Flash Lead automations does not migrate; the tag values are available for manual segmentation in Salesforce reports and campaigns.

Flash Lead Sales Lead Sources (Facebook, Instagram, Referral, Purchased Lists, etc.) map to Salesforce LeadSource standard field. If the Flash Lead account uses custom source labels not represented in the Salesforce LeadSource picklist, we extend the picklist with the additional values during schema setup before migration begins. Source attribution is preserved for campaign reporting and lead quality analysis.

Facebook Messenger and Instagram DM threads export from Flash Lead Sales as flat conversation text logs attached to the contact record. Thread branching, message timestamps, read receipts, and sender attribution are not preserved in the export. We attach the full conversation log as a text body on an EmailMessage record linked to the corresponding Salesforce Contact, with the channel noted as Social in the EmailMessage MessageDate field. The limitation is documented in the migration report so the customer can assess whether conversation history is business-critical for their use case.

Flash Lead Sales accounts using custom fields on leads or contacts map those custom fields to Salesforce custom fields on the equivalent object. We pre-create the destination schema including all custom fields, field types, and any lookup relationships before any data import. Custom object naming follows Salesforce __c suffix convention and preserves the API name from Flash Lead where possible. Any custom objects unique to the Flash Lead account are inventoried during discovery and mapped individually.

Flash Lead Sales deals (if present in the customer's account) map to Salesforce Opportunity. Deal name, amount, stage, owner, and related contact or company are mapped to Opportunity Name, Amount, StageName, OwnerId, and ContactId. The pipeline assignment from Flash Lead maps to a Salesforce Record Type and Sales Process that we configure before migration.

Flash Lead Sales automations (lead assignment, reassignment, email sequences, stage-change triggers) are stored as configuration rather than data. These do not migrate to Salesforce. We deliver a written inventory of every active Flash Lead automation with its trigger conditions, actions, and a recommended Salesforce Flow equivalent for the customer's admin or a Salesforce implementation partner to rebuild post-migration.