Migrate from Evam to Odoo CRM

Evam Customer records map directly to Odoo CRM Contact. Standard profile fields (name, email, phone, demographic attributes) migrate 1:1 to Odoo res.partner records. Custom customer properties migrate to Odoo custom fields on res.partner, which we pre-create via Odoo Studio or XML data migration script before import. The contact's primary address and company affiliation map to Odoo's address fields and partner_latitude/longitude if geolocation is present in Evam.

Evam Customers with a company association map to Odoo CRM Account (res.partner with partner_latitude=company). We use the Evam customer company domain as the Account name and populate the Website field. Accounts are created before Contacts so that the parent_id lookup is satisfied at Contact insert time. Customers without a company association become standalone Contacts with no parent account.

Evam Customers in early lifecycle stages (anonymous visitor, new prospect) map to Odoo CRM Lead (crm.lead) if the customer is not yet a qualified contact in the destination sales process. We document the customer's Evam lifecycle stage as a custom field lead_source_stage__c on the Lead record for audit. Customers who have progressed past initial acquisition in Evam map directly to Contact/Account.

Evam behavioral and transactional event records (page views, purchases, form submissions, custom events) migrate to Odoo CRM Activity records. We use event type to determine the Odoo activity type: browse events map to Note records, transactional events map to Meeting records, and engagement events map to Task records. Event timestamps migrate as Odoo activity create_date and activity_date for timeline ordering. The event payload (JSON schema) migrates as a custom text field event_payload__c for post-migration reconciliation.

Evam processes billions of touchpoints, which cannot all be exported in one pass. We scope the event export to a defined time window (typically the last 90-180 days based on customer retention policy) and aggregate older events into summary records. Each aggregated summary captures the event count, first occurrence, last occurrence, and event type distribution per customer. This keeps migration volume manageable while preserving representative behavioral history.

Evam Segments define customer groupings used to filter journey entry and campaign targeting. We document each Evam segment criteria as Odoo domain filter XML (ir.filters model) with equivalent field references mapped to Odoo res.partner field names. Segment membership (the list of customers in each segment) migrates as Odoo CRM static groups or as tagged records using Odoo's tag system (x_studio_tags). The customer's admin rebuilds dynamic Odoo filters from the documented segment rules post-migration.

Evam marketing campaigns attached to journey steps or run independently migrate to Odoo CRM Campaign (utm.campaign). Campaign metadata (name, status, start date, end date, channel assignments) migrates directly. Campaign performance metrics (open rates, click rates, conversion rates) are derived post-migration in Odoo reporting rather than migrated as historical calculations. Channel-specific campaign configurations (SMS sender IDs, push notification templates) are documented for manual re-setup.

Evam Journeys encode step sequences, branch conditions, wait timers, and entry/exit rules that have no direct Odoo equivalent. We do not migrate journey definitions as code. Instead, we document every active Evam journey as a written specification (step order, trigger conditions, channel actions, wait timers, exit criteria) and map the journey's primary customer segment to an Odoo CRM Sales Team and Pipeline Stage configuration. This gives the customer's admin a blueprint to rebuild journey logic using Odoo Studio or a CRM extension.

Evam SMS channel configurations (sender IDs, template IDs, provider credentials) are environment-locked to Evam's registered application and cannot be moved to Odoo. We document the full SMS channel configuration during discovery (provider name, account ID, sender ID patterns, approved templates) and provide a re-setup checklist for the customer's operations team to configure Twilio, MessageBird, or another SMS gateway in Odoo before cutover. The checklist includes template migration notes for each active SMS campaign.

Evam push notification and in-app message configurations (Firebase credentials, app IDs, notification templates) are bound to Evam's registered app environment and cannot be moved. We document the full push channel configuration during discovery and provide a re-setup checklist for the customer's dev team to configure Firebase Cloud Messaging or an equivalent in Odoo's website module or a custom push app. Template content migrates as text documentation for manual re-entry.

Extended properties on Evam Customers, Events, or Journeys defined beyond the standard schema migrate to Odoo custom fields. We pre-create each destination field via Odoo XML data migration or Studio before import, matching the Evam field data type to the nearest Odoo field type (Char, Text, Integer, Float, Date, Datetime, Selection, Many2one). Lookup fields in Evam that reference other Evam objects require manual schema mapping to Odoo relational fields during scoping.

Evam AI-based propensity scores are computed per-customer within Evam's runtime environment and are not accessible via the documented API. We cannot migrate these scores directly. We document the score calculation criteria (model inputs, weighting factors, score range) as a written specification so the customer's data science team can re-implement scoring in Odoo using Odoo Studio custom fields, an Odoo AI app, or a third-party scoring integration (e.g., a Python-based model connected via Odoo RPC). Customers should plan a scoring-free reset on day one.

Evam Owners referenced on Customer, Event, Campaign, and Journey records map to Odoo CRM User (res.users). We resolve owners by email match against the Odoo destination instance. Any Evam Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status in Odoo is set to match the owner's active status in Evam.

Evam email engagement records (email opens, clicks, sends) migrate to Odoo CRM Note or Task records linked to the parent Contact or Lead. Email content migrates as a Note body; engagement metadata (open count, click count, send timestamp) migrates as custom fields on the Note record. Odoo does not have a native EmailMessage object in standard CRM; email integration requires Odoo Mail module configuration, which is scoped separately from the data migration.