Odoo CRM to Dynamics 365 migration
We migrate Leads, Opportunities, Contacts, Companies, Pipeline Stages, and Activity history from Odoo CRM into Microsoft Microsoft Dynamics 365 Sales , resolving the Lead-versus-Opportunity split, mapping Odoo's res.partner model to the Contact-and-Account structure, and preserving tag hierarchies and engagement timestamps through the Dynamics 365 Dataverse API before cutover.
FlitStack AI migrates leads, opportunities, account and contacts, opportunity stages and team or territories from Odoo CRM to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Odoo CRM to Dynamics 365?
Moving from Odoo CRM to Microsoft Microsoft Dynamics 365 Sales is a structural remapping: Odoo stores Leads and Opportunities in a single crm.lead table with a type discriminator, while Dynamics separates them into a distinct Lead object and a Contact linked to an Account.
Read the full summary
We resolve that split during scoping by classifying every crm.lead record on its type and stage before generating the correct destination object. Odoo's res.partner (used for both individuals and companies) maps to Contact and Account depending on the partner's is_company flag, with the original partner ID preserved as a legacy key. Activity history (mail.activity) migrates as Dynamics Tasks and Notes linked to the parent Contact or Opportunity via Dataverse. We do not migrate Enterprise-only Odoo features including AI lead scoring rules and automation server actions; we deliver a written inventory of these for the customer's admin to rebuild in Dynamics 365's Power Automate or native workflow designer.
crm.lead (type=lead) → Lead
Odoo crm.lead records with type='lead' map directly to Dynamics 365 Lead.
How it maps
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.
crm.lead (type=opportunity) → Opportunity
Odoo crm.lead records with type='opportunity' map to Dynamics 365 Opportunity.
How it maps
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.
res.partner → Account and Contact (split required)
Odoo res.partner is a polymorphic table used for both individuals and organizations.
How it maps
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.
crm.stage → Opportunity Stage
Odoo pipeline stages from crm.stage map to Dynamics Opportunity Stage values.
How it maps
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.
crm.team → Team or Territory
Odoo crm.team records map to Dynamics 365 Teams or Territory records depending on the customer's reporting structure.
How it maps
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.
mail.activity → Task and Note
Odoo mail.activity records linked to crm.lead (via res_id/res_model) migrate to Dynamics 365 Task records.
How it maps
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.
- crm.leadLead1:1
- crm.leadOpportunity1:1
- res.partnerAccount and Contactsplit
- crm.stageOpportunity Stagetransformed
- crm.teamTeam or Territorytransformed
- mail.activityTask and Note1:1
+ 4 more in the mapping below
How Odoo CRM and Dynamics 365 differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Odoo CRM | Dynamics 365 |
|---|---|---|
| Lead vs Opportunity model | Single crm.lead table with type='lead' or type='opportunity' discriminator | Separate Lead and Contact+Account objects with explicit Convert action |
| Contact and company merging | res.partner serves both individuals and companies via is_company flag | Separate Account (company) and Contact (person) with lookup relationship |
| Pipeline stages | crm.stage ordered per team via many2many relation | Opportunity Stage values scoped by Sales Process and Record Type |
| Custom field handling | Studio and custom-addon fields stored as columns in crm.lead with no separate field registry | Custom fields defined in Dynamics as typed metadata entries with no database column until created |
| Activity model | mail.activity with type, date_deadline, user_id, and note; loosely coupled via res_id/res_model | Task and Note objects linked by Regarding (object) lookup; loosely coupled via RegardingObjectId |
| Pricing model | Community free; per-user per-module on Online/Sh at €20-50/user/month; Enterprise stacked by app | Sales Professional at $65/user/month; Sales Enterprise at $105/user/month; per-user named licensing |
| Sales team structure | crm.team groups members via user_id and member_ids; no dedicated territory model | Territory Management and Teams scoped by Geography, Product Line, or custom criteria |
What to watch for in a Odoo CRM to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
The crm.lead Lead/Opportunity split must be resolved before any Opportunity import
Odoo stores Leads and Opportunities in a single crm.lead table with a type field ('lead' vs 'opportunity').
How we handle it
Dynamics 365 separates these into a distinct Lead object and an Opportunity object with a Contact+Account parent. If crm.lead records with type='lead' are loaded as Opportunities, they will have no Contact or Account lookup and appear orphaned in the pipeline. We detect the type distribution during discovery, apply the split rule as the first transform, and validate the split counts against the source before proceeding to Opportunity import.
Odoo Community XML-RPC may be unavailable; direct PostgreSQL export is required
The Odoo External API (XML-RPC) is free only on the Custom Plan (Odoo Enterprise).
How we handle it
Community edition users on Odoo Online or self-hosted Community do not have guaranteed API access. We check XML-RPC availability during discovery and fall back to a read-only PostgreSQL connection for direct database export when the API is gated. Direct PostgreSQL export also captures custom fields (stored as table columns) that may not be visible through the XML-RPC ORM interface.
Custom fields lose their application context if the custom addon is not deployed on the target
Odoo custom fields defined via Studio or in custom addons are stored as columns in crm.lead and res.partner.
How we handle it
If the defining module is not also deployed on the target environment, the column exists but has no ORM field definition, so the field is invisible in the Odoo UI and cannot be read via XML-RPC. We export field definitions alongside data and pre-create matching custom fields in Dynamics 365 before data loads. Any fields that cannot be type-mapped are documented for the customer's admin to handle manually.
Odoo's many2many Tags require a pre-import strategy decision
Odoo crm.tag uses a many2many relation (crm_lead_rel) rather than a flat string field.
How we handle it
Dynamics 365 does not have a native equivalent; we offer two options: a custom multi-select picklist on Opportunity (simpler, limited to 500 values) or Dynamics Topics with TopicAssignment records (scales to unlimited tags but requires the Topic entity to be enabled). We present both options during scoping and the customer chooses before any tag data is exported.
Enterprise-only Odoo features cannot migrate to any non-Odoo CRM
Odoo AI lead scoring rules (crm.scoring.rule) and automation server actions (base.action.rule scoped to CRM) are Enterprise-exclusive and have no equivalent in Microsoft Microsoft Dynamics 365 Sales .
How we handle it
These do not migrate. We export a written inventory of every active Enterprise module, automation rule, and scoring rule with the module name, trigger, conditions, and recommended Dynamics Power Automate equivalent. The customer's admin rebuilds these post-migration as separate work.
How the migration runs
Discovery and source audit
We audit the source Odoo database via XML-RPC (Enterprise) or direct PostgreSQL read-only connection (Community).
What this step covers
The audit covers: crm.lead record count and type distribution (lead vs opportunity), res.partner count with is_company flag breakdown, crm.stage and crm.team counts, mail.activity volume and date range, crm.tag distinct values, custom fields (ir.model.fields entries for crm.lead and res.partner), Enterprise-only module detection (ir_module_module entries flagged as Enterprise), and sale.order linkage to crm.lead. We produce a written migration scope document before any data is extracted.
Lead/Opportunity split rule and destination schema design
We define the split rule: all crm.lead records with type='lead' become Dynamics Lead; type='opportunity' become Dynamics Opportunity.
What this step covers
We design the Dynamics destination schema in a Sandbox: custom fields on Lead and Opportunity matching Odoo custom field types, Opportunity Stages preserving the Odoo stage sequence and probability, Sales Process scoping the stage whitelist, Account and Contact standard fields, and any custom Team or Territory structure matching the Odoo crm.team. Schema is validated in Sandbox before production migration begins.
Owner and User reconciliation
We extract every distinct user_id referenced on crm.lead, mail.activity, crm.team, and sale.order records.
What this step covers
Each Odoo res.users record is matched by email to the Dynamics 365 destination User table. Users without a match enter a reconciliation queue for the customer's admin to provision before record import. OwnerId references on Lead, Opportunity, and Task cannot be satisfied without an active User in Dynamics 365.
Sandbox migration and reconciliation
We run a full migration into a Dynamics 365 Sandbox using a representative data sample.
What this step covers
The customer's RevOps lead spot-checks 25-50 records against the Odoo source for field accuracy, verifies the Lead/Opportunity split counts, confirms Account-Contact parent relationships, and validates activity timeline ordering. Any mapping corrections are made in the sandbox before the production migration phase begins.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Odoo res.partner where is_company=True), Contacts (from res.partner where is_company=False with parentaccountid resolved), Leads (from crm.lead type='lead' with owner resolved), Opportunities (from crm.lead type='opportunity' with AccountId, OwnerId, and stage resolved), Tasks (mail.activity via Dataverse API with parent-record lookup), Tags (as multi-select picklist or Topic), Custom fields (filled after base objects are stable), Attachments (as Notes with Document links), and sale.order line items (as Opportunity Products).
What this step covers
Each phase emits a row-count reconciliation report before the next begins.
Cutover, validation, and Enterprise-feature handoff
We freeze Odoo writes during the cutover window, run a final delta migration of any records modified during the migration window, then enable Dynamics 365 as the system of record.
What this step covers
We deliver the Enterprise feature inventory (scoring rules, automation actions, Enterprise-only modules) as a written document for the customer's admin to rebuild in Power Automate or Dynamics workflows. We support a one-week post-cutover window for reconciliation issues. Workflow rebuild, Power Automate setup, and admin training are outside standard migration scope and are handled as separate engagements.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and how many Odoo modules are in scope. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Odoo CRM to Dynamics 365 →Why teams move from Odoo CRM to Dynamics 365
- Email and Gmail integration reliability is a recurring pain point across G2 and Reddit reviews of Odoo CRM. Teams report that email threads drop, conversations scatter across inboxes, and the Odoo-Gmail sync breaks under common configurations. Microsoft Microsoft Dynamics 365 Sales provides native Outlook and Teams integration through the Dataverse API, giving sales teams a reliable communication record that stays inside the CRM without third-party middleware or manual synchronization steps.
- Odoo Enterprise pricing stacks quickly as teams add apps. Multiple modules at per-user rates (€25-50/user/month) plus Odoo.sh hosting reaches €30-50/user/month for a team using CRM plus one other app, which exceeds what many mid-market teams anticipated. Microsoft Microsoft Dynamics 365 Sales Professional at $65/user/month includes pipeline management, forecasting, and Copilot-assisted insights with no per-module stacking, and it bundles tightly with existing Microsoft 365 subscriptions.
- Companies operating across multiple regions or regulated industries need enterprise compliance support, multi-entity management, and global infrastructure that Odoo Community cannot provide without significant custom development. Microsoft Dynamics 365 Sales runs on Microsoft's global Azure infrastructure with built-in GDPR compliance tooling, audit logging, and data residency controls that Odoo self-hosted deployments must implement manually.
- Odoo version upgrades between major releases (17 to 18, 18 to 19) frequently break custom module view definitions and XPath expressions, and Enterprise customers report that critical bugs during upgrades go unresolved for weeks. Teams moving to Dynamics 365 gain a continuously updated SaaS platform with predictable release cycles and named-user licensing that does not require infrastructure management or manual version alignment.
Questions, answered
Odoo CRM to Dynamics 365 migration questions
How long does an Odoo CRM to Microsoft Microsoft Dynamics 365 Sales migration take?
Migrations under 15,000 Contacts and 3,000 Opportunities with no custom fields and a clean crm.lead type distribution land between three and five weeks. Migrations with Odoo Studio custom fields, multi-team pipeline configurations, large activity histories (over 200,000 mail.activity records), or linked sale.order quotations move to seven to twelve weeks because of Dataverse API chunking, stage-probability mapping, and parent-record resolution work.
Do Odoo automation rules, AI lead scoring, and Enterprise modules migrate to Dynamics 365?
No. Odoo automation server actions (base.action.rule), AI lead scoring rules (crm.scoring.rule), and Enterprise-only modules (CRM Enterprise, Documents, WhatsApp, Social) have no equivalent in Microsoft Microsoft Dynamics 365 Sales and cannot be migrated as functional code. We export a written inventory of every active automation rule and scoring model with its trigger, conditions, and a recommended Power Automate equivalent. The customer's admin or a Microsoft partner rebuilds them post-migration.
How do we handle Odoo custom fields (Studio or custom addons)?
Odoo custom fields stored as columns in crm.lead are fully exportable via direct PostgreSQL read or XML-RPC. We pre-create matching custom fields in Dynamics 365 with equivalent types before data loads: selection fields become picklists, many2one fields become lookups, and many2many fields become multi-select picklists. If a custom field references an Odoo-specific model with no Dynamics equivalent, we document it for the customer's admin to handle as a manual field configuration post-migration.
How do we preserve email and activity history from Odoo?
Odoo mail.activity records migrate to Dynamics 365 Task and Note objects linked to the parent Contact, Lead, or Opportunity via the RegardingObjectId lookup. The activity type, date_deadline, user assignment, and note body all transfer. Activity timeline ordering is preserved by setting the scheduled end date to the original Odoo create_date timestamp. We chunk the activity export by date range to stay within Dataverse API batch limits.
Can we migrate from Odoo Community (no API access) to Dynamics 365?
Yes. Odoo Community edition does not include XML-RPC API access by default. We connect directly to the PostgreSQL database with a read-only user to extract crm.lead, res.partner, crm.stage, crm.team, mail.activity, crm.tag, and ir.attachment records. We export field definitions alongside data and remap them to the Dynamics 365 schema. This approach also captures custom fields that may not be exposed through the Odoo ORM if the custom module has not been properly initialized.
What happens to Odoo sale orders linked to CRM Opportunities?
Odoo sale.order records linked to crm.lead (opportunity) migrate as Opportunity Product line items in Dynamics 365 if the order is in a confirmed state, or as historical Quote records if the order is draft, cancelled, or lost. Open sale orders that need further negotiation after cutover require a re-quote workflow in Dynamics 365, which the customer's admin sets up post-migration. We document every order state and flag orders in draft as requiring manual review.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Dynamics 365 to Odoo CRMThe same pair in reverse HubSpot to Dynamics 365Mapping · history · rollbackBitrix24 to Dynamics 365Mapping · history · rollbackZendesk Sell to Dynamics 365Mapping · history · rollbackZoho CRM to Dynamics 365Mapping · history · rollbackMailchimp to Dynamics 365Mapping · history · rollbackSalesforce to Dynamics 365Mapping · history · rollback Odoo CRM to Zoho CRMMapping · history · rollbackOdoo CRM to HubSpotMapping · history · rollbackOdoo CRM to SalesforceMapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Export and import data — Odoo 19.0 documentation
- Import products — Odoo 19.0 documentation
- Odoo Online programmatic throughput limits — Odoo Forum
Get a quote
Moving from Odoo CRM to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote