Migrate from Flash Lead Sales to Microsoft Dynamics 365 Sales

Flash Lead Sales Lead records map to Microsoft Microsoft Dynamics 365 Sales Lead entity. The primary name, email, phone, source attribution, owner assignment, and current stage migrate directly. We extract all available Lead fields from the CSV export and map them to typed Dynamics fields (string, email, phone, picklist). Any Flash Lead custom properties on the Lead record map to new custom fields (text, picklist, or multi-select depending on the source value type) that we provision in the destination Dynamics org before import. The Lead_Status in Dynamics is set to a default value during migration; the customer's admin sets the appropriate status values per their sales process.

Flash Lead Sales records stage transitions as activity log entries, not as discrete stage-history fields. Only the current stage appears as a guaranteed discrete field in the CSV export. We request the full activity log export during discovery, parse stage-transition timestamps and stage names from the activity records, and reconstruct stage history as a series of custom datetime and picklist fields on the Dynamics Lead record (e.g., stage_1_name__c, stage_1_entered__c, stage_2_name__c, stage_2_entered__c). This preserves deal velocity and time-in-stage metrics that the customer uses for pipeline reporting.

Flash Lead Sales pipeline stages are user-defined with no enforced schema. We extract the full stage list from the customer's Flash Lead account during discovery and produce an explicit mapping table: each source stage name maps to a Dynamics Sales Process stage value (or creates a new one). Stage probability percentages map to StageProbability on the Opportunity entity once Leads are converted. Stage-specific rules or automation triggers in Flash Lead Sales cannot be migrated and are documented for rebuild in Dynamics Sales Process configuration.

Flash Lead Sales Contact records map to Microsoft Dynamics 365 Sales Contact. We map the primary name, email, phone, address, and any purchase history fields directly to typed Dynamics Contact fields. Contact records in Flash Lead Sales carry a relationship to the Lead record; we preserve this linkage by matching on email address during import and setting the parent Customer field or linking via a custom lookup field. Flash Lead Contact notes and conversation history migrate as Note records attached to the Contact.

Flash Lead Sales Team Members map to Microsoft Microsoft Dynamics 365 Sales User records. We extract each Team Member's name, email, and role assignment. Owner assignment on Flash Lead Leads and Contacts is preserved in Dynamics by matching on email address against the destination User table. If a matching Dynamics User does not exist, we place the record in a reconciliation queue for the customer's admin to provision the User before record import continues. Role-based visibility in Flash Lead Sales maps to Dynamics Team or Territory sharing model configuration, which the admin configures post-migration.

Flash Lead Sales tags are applied to Leads without limit and serve as a segmentation mechanism. We export all tags as a comma-separated list per Lead and map them to a Dynamics multi-select picklist field (if tag count is under 150 distinct values) or a custom text field (if tag count exceeds Dynamics picklist limits). The customer chooses tag strategy during scoping. Tags used for lead categorization migrate as-is; tag-based filtering logic in Flash Lead Sales does not migrate and must be rebuilt as Dynamics Views or filters.

Flash Lead Sales Lead Sources (Facebook, Instagram, Referral, Purchased List, etc.) are preserved as a custom field on the Dynamics Lead record. We extract the source label from the Lead record and populate a custom picklist or text field (lead_source_label__c) in Dynamics. If the customer uses Dynamics 365 Marketing, the source label maps to the lead's originating campaign or channel for attribution.

Flash Lead Pro invoices migrate to Microsoft Dynamics 365 Sales Invoice records. We extract invoice amount, status (Draft, Sent, Paid, Void), related Contact or Lead reference, line items, and date fields. Invoice PDF attachments migrate as ContentDocument linked to the Invoice record. Custom invoice fields and formatting templates do not transfer and are documented for rebuild in Dynamics Invoice templates.

Flash Lead Sales Facebook Messenger and Instagram DM threads export as flat conversation text logs attached to the Contact record. Thread branching, message timestamps (individual), and read receipts are not preserved in the export format. We attach the full conversation log as a Note record linked to the corresponding Dynamics Contact, noting the limitation in the migration report so the customer can assess whether conversation history is business-critical for support or compliance purposes.