Migrate from Netmera to Odoo CRM

Netmera Users map directly to Odoo CRM Contacts. The Netmera user identifier becomes an external ID field on the Odoo Contact for future sync reference. Standard profile fields (name, email, phone, country) map to Odoo Contact name, email, phone, and country fields. Any Netmera user with an associated Company ID in Netmera maps to an Odoo Company/Account lookup on the Contact. Netmera's anonymous or tagless user captures may result in Contacts without names; we flag these for the customer to enrich post-migration.

Netmera Companies (if present in the customer's instance) map to Odoo CRM Companies. The company name becomes the Odoo Company name, and domain fields map to Website. We create the Company record before Contact import to satisfy the partner_id lookup on Contact.

Netmera Segments define audience rules based on profile attributes and behavioral conditions. Each Segment becomes an Odoo Tag on the Contact record. The segment membership criteria (rule logic) are documented in a written segment inventory that we deliver to the customer. For segments used as campaign targeting units, we also create a corresponding Odoo CRM Stage value in a custom pipeline field so that marketing and sales can replicate the audience logic. Dynamic segments that auto-update require a frozen rule capture at scoping time.

Netmera custom profile attributes (beyond defaults like name, email, phone) map to Odoo CRM Contact custom fields created via Odoo Studio before migration. We match attribute data types: string attributes map to Char or Text, numeric attributes map to Float or Integer, date attributes map to Date, and boolean attributes map to Boolean. Multi-value or list-type profile attributes map to Odoo Tags or Char fields with semicolon-delimited values. Attribute names are preserved with a netmera_ prefix in the field technical name.

Netmera Device records capture OS type, app version, push token, and device model per user. Push tokens do not transfer across providers and must be regenerated in Odoo's push context. We migrate OS type, app version, and device model to Contact custom fields for record completeness. Push token data is excluded from migration with a documented note that the customer must implement a re-opt-in or silent token refresh campaign for push delivery to function post-migration.

Netmera campaign records (name, channel, content, schedule, performance metrics) map to Odoo CRM Campaign records and to Note records on the Contact for historical reference. We migrate campaign metadata and content text; creative assets (images under 1MB, video under 12MB per Netmera limits) are flagged for manual upload into Odoo. Campaign targeting segments are translated to the corresponding Odoo Tags using the segment inventory from the mapping step.

Netmera Journeys define multi-step user-entry flows with channel steps and conversion events. Odoo CRM has no native journey orchestration equivalent. We do not migrate Journeys as data records. We deliver a written inventory of every active Netmera Journey listing entry conditions, step sequence, channel assignments, and conversion event definitions, with Odoo CRM automated action equivalents documented for the customer's admin to rebuild in Odoo Studio. Note that Netmera's conversion counting is user-based (one conversion per user per journey), which differs from event-occurrence counting in Odoo; we flag this KPI discrepancy in the inventory.

Netmera SDK-tracked Events (page views, custom actions, trigger events) map to Odoo CRM Activity records and Notes on the Contact. Each unique event name becomes an activity type or a Note with the event timestamp preserved. Event property keys and values migrate as structured Note body text or custom Contact activity fields. For high-frequency events (e.g., page_view), we consolidate by date and event name to avoid overwhelming Odoo's activity timeline. The customer defines the consolidation threshold during scoping.

Netmera Widgets (tooltips, pop-ups, in-app message designs) are visual assets tied to Netmera's rendering engine and are not transferable to Odoo CRM. We deliver a written inventory of all active Widgets with screenshots, content text, and trigger conditions so the customer's admin can rebuild them as Odoo email templates, SMS templates, or custom in-app notification configurations. Assets exceeding Netmera's 1MB image or 12MB video limits are flagged for re-encoding before use.

Netmera Tags used for labeling users map directly to Odoo CRM Tags. Tag membership associations migrate as Contact-Tag relations. Some Netmera users may be captured without tags (a platform feature); these untagged contacts are flagged for the customer to review post-migration.

Netmera survey questions and response records map to Odoo CRM Note records attached to the Contact. Survey question text becomes the Note title; response values become the Note body in structured text. Survey display logic and trigger conditions are platform-configured and do not migrate; we document these in the written inventory for manual rebuild in Odoo.

Netmera Owners map to Odoo CRM Users. We resolve owners by email match against the destination Odoo instance's User table. Any Netmera Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before Contact import resumes.