Migrate from Adobe Marketo Engage to Odoo CRM

Marketo Persons (internally called Leads) migrate to Odoo CRM Contacts. Standard fields — email, firstName, lastName, phone, title — map directly. The Marketo lead status maps to a Contact stage or tag in Odoo since Odoo has no separate Lead object as a distinct record type. We preserve the Marketo original create date, last seen date, and lifecycle stage in custom Odoo fields for audit and future segmentation.

Marketo Company records migrate to Odoo CRM Company records. The company name, website, industry, number of employees, annual revenue, and address fields map to Odoo Company fields. Odoo Company serves as the parent for Contact records, so we create Companies first in the migration sequence and resolve the company reference on Contact records before importing contacts.

Marketo Opportunities (synced from the native CRM connection) migrate to Odoo CRM Opportunities. The Marketo opportunity name, amount, close date, and stage map to Odoo Opportunity fields. We create Odoo pipeline stages that correspond to Marketo opportunity stages before migration so that stage assignments land correctly. Marketo opportunity-to-contact links become Odoo Opportunity-Contact references.

Marketo activity records (email opens, page views, form fills, web visits, clicks, score changes) split into Odoo's discrete engagement objects. Form fills and page visits map to Odoo Task records with activity type recorded; calls map to Odoo Call records; meetings map to Odoo Meeting records. We use the Bulk Activity Extract API for large activity sets and preserve the original activity timestamp for timeline ordering. Not all ~70 Marketo activity types have Odoo CRM equivalents — unmatched types are logged in a custom Odoo activity log.

Marketo Custom Activities — user-defined event types beyond the standard 70 — migrate to Odoo Tasks with a custom Activity Type field that we pre-create in Odoo Studio to match the Marketo Custom Activity name. Each custom activity attribute becomes a custom field on the Odoo Task. We validate field types against the Marketo Custom Activity field type glossary (Boolean, Currency, Date, Datetime, Email, Float, Integer, Percent, Phone, String, URL) before mapping.

Marketo Custom Objects with one-to-many (single link field) or many-to-many (two link fields) relationships require pre-creation of equivalent Odoo models in the destination database. We use Odoo's object-relational model to create the related model with the appropriate fields, then build the many-to-many table for N:N relationships. This work happens before any data import so that foreign key references resolve at migration time. Dedupe fields from Marketo Custom Objects become Odoo unique constraints on the custom model.

Marketo Static Lists — fixed sets of Person records — do not have a direct Odoo CRM equivalent. We extract the list membership and reconstruct it in Odoo as Contact Groups (Odoo's tag-based segmentation model). The static list name becomes the group name; each member person ID resolves to the corresponding Odoo Contact ID. Customer chooses between Odoo native Groups or a dedicated mailing list module during scoping.

Marketo Programs (Email Programs, Event Programs, Engagement Programs, Default Programs) carry period costs, tags, and channel assignments that are platform-specific automation artifacts. We do not migrate Programs as functional equivalents in Odoo CRM because Odoo does not have a native Program container concept. We deliver a written inventory of every Program with its channel, period cost, tags, and member count so the customer's Odoo admin can recreate the audience segmentation in Odoo Groups or a dedicated marketing automation module if licensed.

Marketo Smart Campaigns contain Smart List filters, trigger conditions, and flow steps — a campaign logic model with no direct Odoo equivalent. We extract Smart Campaign structure as structured metadata (triggers, filter logic, flow actions, cadence) and deliver it as a written inventory for the customer's admin to rebuild in Odoo Studio server actions or a workflow automation tool. We do not migrate Smart Campaign logic as executable code.

Marketo Engagement Programs hold up to 25 Streams each with up to 125 content items — a Marketo-specific nurture cadence artifact. Odoo CRM has no native engagement streaming equivalent. We extract the stream structure, content item list, and cadence schedule as a written document. If the customer licenses Odoo's Mass Mailing or Email Marketing module, we note how content items map to Odoo email templates and the cadence maps to scheduled server actions.

Marketo Channels (Email, Event, Webinar, etc.) and Tags — used to classify Programs — migrate as Odoo CRM Tags on Contact, Company, and Opportunity records. We extract channel and tag assignments from Program records and map them to Odoo tags with the channel name prefix preserved for clarity.

Marketo lead and contact scoring models (demographic and behavioral) are configuration artifacts stored as rule sets, not as data records. We extract scoring rules as structured metadata and deliver them as a written scoring model document for the customer's Odoo admin to implement in Odoo Studio or a custom module. Odoo CRM does not have native predictive scoring; the rebuilt model would use Odoo server actions triggered by field changes.

Marketo Workspaces and Partitions (Prime and above) isolate data by brand or region. Odoo handles multi-company isolation via its Multi-Company feature at the database level. We map each Marketo Workspace or Partition to a corresponding Odoo Company record, with Contact and Opportunity records scoped to the correct Odoo Company. This requires Odoo Enterprise or Odoo.sh with multi-company enabled.

Marketo Owners (sales reps and marketing users) map to Odoo CRM User records. We extract all distinct Owner IDs and emails from Person, Company, and Opportunity records and match by email to Odoo Users. Owners without a matching Odoo User are held in a reconciliation queue for the customer's admin to provision before record import resumes.