Migrate from Odoo CRM to Microsoft Dynamics 365 Sales

Odoo crm.lead records with type='lead' map directly to Dynamics 365 Lead. The Odoo lead name becomes Lead.fullname, email_from becomes Lead.emailaddress1, phone becomes Lead.mobilephone or telephone, source_id becomes Lead.leadsource1, and stage_id maps to Lead.statecode (or a custom status field). We use the Odoo crm.lead.id as a legacy key in a custom field odoo_lead_id__c on the destination Lead for reconciliation and cross-reference.

Odoo crm.lead records with type='opportunity' map to Dynamics 365 Opportunity. The partner_id foreign key (res.partner) must resolve to an Account lookup first, so we import Accounts before Opportunities. Key field mappings: planned_revenue becomes Opportunity.estimatedvalue, probability becomes Opportunity.stepid probability (mapped to the Dynamics stage), date_deadline becomes Opportunity.estimatedclosedate, team_id maps to Opportunity.territoryid or a custom team field, and user_id maps to Opportunity.ownerid.

Odoo res.partner is a polymorphic table used for both individuals and organizations. Partners with is_company=True map to Dynamics Account; partners with is_company=False map to Contact linked to the parent Account. The parent_id foreign key in res.partner becomes the Contact.parentaccountid lookup. Email, phone, street, city, country, and vat map to Account/Contact standard address and contact fields. We preserve the original res.partner.id in odoo_partner_id__c for reconciliation.

Odoo pipeline stages from crm.stage map to Dynamics Opportunity Stage values. We create a Sales Process in Dynamics 365 that whitelists the migrated stage names, preserving the Odoo stage sequence order and probability percentages (rounded to Dynamics' integer-allowed format). Stages are sequenced before any Opportunity data loads.

Odoo crm.team records map to Dynamics 365 Teams or Territory records depending on the customer's reporting structure. Team member_ids from Odoo (res.users) map to Team Membership records in Dynamics. If the customer uses territory-based quota allocation, we map teams to Territory hierarchy; otherwise we use the standard Dynamics Team object.

Odoo mail.activity records linked to crm.lead (via res_id/res_model) migrate to Dynamics 365 Task records. The activity type (call, meeting, email, upload_document, etc.) maps to a custom Task.customertype or TaskSubject field; date_deadline maps to Task.scheduledend; user_id resolves to Task.ownerid; note (HTML body) maps to Task.description or a linked Note. We chunk mail.activity exports by date range to avoid memory exhaustion and preserve the activity timeline ordering via the original Odoo create_date.

Odoo crm.tag records (many2many with crm.lead) map either to Dynamics Topics (via Topic and TopicAssignment) or to a custom multi-select picklist field on Opportunity. The customer selects the strategy during scoping. Tag names are preserved as a flat list, and any tag frequencies are documented for the customer's admin to decide consolidation before import.

Odoo custom fields defined via Studio or in custom addons are stored as columns in crm.lead but have no separate field definition registry in Community. We export field definitions alongside the data during discovery, then pre-create matching custom fields in Dynamics 365 with equivalent types (selection fields become picklists, many2one become lookups, many2many become multi-select picklists or related entities). If the custom field references an Odoo-specific model, we document it as a manual field for the customer's admin to configure post-migration.

Odoo ir.attachment records linked to crm.lead via res_model/res_id migrate to Dynamics Note records with an associated Document (SharePoint or Dataverse file attachment). Large attachment volumes are chunked separately from record data. We remap ir.attachment.res_id to the destination Dynamics record ID using the legacy key mapping built during earlier migration phases.

Odoo sale.order records linked to Opportunities migrate as Opportunity Product line items if the order is open, or as historical Quote records if closed or lost. sale.order.line items (product, quantity, price, tax) map to OpportunityLineItem records. We resolve the Pricebook2 reference, Product2 reference, and parent Opportunity at migration time and flag any orders in draft state as requiring a re-quote workflow in Dynamics.