Migrate from LeadPrime to Odoo CRM

LeadPrime Leads map directly to Odoo crm.lead records. Standard fields (name, email, phone, source) map to their Odoo equivalents. The LeadPrime status field maps to crm.lead.stage_id via the Odoo stage sequence we create to match the LeadPrime pipeline. Owner assignment from LeadPrime maps to crm.lead.user_id on the Odoo side. Any LeadPrime lead with a converted flag maps to crm.lead with type='opportunity' rather than type='lead' to preserve the qualification state.

LeadPrime Contacts map to Odoo res.partner with company_type set to 'person'. Email, phone, title, and address fields map to their Odoo equivalents. Where a LeadPrime Contact is linked to a LeadPrime Company, we create the res.partner parent company first (with company_type='company'), then link the contact as a child partner via parent_id. The partner's function and tag assignments carry forward as ir.model.data references.

LeadPrime Company records map to Odoo res.partner with company_type='company'. Industry, size, website, and address fields map to their Odoo equivalents. We use the Company domain as a dedupe key during import to avoid creating duplicate partner records if a Contact with the same domain is imported first. Custom fields on the Company record map to custom res.partner fields in Odoo that we create during schema setup.

LeadPrime Users map to Odoo res.users by email match. Active/inactive status transfers. Any LeadPrime User without a matching Odoo user at migration time is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Role and admin flags map to Odoo's access rights groups (Sales / Administrator) that we configure during setup.

Each LeadPrime pipeline maps to an Odoo crm.team with a dedicated stage sequence. Odoo supports multiple crm.team records, each with its own kanban_stage_ids sequence. We export the full LeadPrime pipeline topology (stage names, order, probability percentages, routing triggers) and recreate it as an Odoo crm.team with matching stages. Pipeline-specific routing rules are documented separately (see mapping_type=configuration below) because Odoo does not have a native equivalent to LeadPrime's Shark Tank or Hybrid routing engine.

LeadPrime stage names and ordering map to Odoo csm.stage records attached to the corresponding crm.team. Stage probability percentages migrate to crm.stage.probability. Any stage-specific routing triggers from LeadPrime are captured in the distribution rule inventory and do not become Odoo configuration automatically; we document them for the admin to re-implement using Odoo's crm.lead.assigned_partner_id assignment rules or an Odoo App for round-robin.

LeadPrime Round Robin, Blind, Shark Tank, and Hybrid distribution rules are stored as configuration rather than as data records. We export the full rule definition (bucket size, rep list, daily caps, territory filters, seniority weighting) as a written handoff document. Odoo has no native Shark Tank or Hybrid routing engine; teams rebuild this using Odoo's crm.team member assignment or a third-party Odoo App from the Apps Store. We do not implement the routing rules as Odoo code inside this migration scope.

LeadPrime custom fields on Leads, Contacts, and Companies are organization-specific. We read the full field list during scoping, create equivalent Odoo custom fields via Developer Mode or Studio before migration begins, and map each source field to its destination counterpart. Odoo field types (char, text, integer, float, date, datetime, selection, many2one, many2many) are assigned based on the LeadPrime field type. Fields with no Odoo equivalent are flagged for the customer's admin to decide whether to create a custom field or drop the data.

LeadPrime tags are flat label structures that migrate to Odoo crm.tag records for leads or res.partner.category for contacts and companies. Tags with hierarchical meaning in LeadPrime are flattened during migration since Odoo's tag taxonomy is single-level. We preserve the full tag assignment per record using the tag's name as the match key.

LeadPrime activities (calls, emails, notes) logged against leads or contacts migrate to Odoo mail.message records linked to the crm.lead or res.partner via mail.thread. Call duration and disposition migrate to custom fields on mail.message. Note content migrates as mail.message with subtype='comment'. Odoo 16+ merges activity tracking into the chatter model (mail.thread), so we attach activity history to the record's message_ids rather than a separate activity object.

LeadPrime Lead Finder Credits are a billing token that funds enrichment lookups and are not a data record. They have no equivalent in Odoo CRM. We confirm the credit balance at cutover and advise the customer to download their credit purchase history separately for financial records. Any enrichment results already written to lead fields (verified email, phone number) are migrated as part of those fields since they are contact data, not credit data.

LeadPrime territories and sales team assignments map to Odoo crm.team records. Territory names become crm.team.name values, and rep membership maps to crm.team.member_ids. We preserve the mapping between LeadPrime territory and the rep assignments so the customer's admin can map each territory to a corresponding Odoo sales team. Territory-level daily caps and quota settings from LeadPrime are captured in the distribution rule handoff document.