Which Dynamics products can you migrate from?

Dynamics 365 Business Central (cloud + on-prem), Dynamics 365 Finance & Operations, legacy Dynamics NAV (2009 onwards), Dynamics AX (2009 / 2012), Dynamics GP (2010 onwards). Each has its own migration approach; the underlying methodology is the same.

Will Odoo replace what we get from the Microsoft ecosystem integration?

Honest answer: not 1:1. Dynamics's tight integration with Microsoft 365, Power Platform, Power BI, Azure AD is a real feature. Odoo integrates with all of these but as a peer system, not native. For businesses where the Microsoft integration is load-bearing operationally, this is a real consideration. For most mid-market businesses, the integration value doesn't justify the per-app premium.

How does the migration handle Dynamics dimensions / financial dimensions?

Dimensions map to Odoo's analytic accounting, which is functionally equivalent but more flexible (more dimensions, hierarchy support, dynamic creation). Existing dimension values and hierarchies migrate; we usually expand the dimension model in Odoo because the Dynamics 8-dimension limit doesn't apply.

What about Business Central extensions from AppSource?

AppSource extensions (third-party BC apps) don't port. Each extension audited during discovery — most have direct Odoo Marketplace equivalents or native Odoo features. Where an AppSource extension is genuinely irreplaceable for an industry-specific need, we either build a custom Odoo equivalent or keep BC for that specific entity. Rare case.

Can you migrate from F&O without a partner-led re-implementation?

Yes — that's the whole point. F&O customers commonly face 'you'll need a 12-month partner re-implementation to upgrade' messaging. Our F&O → Odoo migration takes 20–28 weeks at fixed price, with comparable functional coverage for sub-500-user businesses. We've done it.

What about Dynamics CRM (Customer Engagement)?

Dynamics CRM data migrates to Odoo CRM during the project — leads, opportunities, accounts, contacts, activities, customisations. Most ex-Dynamics CRM customers find Odoo CRM sufficient for sales pipeline and account management; complex enterprise sales motions sometimes warrant keeping Salesforce or HubSpot synced with Odoo.

Will my Power BI reports continue to work?

Two paths: (1) repoint Power BI to Odoo's data via the Power BI connector — works for most reports; (2) rebuild reports as Odoo native dashboards — typically faster, simpler, no separate BI tool to maintain. Most customers pick (2) and reduce stack count.

How do AL extensions compare to Odoo customisations on maintenance cost?

AL extensions on BC are partner-built and maintained against BC's release cycle (every 6 months). Odoo customisations on Enterprise are Python and maintained against Odoo's release cycle (annual). Both require ongoing maintenance; Odoo customisations are typically cheaper per hour and have a broader partner pool, so total maintenance cost over 3 years is meaningfully lower.

Does Odoo support SOX compliance like Dynamics F&O does?

Odoo's audit trail, segregation of duties enforcement, and approval framework are sufficient for SOX in most mid-market scopes. F&O's enterprise-tier features (deeper SoD, complex internal controls testing) exceed Odoo. For SOX-listed companies with deep internal-controls requirements, this is a real consideration — assess during discovery.

Can we keep Azure AD / Microsoft Entra for SSO into Odoo?

Yes. Odoo supports SAML and OAuth 2.0 / OIDC. We configure Entra ID as the IdP during migration so users keep their existing SSO into Odoo with no separate password.

What about end-of-support pressure on NAV / GP / AX?

Dynamics NAV mainstream support ended in 2018 (extended support 2028). Dynamics GP mainstream support ends 2028. Dynamics AX is similar. Microsoft pushes upgrade to BC or F&O. Many mid-market businesses find migrating to Odoo cheaper than the prescribed BC / F&O upgrade — and Odoo's release cycle remains supported indefinitely.

What's the first step?

A 45-minute call. Bring: Dynamics variant (BC / F&O / NAV / AX / GP), version, user count, legal entity count, top 3 modules, and rough AL or X++ estate size. We'll tell you whether discovery is worth scheduling and what the realistic project size looks like.

Migration playbook

Migrate from Microsoft Dynamics to Odoo

Microsoft Dynamics covers two products with very different migration paths — Dynamics 365 Business Central (the SMB/mid-market platform descended from Navision) and Dynamics 365 Finance & Operations (the upper-mid/enterprise platform descended from Axapta). This playbook covers both, plus the older NAV / GP / AX installations still common in the wild. We've migrated all of them. The common thread: customers leave Dynamics when Microsoft's per-user-per-app licensing compounds beyond the value delivered.

Last reviewed: May 12, 2026

Why businesses migrate from Microsoft Dynamics 365 to Odoo

Per-app licensing compounding

Dynamics 365 per-user-per-app pricing means each function (Finance, Supply Chain, Sales, Customer Service, Field Service, etc.) carries its own per-user-per-month fee. For a 50-user business needing 4 apps: USD 80–210/user/month × 50 × 4 apps × 12 = USD 192,000–504,000/year. Odoo Enterprise Custom is one all-in price.
AL / X++ customisation lock-in

Business Central customisations live in AL (Application Language); F&O / AX customisations in X++. Both are partner-built and partner-maintained. Switching partners is expensive because new partners often rebuild. Odoo's Python framework has a wider, cheaper partner pool globally.
Microsoft Stack lock-in feels heavier than it's worth

Dynamics is sold as integrated with Microsoft 365, Power BI, Power Automate, Azure. For businesses where this integration is operationally critical, it's worth the price. For businesses where it's nice-to-have but not load-bearing, the per-app premium often exceeds the integration value. Odoo integrates cleanly with Microsoft 365 anyway.
Renewal pricing increases (BC SaaS)

Microsoft pricing typically increases 5–15% annually on commercial cloud subscriptions. Combined with feature-gating (e.g. moving capabilities to higher-priced tiers), customers see effective rate increases of 15–25%. Multi-year commitments lock pricing but require advance forecasting.
F&O / AX legacy on aging infrastructure

AX 2009 / 2012 installations still running in 2026 are common — but on aging on-premises infrastructure with mounting support and security risk. The forward path Microsoft prescribes is F&O cloud migration; many customers find Odoo a cheaper, faster alternative for the mid-market subset of these.
NAV / GP end-of-life pressure

Dynamics NAV mainstream support ended in 2018; extended support ends 2028. Dynamics GP mainstream support ends mid-2028. Microsoft's path forward is upgrade to Business Central, which is effectively a re-implementation. For mid-market customers, Odoo is a competitive alternative to BC at materially lower TCO.
Manufacturing on Dynamics feels heavyweight

BC Manufacturing covers basics; F&O Manufacturing is deep but expensive. Mid-market manufacturers sometimes end up in the F&O tier just to access manufacturing depth. Odoo Manufacturing handles MRP I and II at no incremental module cost.
Multi-entity consolidation costs scaling

Dynamics multi-entity setups (per legal entity in F&O, separate companies in BC) work well but the per-user-per-app licensing compounds across entities. Each entity needs licenses; some Dynamics customers pay for users who only need read-access in some entities. Odoo's single-user-across-companies model is more efficient.

What survives the migration

Plain-English breakdown of what we move, what we re-map, and what gets rebuilt in Odoo's framework rather than ported.

Data category	Coverage	Detail
Customers	Fully migrated	All customer records migrated as Odoo contacts with addresses, contact persons, tax codes, payment terms, credit limits, dimensions / segments, opening AR balances. Multi-currency customers preserved.
Vendors	Fully migrated	Vendor records with banking, payment terms, 1099 (US), VAT registrations, dimension/segment tagging, opening AP balances.
Items	Fully migrated	Item master with SKUs, descriptions, item categories, costs (including landed cost), prices, units of measure. Item attributes (BC) and product variants (F&O) migrate to Odoo's variant model.
Chart of accounts (G/L Accounts)	Partial / mapped	BC's G/L Account structure and F&O's main accounts mapped to Odoo's CoA. Dimensions (BC) and Financial Dimensions (F&O) become Odoo's analytic accounting — usually a cleaner separation than the source.
Opening balances	Fully migrated	G/L balances per legal entity, AR, AP, fixed assets, accumulated depreciation, inter-company balances — reconciled to cutover date. Multi-legal-entity reconciliation is the longest task for F&O migrations.
Stock opening balances	Fully migrated	Item ledger entries (BC) or inventory transactions (F&O) summarised to opening stock by item by location with cost. Costing methods translated.
Transactional history (1–3 years)	Partial / mapped	Sales invoices, purchase invoices, payments, receipts, journal entries migrated for historical reporting. Older history stays in BC / F&O read-only.
Open documents	Fully migrated	Open sales orders, purchase orders, transfer orders, posted-but-not-invoiced shipments, in-transit items — full state. Team picks up mid-flow.
Production BOMs and routes (manufacturing)	Fully migrated	Production BOMs, routings, work / machine centres, formulas migrate to Odoo BOMs. F&O's coproduct / byproduct structures preserved.
Legal entities / companies (multi-entity)	Fully migrated	BC companies become Odoo companies. F&O legal entities become Odoo companies. Inter-company workflows and consolidation re-implemented in Odoo's native multi-company setup.
Dimensions / Financial Dimensions	Fully migrated	Dynamics' dimension framework (departments, projects, cost centres, etc.) maps to Odoo's analytic accounting which is more flexible. Existing dimension hierarchies preserved.
AL extensions (Business Central)	Rebuild in Odoo	AL extensions don't port. Inventoried during discovery, classified, rebuilt as Odoo customisations in Python. Most AL extensions shrink in the rebuild because Odoo's defaults cover more.
X++ customisations (F&O / AX)	Rebuild in Odoo	X++ customisations don't port. Same approach — inventory, classify, rebuild in Python. F&O's customisation depth is substantial; this is the longest sub-project for F&O migrations.
Power Automate flows / Power Apps	Rebuild in Odoo	Power Platform integrations rebuilt as Odoo automated actions or external automation (Make.com, Zapier, n8n) where customers want to keep them. Most Power Automate flows shrink to Odoo automated actions.
RDLC reports / SSRS reports	Rebuild in Odoo	Custom RDLC (BC) and SSRS (F&O) reports rebuilt as Odoo native reports, dashboards, or Spreadsheet views. Document each report's actual usage; rebuild only what's load-bearing.
Users, roles, security	Rebuild in Odoo	BC permission sets and F&O security roles re-created in Odoo's RBAC. Migration is usually a chance to consolidate security role drift and simplify access patterns.

Our phased approach

Discovery 1–2 weeks
1–2 weeks, fixed-price

Senior consultant + technical lead audit Dynamics — variant (BC / F&O / NAV / AX), legal entities, modules, AL or X++ estate, integrations. Discovery is 1 week for BC, 2 weeks for F&O. Output: written migration plan + fixed-price quote.
Sandbox migration
6–12 weeks

Migration scripts built against Dynamics APIs (BC API or F&O OData), run into sandbox Odoo, reconciled per legal entity. Your finance team validates per-entity. Iterations expected — Dynamics data depth means edge cases.
Odoo configuration in parallel
5–9 weeks (overlapping)

Country localisations per legal entity (US sales tax, UK MTD, EU VAT, India GST, etc.). AL / X++ customisations rebuilt in Python. Integrations migrated from Microsoft connectors to Odoo equivalents.
User training
2–3 weeks

Role-based training in sandbox Odoo per legal entity. Dynamics users typically familiar with Microsoft-style UX; Odoo's UI is broadly familiar but distinct enough that training is non-trivial.
Cutover weekend
1 long weekend

Dynamics closes for new transactions Friday evening. Final migration runs Saturday and Sunday. Reconciliation Sunday/Monday with finance + auditor sign-off. Monday/Tuesday: team starts in Odoo.
Parallel-run period
3–4 weeks

Both Odoo and Dynamics accessible. New transactions in Odoo only; Dynamics read-only. We monitor every flow, fix anything that surfaces, validate at least one month-end close per legal entity in Odoo before decommissioning Dynamics.
Stabilisation
60 days post go-live

On-call engineering for 60 days. Weekly status. By day 60, finance has closed two month-ends across all entities in Odoo, and we transition to normal support.

Typical timeline

Business Central: 12–18 weeks. Dynamics F&O / AX: 20–28 weeks. NAV (legacy): 14–20 weeks. GP (legacy): 12–16 weeks. Variables: (1) variant; (2) legal entity count; (3) AL / X++ estate size; (4) industry compliance overhead. Discovery week confirms timeline against your specific scope.

Indicative cost

USD 35,000–100,000 fixed-price for end-to-end migration + Odoo go-live. BC: USD 35,000–70,000 typical. F&O / AX: USD 60,000–150,000 (rarely above USD 100,000 for mid-market scope). Discovery: USD 3,500–6,000 fixed, deductible. Compare to Dynamics ongoing: USD 80,000–250,000+/year subscriptions + USD 30,000–80,000/year partner support. Three-year TCO advantage to Odoo: USD 150,000–500,000.

Risks and mitigations

Risk: AL / X++ customisation depth

Mitigation: AL and X++ estates accumulate over years. Discovery explicitly inventories every customisation via the platform's admin tools; no surprises after that. F&O customisation rebuild is the longest sub-project for F&O migrations and budgeted explicitly.
Risk: Multi-legal-entity reconciliation (F&O)

Mitigation: F&O multi-legal-entity balance reconciliation is complex. We sandbox-test the full close cycle 2–3 times before cutover. Reconciliation discrepancies under USD 100 written off; anything higher investigated. Auditor sign-off required before cutover.
Risk: Microsoft contract renewal overlap

Mitigation: Microsoft commercial contracts have specific notice periods. Discovery includes a contract audit; we plan migration timing to land cutover before renewal so you don't pay for a year of Dynamics you won't use.
Risk: Power Platform integration continuity

Mitigation: Customers using Power Automate / Power Apps heavily for workflows audited during discovery. Each flow either migrates to Odoo's automated actions, to an external automation tool (Make.com, Zapier, n8n), or to a custom Odoo solution. Decision per flow.
Risk: F&O industry modules (Retail, Project, etc.)

Mitigation: F&O's industry-specific modules (Retail with POS, Project Operations, Field Service, etc.) audited during discovery. Most have direct Odoo equivalents; some require dedicated configuration time.
Risk: Power BI dashboards dependent on Dynamics

Mitigation: Power BI reports built on Dynamics datasets either continue (Odoo data feeds the same Power BI via a Power BI connector) or rebuild as Odoo native dashboards. Decision per report; usually we recommend the latter to reduce stack count.
Risk: Microsoft Entra ID / Azure AD authentication

Mitigation: Customers using Azure AD / Entra for SSO to Dynamics typically want the same for Odoo. Odoo supports SAML and OAuth — we configure Entra ID as the IdP during migration so users keep their existing single sign-on.
Risk: NAV / GP / AX out-of-support migrations

Mitigation: Older Dynamics versions still in production work but increasingly hard to extract from cleanly. Discovery includes a data extraction test before contract signing. Migrations from NAV 2009, AX 2009, GP 2010 have all been done; older versions case-by-case.

Who should migrate

Mid-market businesses (50–500 users) on Dynamics 365 Business Central, Dynamics 365 Finance & Operations, or legacy NAV / AX / GP. Particularly: BC customers facing renewal pressure; F&O customers in the lower-mid range (under 500 users) where the F&O premium isn't justified by functional usage; NAV / GP customers facing end-of-life pressure who don't want to re-implement onto BC at full cost; multi-entity Dynamics groups where per-app licensing compounds badly. Not a fit: enterprises (1,000+ users with deep F&O industry vertical usage) where Microsoft's ecosystem is operationally load-bearing.

Frequently asked questions

Which Dynamics products can you migrate from?

Dynamics 365 Business Central (cloud + on-prem), Dynamics 365 Finance & Operations, legacy Dynamics NAV (2009 onwards), Dynamics AX (2009 / 2012), Dynamics GP (2010 onwards). Each has its own migration approach; the underlying methodology is the same.
Will Odoo replace what we get from the Microsoft ecosystem integration?

Honest answer: not 1:1. Dynamics's tight integration with Microsoft 365, Power Platform, Power BI, Azure AD is a real feature. Odoo integrates with all of these but as a peer system, not native. For businesses where the Microsoft integration is load-bearing operationally, this is a real consideration. For most mid-market businesses, the integration value doesn't justify the per-app premium.
How does the migration handle Dynamics dimensions / financial dimensions?

Dimensions map to Odoo's analytic accounting, which is functionally equivalent but more flexible (more dimensions, hierarchy support, dynamic creation). Existing dimension values and hierarchies migrate; we usually expand the dimension model in Odoo because the Dynamics 8-dimension limit doesn't apply.
What about Business Central extensions from AppSource?

AppSource extensions (third-party BC apps) don't port. Each extension audited during discovery — most have direct Odoo Marketplace equivalents or native Odoo features. Where an AppSource extension is genuinely irreplaceable for an industry-specific need, we either build a custom Odoo equivalent or keep BC for that specific entity. Rare case.
Can you migrate from F&O without a partner-led re-implementation?

Yes — that's the whole point. F&O customers commonly face 'you'll need a 12-month partner re-implementation to upgrade' messaging. Our F&O → Odoo migration takes 20–28 weeks at fixed price, with comparable functional coverage for sub-500-user businesses. We've done it.
What about Dynamics CRM (Customer Engagement)?

Dynamics CRM data migrates to Odoo CRM during the project — leads, opportunities, accounts, contacts, activities, customisations. Most ex-Dynamics CRM customers find Odoo CRM sufficient for sales pipeline and account management; complex enterprise sales motions sometimes warrant keeping Salesforce or HubSpot synced with Odoo.
Will my Power BI reports continue to work?

Two paths: (1) repoint Power BI to Odoo's data via the Power BI connector — works for most reports; (2) rebuild reports as Odoo native dashboards — typically faster, simpler, no separate BI tool to maintain. Most customers pick (2) and reduce stack count.
How do AL extensions compare to Odoo customisations on maintenance cost?

AL extensions on BC are partner-built and maintained against BC's release cycle (every 6 months). Odoo customisations on Enterprise are Python and maintained against Odoo's release cycle (annual). Both require ongoing maintenance; Odoo customisations are typically cheaper per hour and have a broader partner pool, so total maintenance cost over 3 years is meaningfully lower.
Does Odoo support SOX compliance like Dynamics F&O does?

Odoo's audit trail, segregation of duties enforcement, and approval framework are sufficient for SOX in most mid-market scopes. F&O's enterprise-tier features (deeper SoD, complex internal controls testing) exceed Odoo. For SOX-listed companies with deep internal-controls requirements, this is a real consideration — assess during discovery.
Can we keep Azure AD / Microsoft Entra for SSO into Odoo?

Yes. Odoo supports SAML and OAuth 2.0 / OIDC. We configure Entra ID as the IdP during migration so users keep their existing SSO into Odoo with no separate password.
What about end-of-support pressure on NAV / GP / AX?

Dynamics NAV mainstream support ended in 2018 (extended support 2028). Dynamics GP mainstream support ends 2028. Dynamics AX is similar. Microsoft pushes upgrade to BC or F&O. Many mid-market businesses find migrating to Odoo cheaper than the prescribed BC / F&O upgrade — and Odoo's release cycle remains supported indefinitely.
What's the first step?

A 45-minute call. Bring: Dynamics variant (BC / F&O / NAV / AX / GP), version, user count, legal entity count, top 3 modules, and rough AL or X++ estate size. We'll tell you whether discovery is worth scheduling and what the realistic project size looks like.

Why businesses migrate from Microsoft Dynamics 365 to Odoo

What survives the migration

Our phased approach

Discovery 1–2 weeks

Sandbox migration

Odoo configuration in parallel

User training

Cutover weekend

Parallel-run period

Stabilisation

Typical timeline

Indicative cost

Risks and mitigations

Who should migrate

Frequently asked questions

Ready to scope your Microsoft Dynamics 365 → Odoo migration?