Migrate from Inflection.io to Odoo CRM

Inflection.io Contacts with Lifecycle Stage of subscriber, marketing qualified lead, or lead map to Odoo CRM Lead. Lifecycle Stage of sales qualified lead, opportunity, customer, or evangelist map to Odoo CRM Contact attached to an Account. We compute the split using the Inflection lifecyclestage and hs_lead_status properties, and preserve the original Lifecycle Stage in a custom Char field on both Lead and Contact for audit and reporting continuity.

Inflection.io Account records map directly to Odoo CRM Account (res.partner with company_name set). The HubSpot company domain becomes the Account's website field and serves as a dedupe key during import. Odoo Accounts are created before any Contact import so that the Contact-to-Account relationship is satisfied at insert time.

Inflection.io custom Person fields (Char, Numeric, Date, Boolean, and dropdown types) map to Odoo CRM custom fields created via Odoo Studio or Python model definition. We create matching field names with the x_inflection_ prefix to preserve provenance. Field types are mapped: text to Char, numeric to Float or Integer, dates to Date, booleans to Boolean, and picklist values to Selection fields.

Inflection.io product event schemas (usage counts, feature flags, PQL scores, last-seen timestamps) have no native Odoo equivalent. We flatten the most relevant event attributes as custom fields on the Contact record: x_last_product_event_date, x_pql_score, x_feature_a_usage_count, and similar. High-cardinality event histories (thousands of events per contact) are summarized as JSON or stored in an Odoo attachment for reference rather than as individual records.

Inflection.io Journey membership flags (which Journeys a contact entered, last active Journey, Journey entry date) map to Odoo CRM Tags and custom fields. We preserve x_journey_names (Tag), x_last_journey_name (Char), x_journey_entry_date (Date), and x_journey_last_active_date (Date) on the Contact record. The Journey step sequence and trigger logic is not migratable as automation; we document it for manual rebuild in Odoo Studio.

Inflection.io Segments built on contact properties, product events, and behavioral signals map to Odoo CRM Groups (an Odoo internal contact grouping feature) or Tags. We export segment rule definitions and contact counts during scoping and rebuild them as domain filters in Odoo Groups or as Tag-based cohorts. Live segment membership recalculation is not available in Odoo without custom development; we document the segment logic for periodic manual refresh or a scheduled Python script.

Inflection.io Account-level custom properties (industry, employee count, revenue tier, hierarchical parent-child relationships) map to Odoo CRM Account custom fields. We create matching fields via Studio and import using the x_inflection_ prefix. Parent-child Account hierarchies in Inflection map to Odoo's Contact多重 address model where the parent Account holds the corporate-level data.

Contact-level tags and label flags in Inflection.io migrate to Odoo CRM Tags (mail.mail.message.subtype). We preserve the exact tag vocabulary and apply all tags to the corresponding Contact record. Tag counts are noted in the scoping report for the customer's admin to validate post-import.

Inflection.io's bi-directional Salesforce sync field-level mappings do not apply in Odoo CRM. We document the Salesforce field names that were mapped in Inflection for reference, but the sync configuration must be rebuilt in Odoo's CRM module with the appropriate Odoo-to-Salesforce integration if a hybrid stack is maintained. We flag any Salesforce custom fields referenced in Inflection sync rules for the customer to provision in Salesforce if bi-directional sync continues.

Inflection.io native forms and third-party form integrations do not migrate. We export form field mappings and submission records (contact field values from each form) as Contact custom field values or tags. The form itself must be rebuilt in Odoo Website Builder forms, a third-party form tool (Typeform, HubSpot Forms), or a custom Odoo form module. We deliver a form inventory with field-level mapping as part of the handoff documentation.

Inflection.io's web tracking attribution data (tracked page visits, behavioral attribution scores, UTM parameters on Inflection-sent email clicks) migrates to Odoo CRM as custom Contact fields: x_last_visit_date, x_utm_source, x_utm_medium, x_utm_campaign. Note that Odoo does not have native anonymous-to-known web tracking; new attribution after migration requires a separate web tracking pixel (Odoo Website analytics or a third-party tool like Hotjar, Google Analytics, or Segment).

Inflection.io's zero-ETL bi-directional sync with Snowflake and Redshift has no Odoo CRM native equivalent. We document the warehouse table schemas, column names, and sync credentials from the Inflection integration during scoping. The customer must provision a new data connector (Fivetran, Airbyte, or a custom Odoo API integration) to stream contact and event data into Odoo. We provide the source schema mapping as a reference for the new connector configuration.

Monthly Marketed Contact counts are derived from Inflection.io Journey execution logs. We export Journey execution history and compute a best-effort MMC baseline (unique contacts who flowed through at least one Journey in the most recent 30-day period) and store it as x_mmc_baseline on each Contact record and in a migration summary document. Odoo does not have an MMC billing model; this data is preserved for the customer's pricing documentation and contract compliance with Inflection.io during the exit process.