Migrate from Plumb5 to Odoo CRM

Plumb5 unified profiles with lifecycle stages of anonymous visitor, lead, or marketing qualified lead map to Odoo CRM Lead. Profiles with lifecycle stages of sales qualified lead, customer, or evangelist map to Odoo Contact attached to a Company (res.partner). We compute the split using Plumb5's lifecycle_stage property and preserve the original stage value in a custom Char field plumb5_lifecycle__c on both Lead and Contact for post-migration reference.

Plumb5 profiles associated with organizations (identified by domain or a company_name property) map to Odoo res.partner records with is_company=True. The Plumb5 company identifier becomes the partner's name, and the domain becomes the website field. This parent Company record is created before any Contact import so that individual Contact records can reference it via parent_id.

Plumb5 behavioral events (web visits, email opens, form submissions, app interactions) migrate as Odoo mail.message records linked to the corresponding Lead or Contact via model and res_id. Event type becomes the message's subject prefix, timestamp is preserved as message_date, and the event payload (page URL, referrer, duration) migrates as body text. We configure a custom Odoo module to register the mail.message extension so the migration user can query events by type after import.

Plumb5 session records containing device type, geography, referrer URL, and session duration map to custom Char and Integer fields on the Odoo Lead or Contact: plumb5_last_device__c, plumb5_last_country__c, plumb5_last_referrer__c, and plumb5_session_duration__c. Odoo does not store raw session data natively, so we flatten the most recent session values as read-only properties on the record.

Plumb5 channel attribution (organic search, paid search, social, email, direct, referral) stored as a property on each profile migrates to Odoo crm.tag records with a 'channel:' prefix. TagAssignment records link each Lead or Contact to its Plumb5 channel source. If the customer uses Plumb5's UTM-based channel tracking, we preserve utm_source, utm_medium, and utm_campaign as separate custom fields.

Plumb5 behavioral score values stored per profile migrate as a custom Float field plumb5_score__c on the Lead or Contact object. The score logic itself (auto-segmentation rules and threshold definitions) does not migrate as executable rules because Odoo has no native scoring engine. We document the Plumb5 score definition table during discovery so the customer's Odoo admin can rebuild thresholds using Odoo automation rules or a custom Python compute method.

Plumb5 auto-segmentation generates dynamic segment membership lists. Since Odoo handles dynamic segmentation differently (usingFilters and domain-based searches rather than pre-computed lists), we migrate segment membership as static crm.tag records on each Lead or Contact. We tag records with the Plumb5 segment name as a static tag, preserving the membership at migration time. The customer's admin rebuilds the dynamic behavior in Odoo using saved Filters and domain views.

Plumb5 marketing campaigns with associated audiences and goals migrate as Odoo crm.lead.tag records with a 'campaign:' prefix, linked to each Lead or Contact that was a member of that Plumb5 campaign. Campaign performance metrics (reach, opens, clicks) do not migrate as Odoo reports because Odoo's campaign tracking lives in the Marketing app rather than CRM. We deliver a campaign membership export as a supplemental CSV for the customer's marketing team to reference when rebuilding campaign analytics in Odoo Marketing.

Plumb5 derived KPIs per customer (recency, frequency, monetary value, sentiment scores) migrate as read-only custom fields on the Odoo Lead or Contact: plumb5_recency_days__c, plumb5_frequency__c, plumb5_monetary_value__c, plumb5_sentiment_score__c. These are preserved as static properties; Odoo does not compute RFM (recency, frequency, monetary) natively in CRM without custom development.

Plumb5 lifecycle stages (anonymous visitor through brand advocate) do not map 1:1 to Odoo's Lead Status values (New, Assigned, Qualified, etc.). We map the closest equivalent: Plumb5 'lead' maps to Odoo Lead with Status 'New'; Plumb5 'customer' maps to a Contact record rather than a Lead. Stages with no Odoo equivalent (brand advocate, inactive) are preserved in the plumb5_lifecycle__c custom field for the customer's admin to decide on post-migration naming conventions.

Plumb5 user-defined profile fields require a named Odoo custom module before they can receive data. We develop a lightweight Python module (plumb5_migrate) that defines all discovered Plumb5 custom properties as typed Odoo fields (Char, Integer, Float, Boolean, Date, Datetime, Selection) on the res.partner and crm.lead models, then deploy it to the target Odoo instance before migration begins. The module is handed off to the customer post-migration for ongoing maintenance.

Plumb5 Owners map to Odoo res.users records by email match. Any Plumb5 Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Leads and Contacts migrates as Odoo's user_id field. If the customer uses Plumb5's team-based routing, we map team membership to Odoo Odoo Sales Team (crm.team) via the resource.calendar relationship.