Scope note, up front: del.ai migrates NetSuite to Odoo today. Dynamics 365 Business Central is not a migration we sell. This is analysis of what the move would involve and what it would cost you to keep standing still, written because the question keeps coming up. It is not an offer, and no figure here is a quote. Every dollar amount below is either Microsoft's own published list price, with a link, or explicitly flagged as something Microsoft does not publish.
A dynamics 365 business central to odoo migration is less common than a NetSuite move. It is becoming less rare. Microsoft licensing costs compound at renewal, Power Apps dependencies accumulate, and the Azure allocation that looked manageable two years ago is a real line on the P&L today. Add a board AI mandate that requires agents operating outside M365 schema, and the structural case for re-evaluating Business Central starts to form. This is not an argument that D365 BC is a bad product. It is a functional ERP with genuine strengths. This article is for CFOs who want to see the full cost stack clearly, understand what a migration would actually involve operationally, and know when it is the wrong decision.
The reason this is worth an afternoon: the ERP line most CFOs can recite is the licence, and the licence is the only layer Microsoft publishes. Power Apps and Power Automate add-ons, the Azure allocation, and the partner retainer are three separate bills that nobody totals against the ERP budget until something forces it. (For the MRP-ownership case specific to manufacturers, see Open Source ERP for Manufacturing: Who Owns Your MRP Logic?.)
Three structural triggers show up consistently when CFOs look at Dynamics 365 Business Central alternatives: Microsoft licensing that compounds at renewal, board AI mandates that run into the M365 schema boundary, and a total cost split across bills that nobody adds together. Microsoft's published list price for Business Central is $80 per user per month for Essentials and $110 for Premium, with Team Members at $8, all quoted annually. Power Apps Premium lists at $20 per user per month. Those are the layers you can look up. The Azure allocation attributable to Business Central and the Microsoft partner retainer are not published by anyone, are specific to your tenant and your contract, and are exactly where the surprises live. None of the three triggers is a product-quality complaint. All three are questions about what the full stack costs against what the company gets, and the first step is arithmetic on your own invoices rather than a benchmark from an article.
Source: Microsoft, "Dynamics 365 Business Central pricing," 2026. ↗ | Microsoft, "Power Apps pricing," 2026. ↗
They are also the reasons CFOs searching for dynamics 365 bc alternatives end up in the same place: looking at the full Microsoft bill, not just the license line.
Microsoft licensing costs compound at renewal. D365 BC Essentials lists at $80 per user per month and Premium at $110, both paid yearly — Microsoft publishes these openly, and Essentials rose from $70 in the November 2025 increase. That figure is visible. The Power Apps and Power Automate add-ons that accumulated over three years are also visible, once you find them in the Microsoft billing portal. What is not visible anywhere is how far the combined bill has drifted from what your finance team thinks ERP costs — that number does not exist until you build it. The per-user cost is the tip of the stack.
Board AI mandates are creating schema tension. In 2026, most mid-market boards have said something about AI. The implementations that stall are almost always substrate problems. The model is not the constraint. Data access is. D365 BC operates within the Microsoft schema boundary. Agents that need to read and write across AR, AP, inventory, CRM, and project accounting simultaneously run into API surface limits that the M365 boundary defines. An open-schema platform removes that ceiling.
The cost is inside the Microsoft bill, not a clean line item. This is the practical problem. Most companies do not know their D365 BC all-in cost because it does not appear as a single line on the P&L. It is disaggregated across Microsoft license, Azure, Power Apps, and partner invoices. Before any decision is made, those lines have to be isolated and totaled.
To be direct: BC is a functional product. These are structural economics questions, not product quality criticisms. The question is whether you are getting ERP value commensurate with what you are paying for the full stack.
The phrase "business central too expensive" often comes up 12 to 18 months after initial deployment. Not because the license price changed dramatically. Because the adjacent layers accumulated without anyone tracking them against the ERP budget.
The ERP cost is usually inside a single "Microsoft" line on the P&L. That line contains several different decisions bundled together.
Power Apps and Power Automate. Power Apps Premium lists at $20 per user per month; Power Automate is licensed separately again. These start as reasonable extensions — approval workflows, invoice routing, data transformation between BC and external systems — and become operationally embedded. Your cost here is seats multiplied by rate, which you can compute exactly. What you cannot look up is how many flows you are running: by the time a CFO is looking at a migration there are often dozens, and somebody has to inventory them before any transition can be scoped.
Azure infrastructure. D365 BC runs on Azure SQL. That infrastructure cost appears on the Azure bill, not the ERP line. Some of it is ERP-specific and some is shared with other Microsoft workloads, and no published figure can tell you the split for your tenant. Isolating the ERP-attributable portion is work most companies have not done, and it is the single most useful hour in this exercise.
Microsoft partner retainer. Every customization your partner built, every workflow, every integration generates configuration complexity that lives in their systems, and retainers tend to grow as the BC instance matures. Partner retainers are privately negotiated and nobody publishes them — including us. Take yours from your own contract.
Here is the honest distinction: if Microsoft is already core infrastructure across your organization (Teams, M365, Azure DevOps, SharePoint) the marginal ERP cost is genuinely lower. Some of those Azure and Power Apps costs exist regardless of your ERP choice. The real question is whether you are getting full ERP value from the bundle, or paying for BC on top of a Microsoft infrastructure spend you would carry either way.
Isolating that number is the first step. The analysis only gets meaningful once you can see the ERP-specific cost clearly.
Here is the worksheet. Two rows you can fill from a public page, three you can only fill from your own bills.
| Cost Layer | Where the number comes from |
|---|---|
| Licence, Essentials | Published: $80/user/month, paid yearly |
| Licence, Premium | Published: $110/user/month, paid yearly |
| Licence, Team Members | Published: $8/user/month, paid yearly |
| Power Apps Premium | Published: $20/user/month — multiply by seats actually assigned |
| Power Automate | Licensed separately; check what is assigned in your tenant |
| Microsoft partner support | Your retainer contract. Not published by anyone |
| Azure infrastructure | Your Azure bill, ERP-attributable portion only. Not published by anyone |
At 50 Essentials seats the licence line alone is $48,000 a year at list. That is the number most CFOs can recite. The three unpublished layers underneath it are the reason the recited number and the real number diverge — and the honest answer to "how far do they diverge?" is that it depends on your tenant, and anyone who quotes you a benchmark range has made it up.
The true annual cost of Dynamics 365 Business Central has a published part and an unpublished part, and only the published part can be quoted. Microsoft lists Business Central Essentials at $80 per user per month, Premium at $110, and Team Members at $8, all paid yearly, following the price increase effective November 2025. Power Apps Premium lists at $20 per user per month. At 50 Essentials seats that is $48,000 a year in licence at list price. Three further layers sit underneath and none of them is published: the Microsoft partner support retainer, which is privately negotiated; the ERP-attributable share of the Azure bill, which is specific to your tenant; and whatever Power Automate and add-on entitlements have accumulated in your billing portal. Those three are where the gap between the recited ERP number and the real one lives, and the only reliable way to size them is to total your own invoices rather than trust a published benchmark range.
Source: Microsoft, "Dynamics 365 Business Central pricing," 2026. ↗ | Microsoft, "New Microsoft Dynamics 365 Business Central pricing effective November 2025," 2025. ↗
User licensing list prices come from Microsoft's Business Central pricing page. Power Apps pricing comes from Microsoft's Power Platform pricing page. Partner retainer and Azure allocation have no published source and are deliberately left blank above.
For a side-by-side view of how that total compares against NetSuite, Odoo, and SAP B1 across all five cost layers, see Mid-Market ERP Cost Comparison 2026.
A business central odoo migration on a parallel-run model runs 90 days. The structure is condition-based, not calendar-based. Odoo does not become the system of record until the numbers reconcile against D365 BC output. Here is how the phases work.
del.ai does not sell Business Central migrations; this is analysis, not an offer. A Dynamics 365 Business Central to Odoo migration would be scoped at 90 days on a parallel-run model. The structure is condition-based, not calendar-based. Weeks 1–2 cover discovery and data mapping, including a mandatory Power Apps and Power Automate flow inventory — every active flow must be documented before scope is finalized. Missing this step causes change orders post-contract. Weeks 3–8 run D365 BC and Odoo simultaneously; D365 BC remains the system of record throughout. Cutover does not happen on a date: it happens when the reconciliation gate passes. Reconciliation means line-by-line comparison of journal entries, AR aging, AP aging, and inventory positions between both systems — not a visual review. Weeks 9–12 complete cutover once written sign-off is received. Written sign-off records the comparison period, the specific financial outputs reviewed, and the individuals who confirmed the match. D365 BC credentials remain live through the full parallel run.
Source: del.ai migration methodology, 2026 — generalized from del.ai's NetSuite-to-Odoo methodology, which is the only migration del.ai offers | Microsoft, "Service overview for Business Central online," Business Central documentation, 2026, on Business Central's Azure SQL Database backend. ↗ | Microsoft, "Power Automate Integration Overview," Business Central documentation, 2026, on the native Power Automate/Power Apps connector this migration's flow inventory step accounts for. ↗
This phase produces one output: a signed scope document that anchors the fixed price.
Discovery for a BC migration has a specific requirement that does not apply to NetSuite migrations: Power Apps and Power Automate flow inventory. Every active flow needs to be documented before migration is scoped. Vendors who skip this step will find the flows post-contract, which means they surface as change orders. The inventory happens in weeks 1–2, before anything is priced.
The Azure SQL schema mapping is the technical extraction plan. D365 BC uses Azure SQL as its backend. This makes data extraction cleaner than HANA-based sources like SAP. It is technically similar to SQL Server SAP B1 migrations. The schema is readable, the data is portable, and the extraction does not require proprietary tooling.
The Odoo instance is built against the signed scope document. D365 BC stays live. Both systems process the same transactions simultaneously.
Reconciliation runs weekly. Each weekly comparison is a gate. If the gate fails, the build does not advance. D365 BC remains the system of record throughout this phase. There is no moment where you are committed to Odoo before verification is complete.
The parallel run length is four to eight weeks depending on transaction volume and how quickly reconciliation clears. Month-end periods extend the run because that is when systematic errors surface.
Cutover requires written reconciliation sign-off. The sign-off document records the comparison period, the outputs compared, and the confirmation that both systems match. That document is the authorization for cutover. Numbers must reconcile before cutover proceeds. The calendar date does not override that condition.
After cutover, D365 BC credentials remain available through the stabilization window. The license is not cancelled until go-live is confirmed stable. Issues that surface post-cutover and relate to the migrated configuration are in scope. New requirements are change orders.
The parallel run methodology here is the same approach used in NetSuite migrations. For a detailed breakdown of how parallel reconciliation works, see NetSuite to Odoo Migration: Timeline, Risk, and What CFOs Need to Know.
Insist that migration is fixed-price against a signed discovery document, that the vendor absorbs overruns inside that scope, and that change orders require written approval before work starts. That is the structure del.ai uses on NetSuite migrations, and it is the structure to demand from whoever you engage for this one.
Baseline: 50-user company, single legal entity, US operations. Both sides of this comparison have a published half and an unpublished half, so what follows is a worksheet rather than a total.
| Published rate | Not published | |
|---|---|---|
| Dynamics 365 BC | $80/user/month Essentials, $110 Premium; Power Apps Premium $20/user/month | Partner retainer, Azure allocation, escalation at renewal |
| Odoo | $38.90/user/month Standard, $76.20 Custom | Implementation, quoted by the partner you engage |
You compare Dynamics 365 Business Central and Odoo over five years by building each side from published rates and then adding the layers only your own invoices can supply. Microsoft lists Business Central at $80 per user per month for Essentials and $110 for Premium, with Power Apps Premium at $20 per user per month. Odoo lists $38.90 per user per month on its Standard plan and $76.20 on Custom. Those four numbers you can check in a browser. On the Microsoft side you must then add your partner retainer and the ERP-attributable share of your Azure bill, neither of which Microsoft publishes; on the Odoo side you must add implementation, quoted by whichever partner you engage. Any five-year total published without those inputs — including totals that appeared in earlier versions of this article — is an estimate wearing the costume of a calculation, and a CFO should treat it accordingly.
Source: Microsoft, "Dynamics 365 Business Central pricing," 2026. ↗ | Odoo S.A., "Pricing," 2026. ↗
Whatever gap your own worksheet produces, it sits on top of a second question the arithmetic does not capture: what the closed Microsoft schema costs an AI roadmap.
The board AI mandate adds that second dimension. A migrate dynamics 365 to odoo decision, where the numbers support it, does not add a budget line — it replaces existing spend with an open-schema platform where cross-system agents can operate without the BC schema ceiling. The AI capacity is not an add-on. It comes from removing the closed-platform constraint.
del.ai does not price Dynamics 365 Business Central migrations, because del.ai does not sell them. For the methodology behind building your own layered model, see Mid-Market ERP Cost Comparison 2026.
These are hard disqualifiers. Not risks to manage. Reasons to stop the conversation early.
Power BI is deeply embedded in FP&A reporting. Odoo's native BI does not replicate Power BI. Rebuilding your financial dashboards, variance reports, and board packages is a parallel project, not a migration task. If Power BI is how your FP&A team does their job, this migration is probably wrong for you. The savings math does not change that.
Teams is the operational approval layer. Purchase order approvals, expense workflows, and invoice routing that run through Teams are genuinely integrated in D365 BC. Moving to Odoo means rebuilding those flows in a different system and retraining the people who use them daily. The retraining cost is non-trivial and often underestimated.
Azure DevOps is tightly coupled to BC project accounting. If project budgets, change orders, and cost tracking flow between Azure DevOps and BC in both directions, that integration needs to be scoped carefully before any migration is authorized. This is a complexity flag, not an absolute block, but it extends timeline and cost significantly.
Active M&A is in process on the Microsoft stack. Do not swap the system of record while a deal is in diligence. Your financial data is under scrutiny. This is not the time to introduce migration risk.
Multi-entity with complex intercompany eliminations. Evaluate Odoo Enterprise multi-company features carefully before committing. Odoo handles simpler multi-entity structures. Complex intercompany eliminations, per-jurisdiction statutory compliance, and transfer pricing across multiple legal entities require honest functional gap analysis before any contract is signed.
These are the questions a CFO should have clear answers to before any vendor conversation gets serious.
What is your actual Microsoft stack dependency? List it: Azure, Teams used for operational workflows, Power BI in FP&A, M365 productivity broadly. Then separate ERP-specific from infrastructure-that-stays-regardless. The marginal ERP cost is different from the total Microsoft spend.
What does your D365 BC full cost total when you isolate every layer? License plus Power Apps plus Azure allocation plus partner retainer. Most CFOs have never seen this as a single number. Build it before any comparison is meaningful.
What does your AI roadmap require? If cross-system agents are part of the mandate, do D365 BC's schema surfaces support that cleanly? Ask your Microsoft partner directly what the API surface covers and what it does not. The answer matters for any AI roadmap that extends beyond M365.
What is your renewal timing? Inside 12 months with growing Power Apps usage: the timing is right to evaluate. More than 18 months out: the urgency math changes. Do not accelerate a migration decision if the renewal pressure is not real yet.
What does a pre-commitment functional gap review cost? A few days of BC workflow review against Odoo modules. This is the lowest-risk first step before anything is signed. If a vendor will not do a structured gap review before contract, that is information about how they operate.
Apply these in any vendor conversation, not just del.ai.
A vendor who cannot answer the rollback and reconciliation questions specifically is operating under conditions that produce the migration horror stories. Vague answers on those two points mean the risk transfers to you.
This analysis is for mid-market companies on D365 BC where the full stack — licence, Power Apps, partner support, and Azure combined — has drifted well past what finance believes ERP costs. Whether it has, and by how much, is a worksheet only you can complete. If the gap turns out to be small, the one-time migration cost will not return enough to justify the disruption, and that is a legitimate answer.
And to restate the scope note: del.ai migrates NetSuite to Odoo. Dynamics 365 Business Central migrations are not a service we offer, so there is no call to book at the end of this article for a BC move. Take the worksheet to a Business Central partner or an Odoo partner and make them fill it in.
If you are on NetSuite, that conversation we do have.
Sources
1. Microsoft, "Dynamics 365 Business Central pricing," 2026. ↗
2. Microsoft, "New Microsoft Dynamics 365 Business Central pricing effective November 2025," 2025. ↗
3. Microsoft, "Power Apps pricing," 2026. ↗
4. Odoo S.A., "Pricing," 2026. ↗
5. del.ai migration methodology, 2026 — parallel-run structure, generalized from NetSuite-to-Odoo work