Migrate from Lead Perfection to Odoo CRM

Odoo crm.lead collapses Lead Perfection's separate Lead and Contact objects

Lead Perfection maintains distinct Lead and Contact objects with different schemas — leads carry product interest and project type fields, while contacts carry billing and address data. Odoo CRM uses a single crm.lead model where both record types live, differentiated by the type field (lead vs. opportunity). FlitStack routes Lead Perfection leads to crm.lead and converts customers to res.partner, but the merged Odoo model means Lead Perfection's separate contact data for leads gets stored alongside the lead record. Industry-specific fields migrate as custom fields on crm.lead; your Odoo admin must create x_product_interest, x_project_type, and x_appointment_source in Settings > Technical > Models before migration data lands.

Lead Perfection's appointment timeslot model has no native Odoo equivalent

Lead Perfection defines up to 6 appointment slots per day per sales rep, each with a status flag (available, booked, no-appointment). Odoo CRM has no timeslot scheduling concept — activities use a single scheduled date with optional duration. FlitStack migrates appointment records as crm.activity entries with the original scheduled date and time preserved, but the per-slot configuration requires custom fields (x_timeslot_number, x_slot_status) and the logical routing that maps Lead Perfection's zip-code-based office assignment to Odoo crm.team. Pre-migration planning must identify which Odoo sales team each Lead Perfection office maps to so team assignment is correct from the first data load.

Industry-specific custom fields must exist in Odoo before migration runs

Lead Perfection's home remodeling verticals (product interest, project type, appointment source, and related pick-list values) are baked into the platform's data model. Odoo CRM ships with no equivalent fields — they need to be created as custom fields on crm.lead before any Lead Perfection data can land in them. FlitStack delivers a schema setup plan that names each custom field, its type (char, selection, integer), and its pick-list options, so your Odoo admin can create them in Settings > Technical > Models > crm.lead before the migration runs. If custom fields don't exist at load time, Lead Perfection's industry data either drops or gets flagged as unmapped.

Workflows and automated rules in Lead Perfection do not migrate and require Odoo rebuild

Lead Perfection stores workflow logic for lead routing, assignment rules, and stage progression in its application layer — this logic lives in the code, not the data. FlitStack migrates data only; the automation rules must be rebuilt in Odoo using Action Rules, automated actions, or server actions. FlitStack exports Lead Perfection workflow definitions as a written reference document your Odoo admin can use to reconstruct assignment logic and stage automation. For outbound dialing configurations and appointment routing rules, Odoo has no native equivalent — teams typically configure third-party VoIP integrations post-migration to handle calling workflows.

Owner IDs require email matching against Odoo users before migration

Lead Perfection owner IDs point to users within its own system. Odoo uses res.users for ownership, and the cross-system link is email address. FlitStack matches Lead Perfection owner email addresses against Odoo user emails to resolve user_id on migrated records. Any owner whose email has no corresponding Odoo user account gets flagged in a pre-migration match report. Records owned by unmatched users land with a null user_id in Odoo unless you assign them to a fallback owner. You can invite the unmatched owners to Odoo before migration or pre-create their user accounts so the match succeeds at load time.