Migrate from Odoo Marketing Automation to Microsoft Dynamics 365 Sales

Odoo res.partner records with type = 'contact' map to Microsoft Dynamics 365 Contact. The Odoo partner ID becomes the source_reference field for deduplication. Email, phone, mobile, street, city, country, and custom fields migrate directly. The partner's parent_id (linking to a company-type partner) resolves to an Account on the destination before Contact insert so that the accountid lookup is satisfied. Tags stored as a many2many tag_ids relation flatten to a string array on the Contact custom attribute.

Odoo res.partner records with type = 'company' map to Dynamics 365 Account. Company name becomes the Account Name field, website migrates to Account WebSite URL, and street/city/country/phone map to the standard Address and Phone columns. The Odoo partner ID is preserved as source_reference for reconciliation. Account is created before any Contact import because the Contact-to-Account lookup is a hard requirement on the Dynamics 365 Contact insert.

Odoo CRM Leads map directly to Dynamics 365 Lead. Lead name, email, phone, company name, source, priority, and stage all have direct column equivalents in the Dynamics 365 Lead table. The Odoo lead_stage_id maps to Lead Status via a staging table we build during scoping. Custom fields on the Odoo CRM lead model migrate as custom columns on the Dynamics 365 Lead entity. Lead scoring values stored as custom float fields on Odoo migrate to a custom integer field on Lead.

Odoo CRM Opportunities map to Dynamics 365 Opportunity. The Odoo stage name maps to Dynamics 365 StageName via a per-pipeline mapping table. Expected revenue, partner (account link), lost reason, and priority migrate directly. Close date migrates to EstimatedCloseDate. If the Odoo database has multiple CRM pipelines, each maps to a separate Microsoft Dynamics 365 Sales Process or Opportunity Record Type. Closed-Won and Closed-Lost outcomes are preserved as stage names rather than separate status flags.

Odoo Marketing Automation Campaigns map to Dynamics 365 Campaign. Campaign name, target model (Contact, Lead, or Sales Order reference), audience domain filter, and state (draft, running, done, cancelled) migrate as Campaign metadata. Traces and activity logs (which contact entered which campaign under which condition) migrate as CampaignActivity records linked to the Campaign. Note that Dynamics 365 Campaign is a container for marketing initiatives rather than a trigger-based automation engine.

Automation Rules from Odoo Marketing Automation cannot migrate as executable code. We extract every rule's name, trigger type (time-based, email event-based, server action, record update), filter domain, action chain, and activity sequence and present them as a written inventory document. The customer's admin or a Power Automate specialist uses this inventory to rebuild the automation logic in Power Automate, which uses a different trigger-condition-action model. Rules containing Python Code activities are flagged separately with a note that the logic requires a custom connector or Azure Function replacement.

Odoo Email Marketing templates (name, subject, body HTML, inline images) migrate as Dynamics 365 Email Template records. The HTML body transfers as-is; inline image URLs that reference Odoo's /web/binary/ path are flagged for manual re-hosting on SharePoint or Dynamics 365 marketing asset storage. Variable placeholders using Odoo's {{ }} syntax require conversion to Dynamics 365 token syntax ({{contact.firstname}}) during template import.

Odoo Mass Mailings (sent email records from Email Marketing) contain subject, recipient count, scheduled date, and body HTML. We migrate the most recent 12 months of Mass Mailing records as CampaignActivity entries linked to the parent Campaign, preserving subject, send date, and recipient count. Full email body content migrates via the Email Template object. Older mass mailings beyond the 12-month window migrate as counts and metadata only.