Migrate from Flash Lead Sales to Twenty CRM

Flash Lead Sales Leads map directly to Twenty's People CRM Object, which serves as the unified record for prospects and customers. The Lead name, email, phone, location, and custom properties migrate as standard and custom fields on the People record. We preserve the Flash Lead source attribution (Facebook, Instagram, Referral, Purchased List) as a custom text field on the People record, and tags migrate as comma-separated text or to Twenty's Topics if the customer chooses that classification model during scoping.

Flash Lead Sales Contacts map to Twenty's People CRM Object, treating Leads and Contacts as a unified record in Twenty's model. The Flash Lead contact's name, email, phone, purchase history, location, and previous conversation references migrate as fields on the People record. We set a source_system__c custom field to 'FlashLead' to identify migrated records. If a Contact already exists as a People record from a prior Lead conversion in Flash Lead, we match on email and update rather than duplicate.

Flash Lead Sales records stage transitions as activity log entries, not as a structured stage-history table. We extract the full activity log during CSV export, parse stage-change events by timestamp, and reconstruct the progression timeline as a custom stage_history JSON field on the corresponding Opportunity in Twenty. The current stage at migration time maps to the Opportunity's Stage field. Stage-specific probability percentages are mapped from Flash Lead's stage configuration to Twenty's Stage values.

Flash Lead Sales Deals map to Twenty Opportunities attached to a People CRM Object (the deal contact). We map the deal amount, expected close date, and custom deal fields to their Twenty equivalents. The pipeline assignment from Flash Lead maps to Twenty's Opportunity pipeline configuration. Any deal-specific notes or attachments migrate as comments or file attachments on the Twenty Opportunity.

Flash Lead Sales pipeline stages are user-defined with no enforced schema, and one account's stages may not map to another's. We extract the complete stage list during discovery, produce an explicit mapping table assigning each Flash Lead stage to a Twenty stage or creating new ones, and configure stage probabilities in Twenty before migration. Stage-specific automation rules from Flash Lead are documented for manual rebuild in Twenty's automation framework; they do not migrate as code.

Flash Lead Sales Team Members with role-based access controls map to Twenty User records. We resolve owners by email match during migration. Any Flash Lead Team Member without a matching Twenty User goes to a reconciliation queue for the customer to provision before record import resumes. Role-based visibility from Flash Lead maps to Twenty's workspace-level permissions.

Flash Lead Sales tags are applied to Leads without limit and serve as segmentation and filtering mechanisms. We export all tags as a comma-separated string on each record. Tags migrate as a custom multi-value text field or to Twenty's Topics with TopicAssignment records, depending on whether the customer wants tag-based filtering as a first-class feature in Twenty. The customer selects the tag strategy during scoping.

Flash Lead Sales Lead Sources (Facebook, Instagram, Referral, Purchased List) track where leads originated and are preserved as a custom text field on the People CRM Object in Twenty. Source labels map directly without transformation. If the customer uses multiple Flash Lead source categories, we preserve the full label as entered in Flash Lead.

Flash Lead Pro invoices tied to Deals migrate as custom fields on the corresponding Twenty Opportunity (invoice amount, invoice status, invoice number). Full invoice formatting and custom invoice fields require field-level mapping per the customer's Flash Lead configuration. Invoice PDFs are attached as files to the Opportunity record. If the customer requires full invoicing functionality in Twenty, they use Twenty's native Opportunity fields or a third-party invoicing integration post-migration.

Flash Lead Sales Facebook Messenger and Instagram DMs export as flat text logs attached to the contact record without thread structure, timestamps, or read receipts. We attach the full conversation log as a text file to the corresponding People CRM Object in Twenty. We document the limitation in the migration report so the customer can assess whether conversation history is business-critical. Thread metadata (branching, timestamps, read receipts) cannot be reconstructed from the export.

Flash Lead Sales automated workflows for lead assignment, reassignment, and email sequences are stored as configuration rather than data. We do not migrate automation rules. We deliver a written inventory of every active Flash Lead automation with its trigger, conditions, actions, and a recommended Twenty automation equivalent. The customer's admin rebuilds these in Twenty's automation framework post-migration.

Flash Lead Sales reporting dashboards and insights are platform-generated views that cannot be exported as data. We deliver a written summary of the existing Flash Lead report structure (report types, filters, metrics) so the customer can recreate equivalent views in Twenty's reporting module. We do not rebuild reports as part of the migration scope.