Migrate from Marketing Tools Growth Marketing Platform to Odoo CRM

Marketing Tools contacts map directly to Odoo CRM contacts with standard fields (name, email, phone, mobile, website) transferred via the Odoo import CSV or external API. We preserve the original contact ID in a custom field x_src_id for audit. Contact-company linkage is resolved at import time by matching the company domain or name from the contact export against the Odoo company records, which we create first in dependency order.

Marketing Tools company records map to Odoo CRM companies. The company name becomes the Odoo company name; domain becomes the website field; address fields map to street, city, state, country, and zip on the company form. Companies are imported before contacts so that the contact-company relationship is satisfied at the moment of contact insert. Any company record without a name is flagged for manual review before import.

Marketing Tools deals map to Odoo CRM opportunities. The deal amount maps to Odoo expected_revenue; deal stage maps to a stage value in the Odoo pipeline that we configure before migration. We extract all distinct deal stages from the source, create corresponding Odoo stages with appropriate probability percentages, and assign the stage sequence to match the source workflow order.

Marketing Tools deal pipelines map to Odoo CRM sales teams or pipeline configurations. If the source has multiple pipelines, we create corresponding Odoo CRM teams with their own stage sequences and assign owner-based routing rules. Odoo's team-based pipeline model is less flexible than a pure multi-pipeline approach; we document the mapping during scoping and flag any stage logic that cannot be replicated in Odoo's team configuration.

Marketing Tools segment membership per contact maps to Odoo tags on the contact record. We extract the full list of segments from the source, create Odoo tags with matching names, and set the many2many tags field during contact import. Segment rule logic (the conditional definitions that build segments) is not exportable and must be rebuilt in Odoo using domain filters or manual tagging workflows.

Marketing Tools campaign metadata (name, status, start date, end date, channel) exports from the platform and maps to Odoo CRM campaigns. Campaign performance metrics (open rates, click rates, revenue attribution) are not available via the standard export; we advise customers to export reporting snapshots from the platform's analytics dashboard before cutover and deliver these as reference CSVs alongside the migrated campaign records.

Journey automation definitions are not accessible via export in the source platform. We document every active journey during the discovery call, capture screenshots of the flow diagram, and list the trigger conditions, branch logic, and action steps in a written inventory. The customer's admin rebuilds equivalent automation in Odoo using Automated Actions, Server Actions, or base.automation rules. This is not migration scope; it is a deliverable for the admin team to execute post-migration.

The source platform's custom object schema is not publicly documented. Where customers report custom object usage, we attempt field-level mapping during scoping by requesting API access or sample export files from the customer. Odoo supports custom models via Odoo Studio with fields, relational models, and computed fields. We pre-create the destination custom model in Odoo before data import and flag any source custom objects that cannot be mapped due to undocumented schema.

Marketing Tools tags export as flat key-value pairs per contact. We map them to Odoo CRM tags on the contact record using the same tag name. Tags exceeding Odoo's 32-character limit are truncated and flagged in the reconciliation report. Multi-value tags per contact map to multiple Odoo tag entries on the same contact record.

Marketing Tools owners map to Odoo CRM users. We resolve owners by email match against the Odoo destination user list. Any source owner without a matching Odoo user is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive source owners map to Odoo inactive users with a note in the record.

Marketing Tools email engagements map to Odoo CRM mail.message records linked to the contact. The email body, subject, and timestamp transfer to the message record. Odoo does not natively store a separate engagement history object; messages attached to the contact thread serve as the activity timeline. We set the mail.message date to the original engagement timestamp for chronological ordering.

Marketing Tools call engagements map to Odoo CRM notes or tasks with call disposition metadata stored in custom fields. Duration, call outcome, and any notes from the call transfer to a note attached to the contact record. Odoo does not have a native call engagement object; we use the note model with a custom field x_call_duration and x_call_disposition to preserve call metadata.

Marketing Tools meeting engagements map to Odoo CRM calendar.event records linked to the contact. Start datetime, end datetime, location, and meeting title transfer to the Odoo event. Attendee information from the source meeting is stored as a note attachment on the event for reference.

Marketing Tools task engagements map to Odoo CRM project.task records attached to the CRM pipeline or to Odoo todo.task records on the contact. Task status, priority, due date, and description transfer to the Odoo task fields. Task assignment resolves the source owner to the destination Odoo user via email match.

Marketing Tools notes migrate to Odoo CRM notes attached to the contact record. Note body transfers as plain text; any attachments associated with the note are flagged as a manual export item because the source platform does not expose attachments via standard export.