Migrate from Lead Liaison to Odoo CRM

Lead Liaison Prospects map directly to Odoo crm.lead records. The Lead's name, email, phone, company_name, and street/city/state/country address fields map 1:1. We extract all custom Prospect properties (lead source, org type, industry, and any customer-defined fields) and pre-create Odoo custom fields (ir.model.fields with track_visibility=onchange) before import so that no data is dropped. The original Lead Liaison record ID is stored in a custom char field x_ll_record_id for audit traceability.

Lead Liaison Companies map to Odoo res.partner records with is_company=True. The HubSpot-like flat Company model in Lead Liaison (separate from Prospects) becomes Odoo's partner-as-company record. We set partner_latitude and partner_longitude if geolocation data is present, and website if the company has a domain record. After importing Companies, we run a second pass on Prospects to link each Prospect to its corresponding Company partner via parent_id on res.partner.

Lead Liaison tags are a flat labeling system that migrates directly to Odoo crm.tag records. Each unique tag name is inserted into crm.tag, and the many2many relationship between Prospect and Tag is migrated via crm.lead.res.partner.rel. Tag-based segmentation from Lead Liaison is preserved as tag memberships in Odoo for use in kanban filtering and automated action triggers.

Lead Liaison's numeric lead scores have no native Odoo equivalent because Odoo CRM does not include a weighted scoring engine. During scoping the customer chooses one of two strategies: (a) store the numeric score as a custom integer field x_lead_score__c on crm.lead, or (b) bucket scores into named crm.tag values (Hot 80-100, Warm 50-79, Cold 0-49). We export the raw numeric score regardless of strategy and let the customer decide the tagging threshold during configuration review.

Lead Liaison's user-defined custom activity types (button clicks, phone calls, orders, link clicks) require upfront schema alignment because Odoo does not have an arbitrary event-type system. We request a list of all active custom activity type names during discovery, pre-create corresponding custom fields on crm.lead (e.g., x_last_order_date, x_button_click_count), and migrate each activity record as a mail.message with subtype=comment and a custom body field storing the activity type and metadata. Activity timestamps are preserved as mail.message.date.

Lead Liaison buy signals are behavioral triggers (signal type, trigger date, associated Prospect) attached to a Prospect. We export signal type and trigger date and migrate them as crm.tag entries (e.g., tag=High-Intent-Signal) plus a note body storing the signal classification. The underlying rule configuration is not exposed via API and requires manual rebuild in Odoo's Automated Actions if the customer wants automated re-triggering.

Lead Liaison visitor tracking produces chronological page-view logs per Prospect including company identification, page URL, and engagement depth. Odoo CRM has no native visitor-identification module. We flatten the visit history into a series of mail.message records attached to the crm.lead with subtype=comment, body text storing the page URL and timestamp, and a custom field x_visit_company storing the identified company name. Visit count and last-visit date also migrate to custom fields x_visit_count and x_last_visit_date for quick reference without opening each note.

Lead Liaison form definitions and all submission records are available via API including field responses, submission timestamps, and referring pages. We migrate each submission as a mail.message note on the linked crm.lead, storing the form name, field responses, and referring URL in the body. If the form has fewer than five fields and the customer requests it, we pre-create equivalent custom fields on crm.lead for cleaner CRM use.

Lead Liaison list memberships define audience targeting for campaigns and automations. We export all list definitions and Prospect-to-List assignments. Each list name becomes a crm.tag entry, and every Prospect in that list receives the corresponding tag. Dynamic list logic (criteria-based segmentation) is documented in the automation inventory and cannot be replicated in Odoo without manual rebuild in Automated Actions.

Lead Liaison email campaign metadata (name, status, associated lists) transfers cleanly as crm.tag entries denoting campaign membership. Email HTML content, templates, and assets are extracted and delivered as a file package for the customer's admin to re-upload into Odoo Email Marketing or a third-party email tool. Campaign performance metrics (open rates, click rates) are UI-visible in Lead Liaison but not reliably retrievable via API in bulk; we flag these as scope gaps in the migration report.

If the customer uses Lead Liaison's bundled OneFocus CRM for deal management, pipeline stage definitions and deal assignments migrate to Odoo crm.stage. Stage names map directly; stage sequence order is preserved by setting sequence values. Custom pipeline fields on deals migrate as custom fields on crm.lead. We configure Odoo's kanban default_stage_id and team-based stage filtering (crm.team) to match the customer's pipeline layout.

Lead Liaison User records (name, email, role, ownership assignments) map to Odoo res.users. We resolve owners by email match. Any Lead Liaison Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Lead Liaison users are imported as Odoo partners (res.partner) with the original user flag preserved rather than as active users.