Migrate from Flash Lead Sales to Odoo CRM

Flash Lead Sales Leads map to Odoo CRM crm.lead records. The current stage maps to Odoo stage_id; custom stage names require an explicit mapping table built during discovery. Tags migrate as a comma-separated string into a custom char field; lead sources migrate to the crm.lead source_id field or a custom field. Owner assignment maps by email match to Odoo res.users. Flash Lead does not export stage transition history as structured data; we request the activity log separately and store reconstructed progression as a custom stage_history__c text field on each lead.

Flash Lead Sales Contacts map to Odoo res.partner records with type=contact. Email address is the dedupe key. The customer's name, phone, location, and conversation history attach to the partner record. If Flash Lead exports a company association, we resolve the Company record first and attach partner_id with parent_id pointing to the company partner.

Flash Lead Sales Company records map to Odoo res.partner with type=company. The company name becomes the partner name, domain or website becomes website, and any associated contact roles or deal history attach via the partner relationship. If Flash Lead exports contacts without a named company, we create placeholder company partners as needed to satisfy Odoo's partner hierarchy.

Flash Lead Sales Deals map to Odoo CRM crm.lead records with type=opportunity. The deal amount maps to Odoo's expected_revenue; the pipeline stage maps to stage_id via the explicit stage mapping table. We set type=opportunity so records appear in the Odoo pipeline kanban view alongside leads. Deal-specific custom fields migrate as additional columns on the opportunity record.

Flash Lead Sales custom pipeline stages (e.g., Lead, Qualified, Proposal, Negotiation, Won, Lost) require an explicit mapping table produced during discovery. Each source stage is assigned a target crm.stage record with matching name and probability percentage. Stage-specific automation rules in Flash Lead are documented but not migrated; Odoo Studio or server actions rebuild them post-migration. Odoo's stage is tied to a sales team (crm.team) so multi-pipeline accounts require one stage set per team.

Flash Lead Sales Team Members map to Odoo res.users by email address match. Role-based access (manager, agent) maps to Odoo's access rights groups: crm.group_sale_salesman for agents and crm.group_sale_salesman_all_leads or custom groups for managers. The migration holds any owner assignments where the Odoo User does not yet exist in a reconciliation queue until the admin provisions the user.

Flash Lead Sales tags (applied without limit to leads) migrate to Odoo crm.tag records. Tags are created on demand during the import phase and linked to crm.lead records via crm.lead.tag_ids. If tag names exceed Odoo's 32-character name limit, we truncate to 32 characters and append a hash suffix for uniqueness. Tags are not the same as Odoo's internal note flags; they map to the dedicated tag model.

Flash Lead Sales Lead Sources (Facebook, Instagram, Referral, Purchased List, etc.) map to Odoo's utm.source model. We create utm.source records for each distinct source label and link them to crm.lead via the medium_id or a custom source field. If Odoo's utm module is not installed, we create a custom selection field on crm.lead to preserve the source attribution.

Flash Lead Sales Pro Invoice records (amount, status, related deal) map to Odoo sale.order. The deal reference in Flash Lead is resolved to the corresponding Odoo opportunity record, and the sale.order origin field references the source deal ID for audit traceability. Invoice PDF attachments migrate as ir.attachment records linked to the sale.order. Odoo's invoice generation (account.move) is a separate accounting step not covered under CRM migration scope.

Flash Lead Sales social message threads (Facebook Messenger and Instagram DMs) export as flat text logs attached to the contact record. We import the full conversation text as an ir.attachment linked to the res.partner record in Odoo. Thread structure, branching, timestamps, and read receipts are not preserved in the export from Flash Lead; we note this limitation in the migration report so the customer can assess business-critical conversation history requirements.

Flash Lead Sales automation rules (lead assignment, reassignment, email sequences) are stored as platform configuration and do not export as data. We document every active automation in the migration handoff inventory with its trigger, conditions, and actions. Odoo Studio, Server Actions, and Automated Actions are the rebuild targets. Sequence-based outreach rebuilds use Odoo CRM Live Chat or a third-party sales engagement integration. This object is listed for transparency; no records are migrated.

Flash Lead Sales reporting dashboards and sales activity insights are platform-generated views with no export capability. We deliver a written inventory of the reports the customer relies on, including the record counts, filter sets, and date ranges shown in each dashboard, so the customer's Odoo admin or implementation partner can recreate them in Odoo Reporting. This object is listed for transparency; no records are migrated.