Migrate from Insider to Odoo CRM

Insider user profiles with a lifecycle stage of Subscriber, MQL, or prospect-level assignment map to Odoo Lead. Profiles with a sales-qualified or customer lifecycle stage map to Odoo Contact attached to a Company (res.partner with customer_rank). We use the Insider Unification API upsert to extract all profile fields, compute the split using the lifecycle stage property, and preserve the original Insider lifecycle stage in a custom Char field (x_insider_lifecycle_stage__c) on both Lead and Contact for audit traceability. Email and phone map directly to email_from and phone on Lead; for Contact, email maps to email and phone to phone.

Insider Companies map to Odoo Company records (res.partner with is_company=True, customer_rank > 0). The Insider company name maps to name, domain maps to website, and industry maps to industry_id via Odoo's industry selection list. Address fields (city, country, street) map to partner address fields. We create Company records before any Contact or Lead import so that the parent_id lookup is satisfied at insert time.

Insider Deals map to Odoo CRM Opportunities (crm.lead records with type='opportunity'). The Insider dealstage property maps to Odoo stage_id within the configured pipeline. Pipeline names from Insider become Odoo team_id assignments (sales teams). Deal amount, currency, expected close date, and probability migrate to planned_revenue, x_currency_id, date_closed, and probability respectively. Any custom deal properties become custom fields on crm.lead.

Each Insider deal pipeline and its stages map to an Odoo CRM Pipeline (c.crm.team) with corresponding Stage records (crm.stage). We configure stage sequence, probability percentages, and is_won/is_lost flags during schema setup to match Insider's pipeline structure. Stage names and order transfer directly; probability values round to Odoo's integer constraint.

Insider behavioral events (page views, purchases, custom actions) export via the Raw Export API as event_name, timestamp, and event_parameters. We translate these into Odoo mail.message records with message_type='notification' linked to the parent Lead or Contact via res_id and res_model, or into a custom crm.event.log model if the customer's use case requires structured event history. The event_parameters JSON serializes into a custom Text field for audit. Historical timestamp preserves via mail.message date.

Insider segments are dynamic audience lists defined by attribute-and-event rule conditions. Since Odoo has no dynamic behavioral segmentation equivalent, we export the segment member list (user IDs) and recreate them in Odoo as Tags on the relevant Lead or Contact records. The segment rule definition exports as metadata for the customer's admin to reference when rebuilding equivalent filters using Odoo's domain-based filtering or static Tag groups.

Insider product catalog entries (sku, name, price, category, images) map to Odoo Product records. The Insider product ID becomes the default_code (SKU field). Prices and categories map to list_price and categ_id. Product images migrate as binary attachments on the product.product record. If the customer uses Odoo Sales or eCommerce modules alongside CRM, product variants map to product.template with attribute lines.

Insider transaction objects (order_id, total, items, currency, timestamps) map to Odoo Sale Order records linked to the corresponding Contact (partner_id) and Company (partner_invoice_id, partner_shipping_id). Order lines map to sale.order.line with product_id resolved from the product catalog mapping. Currency maps to currency_id. If the customer does not use Odoo Sales module, transactions map instead to custom fields on the Contact record.

Insider allows arbitrary key-value custom properties beyond the standard profile schema. We export all custom attribute keys and types, then create corresponding custom fields on the Odoo crm.lead model (or res.partner if used for contacts) via Odoo Studio before migration. Field types map from the Insider attribute type: string attributes become Char, numeric attributes become Float or Monetary, date attributes become Date, and boolean attributes become Boolean. Multi-value attributes become Char with comma-separated values or One2many lines depending on structure.

Insider static Lists (named user collections beyond dynamic segments) export as a list of user IDs per list. We recreate each list in Odoo as a Tag on the corresponding Lead or Contact record. List membership resolves by matching user email to the migrated Lead or Contact email. If the customer requires list-level grouping, we create a Tag per list name.

Insider tags export as string label arrays per user. We migrate each unique tag string to an Odoo Tag record (mailing.contact.subscription or a custom tag model depending on Odoo version and installed modules) and link it to the matching Contact or Lead via the tag_id relation. Tag arrays per user create multiple tag assignments on the same record.

Insider Journeys are multi-step event-triggered workflows with conditional branching, delays, and channel actions (email, SMS, WhatsApp, push). Odoo has no direct Journey equivalent. We export Journey definitions as a structured written inventory documenting each Journey's entry trigger, conditional gates, channel steps, exit conditions, and timing logic. The customer's admin or Odoo partner uses this inventory to rebuild equivalent automations in Odoo Automated Actions (base.action.rule) and Server Actions. We do not migrate Journey logic as code.