Migrate from Dynamics 365 Marketing to Odoo CRM

Dynamics 365 Contact records (msdyn_contact) map directly to Odoo res.partner. Standard fields (name, email, phone, address) use straightforward field-to-field mapping. We preserve the original lifecycle stage (subscriber, lead, MQL, SQL, customer) as an Odoo tag on the res.partner record for segmentation reference. The Contact-to-Account relationship resolves via the parent_id lookup at migration time after Account records are loaded first.

Dynamics 365 Leads (unqualified prospects that have not been converted to Contacts) merge into Odoo res.partner because Odoo CRM does not have a separate Lead object at the Contact layer. The original Lead_Status and lead score from Dynamics migrate as tags on the res.partner record. If the customer requires a separate unqualified-pipeline view, we configure Odoo's CRM pipeline with an initial stage named Unqualified/Legal to which these records are assigned at import time.

Dynamics 365 Account records map to Odoo res.partner with type=company. The Account name becomes the company name, and the domain becomes the website field. Account hierarchies (parent-account structures) map to Odoo's contact hierarchy via the parent_id field on res.partner. Industry, address, and custom account fields migrate as Odoo custom fields or tags depending on field cardinality.

Dynamics 365 Opportunities from the underlying Dataverse CRM layer (msdyn_opportunity) map to Odoo crm.lead. Pipeline stage from Dynamics maps to Odoo's stage_id within the CRM pipeline view. Estimated close date, amount, probability, and owner assignment migrate directly. The opportunity-to-contact and opportunity-to-account lookups resolve via the Account and Contact records already imported. We configure Odoo's CRM stages to match the Dynamics pipeline stages before import.

Dynamics 365 Marketing email templates (msdynmkt_email) contain HTML body, subject line, sender details, and preheader text. Odoo CRM does not have a native marketing email template store separate from its transactional email templates (mail.template). We preserve the email subject, HTML body, and sender address as a custom field on Odoo's mail.template model so that the customer's marketing team has the content documented for rebuild in their chosen marketing automation platform. The automated send logic (Journey triggers) does not migrate and is documented separately.

Customer Journey definitions in Dynamics 365 Marketing (msdynmkt_journey) include trigger conditions, branch logic, wait delays, and action steps. Odoo CRM has no Journey or marketing automation equivalent. We extract the Journey configuration (trigger type, conditions, steps, and step order) and preserve it as a document in the customer's migration handoff package. The customer's marketing team uses this as a specification to rebuild Journey logic in Marketo, Mailchimp, HubSpot Marketing, or another marketing automation platform. We do not migrate Journey logic as executable code.

Customer Insights segments are stored in the Customer Insights - Data service, which is separate from the core Dataverse CRM database. We execute a separate export pass for segment definitions and membership data. Static segments (explicit member lists) map to Odoo crm.lead.group records with members linked to the corresponding res.partner records. Dynamic segments (criteria-based) cannot be replicated in Odoo CRM and are documented with their full criteria expression for rebuild in a marketing automation platform. Segment memberships are imported after all contact records are present in Odoo to avoid orphaned references.

Custom entities created within a Dataverse managed solution require the customer to provide the managed solution ZIP or schema export from the Configuration Migration Tool before we can map them. We do not infer custom entity structure from UI exports because UI exports do not capture relationship metadata, field security profiles, or managed property settings. Custom entities map to Odoo custom fields on res.partner, crm.lead, or as separate Odoo Studio models depending on the entity's structure and lookup relationships.

Dynamics 365 ActivityPointer records (Email, Task, PhoneCall, Appointment) map to Odoo mail.activity with the activity_type field set to email, call, meeting, or pending. The activity subject, note, and date migrate directly. The regarding object lookup (objectid and objecttypecode) resolves to the migrated res.partner or crm.lead record. Activity owner assignments migrate as Odoo user assignments. We process activities in a separate pass after all parent contact and opportunity records are present.

Dynamics 365 Annotations (notes with file attachments) are exported individually with the objectid and objecttypecode preserved. We re-associate attachments with their parent record in Odoo via ir.attachment with res_model=res.partner or crm.lead and res_id pointing to the migrated record. We handle annotations in a separate pass after the parent records are loaded. The original filename and any inline note body migrate as Odoo attachment name and description.

Dynamics 365 Marketing Lists contain member records with list-type (static or dynamic) and are associated with Campaigns. Odoo CRM does not have a native Marketing List equivalent. Static Marketing List membership is preserved as Odoo crm.lead.group records with member links to the corresponding res.partner records. Dynamic Marketing Lists (query-based) are documented with their original query criteria for rebuild as a segment in the customer's chosen marketing automation platform.

Dynamics 365 Campaigns and Campaign Activities (the legacy marketing model) map to Odoo utm.campaign with the campaign name, status, budget, and dates preserved. Campaign Activities are documented as campaign milestones or tasks within the Odoo Campaign because Odoo does not have a separate Campaign Activity object. The association between Campaign and Marketing List members is preserved in the Group migration. Microsoft Dynamics campaign response records are documented as campaign tags in Odoo.

Dynamics 365 systemuser records and owner assignments on CRM records map to Odoo res.users. We resolve owners by email match against the destination Odoo user list. Any Dynamics Owner without a matching Odoo user is held in a reconciliation queue for the customer's admin to provision before record import resumes. The Dynamics user role (salesperson, marketing manager, administrator) migrates as a tag on the res.users record for access-control planning in Odoo.

Dynamics 365 Marketing Contact billing is triggered at the tenant level based on contact record properties. The marketing contact flag has no Odoo CRM analog because Odoo does not have a native marketing automation billing model. We preserve the original billing eligibility status as a custom field on res.partner so that if the customer later integrates a marketing automation tool (Marketo, Mailchimp, HubSpot), the segmentation data is already present and does not require a second export from Dynamics 365.