Microsoft Dynamics 365 Business Central Edition
Insights, updates, and practical guides for Microsoft Dynamics 365 Business Central
On-Prem vs. SaaS Business Central: Why The Earlier You Move, The More You Save (2026)
- July 6, 2026
- 3:48 pm
Every Dynamics NAV 2018 environment we audit in 2026 carries the same three hidden costs: a SQL Server license nobody has re-negotiated since 2019, a C/AL customization backlog no current developer will touch, and an ISV add-on whose vendor has already shipped their AL replacement. That is the real starting point of the on-premises vs. SaaS Business Central conversation. Not licensing math, not feature parity, but the compounding tax you pay every quarter you delay. If your finance team is still exporting to Excel to reconcile intercompany, the migration decision was made two years ago. You just have not signed the SOW yet.
Table Of Contents
- Quick Answer
- What On-Premises Dynamics NAV Actually Is In 2026
- Why On-Premises NAV Is Outdated In 2026
- What SaaS Business Central Is
- On-Premises NAV vs. SaaS Business Central Feature Matrix
- The True 3-Year Cost Of Staying On NAV
- Pros and Cons—The Honest Breakdown
- Why Earlier Migration Is Cheaper And Cleaner
- What A Real NAV To SaaS BC Migration Looks Like
- Common Objections We Hear From NAV Holdouts
- Key Takeaways
- FAQs
Quick Answer
• On-Premises Dynamics NAV is a frozen platform. Microsoft ended mainstream support for NAV 2018 in January 2023, and extended support ends in January 2028. Every version before it is already out.
• SaaS Business Central is the same product line, rebuilt for the cloud, receiving two feature waves per year, native Copilot, and Power Platform integration.
• The on-premises vs. SaaS Business Central math almost always favors SaaS by year two, once you count SQL licensing, server refresh, downtime, and developer scarcity.
• The longer you wait, the worse the migration gets. Data volume grows, C/AL debt compounds, and qualified NAV partners retire faster than they are replaced.
• On-premise Business Central still exists, but it is a stopgap, not a strategy.
• Canadian firms have added weight: Quebec Law 25 and PIPEDA obligations are easier to defend on Azure Canada Central than on a self-hosted rack.
What On-Premises Dynamics NAV Actually Is In 2026
On-premises Dynamics NAV is Microsoft’s legacy mid-market ERP, versions 2009 through 2018, installed on your own Windows Server and SQL Server, customized in C/AL, and maintained by your IT team or partner. It is the direct ancestor of Business Central, but it stopped receiving new features when Microsoft rebranded the product line in 2018.
Dynamics NAV is Microsoft’s on-premise mid-market ERP, sold from 2001 to 2018 across versions 2009 R2, 2013, 2015, 2016, 2017, and 2018. It runs on a Windows Server backend with a SQL Server database, is customized in the C/AL language via the Classic or RoleTailored client, and shares its data model with modern Business Central.
If you are still on NAV in 2026, you are almost certainly on 2016, 2017, or 2018. Anything older is out of extended support entirely. Your object customizations sit in fobs and text files. Your reports are RDLC or Classic. Your integrations are probably SOAP web services or direct SQL views. That entire stack is a product Microsoft stopped investing in seven years ago.
At Omni Logic Solutions, we have walked clients through NAV footprints where the last cumulative update was applied in 2021 because the ISV add-on could not be reconciled with the new objects. That is the state of most on-premises NAV in Canada today: functional, paid-for, and quietly rotting.
Why On-Premises NAV Is Outdated In 2026
NAV is a frozen codebase running on a frozen runtime, and the ecosystem around it has moved on. There will be no new features, no Copilot, and no AL parity retrofit, and the pool of C/AL developers shrinks every year. It is not that NAV stopped working. It stopped mattering to Microsoft’s roadmap.
Five specific pressures make 2026 the wrong year to still be on-premises:
- Support timeline. NAV 2018 extended support ends January 2028, per Microsoft Lifecycle Policy documentation. Every earlier version is already out. No security patches once you fall off.
- Developer scarcity. C/AL is not taught anywhere. Junior developers train in AL. The senior C/AL bench in Canada are retiring, and their rates have doubled since 2022.
- ISV abandonment. Most credible NAV add-ons, including warehouse, EDI, and Canadian payroll bridges, have shipped their AL replacements and are sunsetting C/AL versions.
- No AI layer. Copilot, Sales Copilot, and the Business Central AI features do not exist for on-premises NAV and never will.
- Security debt. Self-hosted SQL and Windows Server carry a patching, backup, and disaster recovery load that most mid-market IT teams underfund.
“NAV did not die. It was quietly abandoned. There is a difference, and only one of them shows up on your risk register.”
What SaaS Business Central Is
SaaS Business Central is Microsoft’s cloud-hosted mid-market ERP, delivered from Azure, updated on a fixed twice-yearly wave cycle, and licensed per user per month in CAD. It is the same product family as NAV, rebuilt on the AL language, extension model, and modern web client, with Copilot, Power Platform, and Dataverse native to the stack.
SaaS Business Central is the fully Microsoft-hosted version of Dynamics 365 Business Central, running in an Azure region (Canada Central or Canada East for Canadian tenants), updated automatically twice per year, extended via AL apps from AppSource, and licensed as a Microsoft 365-style subscription with Essentials or Premium user SKUs.
The practical difference: you do not run the servers, you do not apply the CUs, and you do not choose when features arrive. You get Copilot bank reconciliation, Copilot sales line suggestions, Power Automate flows, embedded Power BI, Teams integration, and continuous compliance updates as part of the subscription. Your job shrinks to configuration, extension apps, and process design.
Across the 40+ Canadian deployments Omni Logic Solutions has shipped, the SaaS teams spend roughly 60 percent less time on ERP infrastructure work in year one compared to their previous on-premises NAV routine.
On-Premises NAV vs. SaaS Business Central Feature Matrix
Pattern from the field: the comparison below is the one most partners will not put on a slide because it makes the “let us just keep upgrading NAV” argument fall apart. This is the honest on-premises vs. SaaS Business Central view we walk every client through.
|
Capability |
On-Premises Dynamics NAV |
SaaS Business Central |
|
Update Cadence |
Manual CUs, often skipped |
Two automatic waves per year |
|
AI And Copilot |
None, ever |
Native Copilot, Sales Copilot |
|
Licensing Model |
Perpetual + BREP maintenance |
Per user per month in CAD |
|
3-Year TCO (50 users) |
CAD 234,000 to 454,000 |
CAD 260,000 to 330,000 |
|
Security Patching |
Your team, your risk |
Microsoft-managed, SLA-backed |
|
Mobility |
Limited, VPN-gated |
Full browser, mobile, Teams |
|
Power Platform Integration |
Limited connector |
Native Dataverse virtual tables |
|
Integration Surface |
SOAP, direct SQL views |
REST, OData, Business Events |
|
Compliance Posture |
You certify Law 25, PIPEDA |
Azure Canada compliance inherited |
|
Developer Talent Pool |
C/AL, shrinking every year |
AL, growing, taught in current curricula |
The One Row That Ends The Debate
The True 3-Year Cost Of Staying On NAV
Across the engagements where we have run this math for a 50-user Canadian mid-market firm, staying on on-premises NAV over three years typically costs 20 to 40 percent more than moving to SaaS Business Central, once you count infrastructure, BREP, downtime, and the developer premium. Most CFOs miss this because the NAV cost is spread across five budget lines that never appear on the same page.
The table below is a defensible range for a 50-user Canadian distributor running NAV 2018 with one moderate ISV add-on. All figures in CAD.
|
Cost Line (3-Year, 50 Users) |
Stay On On-Premises NAV |
Move To SaaS Business Central |
|
BC SaaS Subscription |
N/A |
CAD 180,000 (Premium) |
|
SQL Server Licensing |
CAD 45,000 to 80,000 |
Included |
|
Windows Server + Hardware Refresh |
CAD 25,000 to 60,000 |
Included |
|
BREP And Enhancement Fees |
CAD 54,000 |
N/A |
|
Downtime And Lost Productivity |
CAD 40,000 to 120,000 |
Minimal |
|
C/AL Developer Premium |
CAD 40,000 to 90,000 |
N/A (AL market rates) |
|
Migration Project (one-time) |
N/A |
CAD 80,000 to 150,000 |
|
Indicative 3-Year Total |
CAD 234,000 to 454,000 |
CAD 260,000 to 330,000 |
“The NAV cost line CFOs miss is not the servers. It is the year-two developer invoice for a C/AL fix nobody wants to quote.”
Pros and Cons—The Honest Breakdown
Stay On-Premises with NAV If:
- Your industry has a hard data-residency clause that Azure Canada Central does not satisfy (rare; verify with counsel).
- You have deep C/AL customizations that generate direct competitive advantage and a captive developer bench to maintain them.
- You are inside 18 months of a planned business sale, and the buyer has said, in writing, they want the NAV asset as-is.
- Your internet reliability at core sites is genuinely below 99 percent uptime with no fixed-wireless or Starlink fallback.
Move To SaaS Business Central If:
- You are on NAV 2016, 2017, or 2018 and have not applied a CU in the last 12 months.
- Your finance team exports to Excel to close the month.
- You want Copilot, Power BI, Power Automate, or Teams-embedded workflows.
- You operate in more than one province and touch GST, HST, PST, and QST.
- You have Quebec operations subject to Quebec Law 25 requirements.
- Your ISV vendor has already announced an AL replacement.
- You have lost, or are about to lose, your senior C/AL developer.
Why Earlier Migration Is Cheaper And Cleaner
The migration cost scales with data volume, customization debt, and partner availability, and all three get worse every quarter you wait. A NAV 2018 environment migrated in 2026 is a materially cheaper project than the same environment migrated in 2028.
Three compounding factors:
- Data volume compounds. Every quarter adds transactions, dimensions, and item ledger entries. Cutover complexity and testing hours scale directly with volume.
- Customization drift. Each patched-in fix or ISV workaround adds an object that must be triaged (keep, replace, or retire) in AL. Older debt is harder to decode.
- Partner capacity. The pool of qualified Canadian Business Central partners is finite. As NAV 2018 hits 2028 EOL, the market compresses into a scramble. Rates rise, calendars close.
For the full migration methodology, see our NAV to Business Central migration guide.
Not Sure If Your NAV Environment Is Migration-Ready?
Book a working session with Omni Logic Solutions. We will walk your version, ISV stack, and customization footprint and give you a scored, no-fluff readout.
What A Real NAV To SaaS BC Migration Looks Like
From the implementations Omni Logic Solutions has led, a mid-market NAV to SaaS Business Central migration runs 4 to 9 months end-to-end, moves through five phases, and lands with historical data accessible either in BC or in a read-only archive. It is not a re-implementation if it is scoped correctly.
-
- Readiness assessment. Version audit, object inventory, ISV mapping, integration list.
- Design and AL conversion planning. Decide to keep, replace, or retire every customization.
- Data migration build. Master data first, open transactions second, and history strategy third.
- UAT and parallel run. Two closed months in both systems.
- Cutover and hypercare. 30-day post-go-live stabilization with Copilot enablement.
Full technical detail lives inside our Business Central implementation services. Copilot enablement specifics sit inside Copilot in Dynamics 365.
Common Objections We Hear From NAV Holdouts
“We have run NAV since 2013, and it has never let us down.” We hear this line, or close to it, in almost every discovery call with a NAV holdout. The problem is that “never let us down” is a rear-view mirror measurement. Every objection we get to leaving on-premises NAV has been solved by SaaS Business Central for at least three years. The objections persist because nobody has stress-tested them recently.
- “We own our data.” You still do. BC data is exportable via API, OData, and BYODB into your own Azure Data Lake or Fabric workspace on your schedule.
- “We need offline access.” True offline ERP is a myth in 2026. What you actually need is mobile and cached reading, both native to BC.
- “Our customizations will not survive.” Most will as AL extensions. Some will not, and those are usually the ones that should not have existed.
- “SaaS is more expensive.” Only on the first line item. Once SQL, Windows, refresh cycles, and downtime are counted, the math flips by year two.
- “We will lose historical data.” History either migrates into BC or lives in a read-only archive that finance and audit can still query. Nothing is lost. It is a scoping decision, not a limitation.
Compliance posture is stronger too. Azure Canada Central inherits certifications your on-premises rack does not have. That matters for PIPEDA obligations and increasingly for provincial procurement. For a broader read on the Canadian regulatory surface, see Statistics Canada digital adoption data.
The Longer You Wait, The More The Migration Costs
Every quarter on NAV adds data, debt, and risk. Get a candid readout of your exit position from Omni Logic Solutions, a Microsoft Solutions Partner headquartered in Vancouver.
Key takeaways
- On-Premises Dynamics NAV is a frozen product with a hard 2028 support cliff for its last version. Every earlier version is already out.
- SaaS Business Central is the actively developed continuation of the same product line, with Copilot, Power Platform, and Azure compliance built in.
- In the on-premises vs. SaaS Business Central math, SaaS wins on 3-year TCO for almost every 25-plus-user Canadian firm once hidden costs are counted.
- Migration cost compounds with delay. Data volume, C/AL debt, and partner scarcity all get worse each quarter.
- On-premise Business Central exists but is a bridge, not a destination.
- The right question in 2026 is not whether to move, but whether you move in Q3 or Q4.
FAQs
Is Dynamics NAV still supported in 2026?
Partially. NAV 2018 is in extended support until January 2028, with security fixes only and no new features. NAV 2017 and earlier are fully out of support. If you are on any version before 2018, you are running unsupported software right now, a finding your next cyber-insurance renewal will flag as an unsupported-software exclusion.
Can I keep Business Central on-premises instead of SaaS?
Yes, on-premise Business Central exists and is fully supported. For most Canadian mid-market firms, it is a stopgap, not a strategy. You get the AL codebase but lose Copilot, automatic waves, and Azure-managed compliance. Omni Logic Solutions uses it only for clients with specific residency or connectivity constraints.
How much does SaaS Business Central cost vs. running NAV on-premises?
For a 50-user Canadian firm, SaaS Business Central Premium runs roughly CAD 180,000 over three years in subscription. Comparable on-premises NAV, once SQL, Windows Server, refresh, BREP, and developer premium are added, typically lands between CAD 234,000 and 454,000 over the same window.
Will my C/AL customizations survive the move to SaaS BC?
Most will be rebuilt as AL extensions. Some will not, typically the ones that duplicated standard functionality or worked around bugs Microsoft has since fixed. A proper assessment sorts every object into keep, replace, or retire before any code is written. That triage is where migration budgets are made or blown.
Is SaaS Business Central secure enough for Canadian financial data?
Yes. SaaS Business Central runs on Azure Canada Central or Canada East, inherits Microsoft’s certifications, and supports the controls needed for PIPEDA, Quebec Law 25, and provincial procurement rules. For most mid-market firms, Azure compliance is materially stronger than what a self-hosted NAV rack can defend.
How long does an On-Premises NAV to SaaS BC migration take?
Four to nine months for most mid-market firms, depending on customization depth, integration count, and data history scope. A clean NAV 2018 environment with two integrations lands closer to four months. A heavily customized NAV 2016 with five ISVs and multi-entity consolidation is closer to nine.
What happens to my historical NAV data?
Three options. Migrate it fully into BC (highest cost, cleanest experience). Migrate a rolling two-year window and keep the rest in a read-only Azure SQL archive with reporting access (most common). Or archive everything pre-cutover and start BC clean. Finance and audit sign off on the choice before the build.
-
Top Accounting Software for Canadian Small Business : Comparison Guide (2026)
The ERP & CRM Knowledge Hub Strategy, Selection & Comparison Guides For Canadian Businesses Home Choosing The Best Accounting Software for Canadian Small Business in 2026 Vishal R August 18, 2026 1:12 pm Most Canadian small businesses choose their accounting software once, early, and under pressure a founder signs up for QuickBooks or Wave in year one because the
August 18, 2026 -
Logistics vs Supply Chain Management: The D365 Difference
Logistics is a subset of supply chain management. Logistics moves and stores goods. Supply chain management plans, sources, and orchestrates the entire flow, then hands physical execution to logistics.
August 7, 2026 -
Best CRM Softwares For Canadian Businesses
The ERP & CRM Knowledge Hub Strategy, Selection & Comparison Guides For Canadian Businesses Home Ranking The Best CRM Softwares for Canadian Businesses (2026) Vishal R July 16, 2026 12:30 am Every Dynamics NAV 2018 environment we audit in 2026 carries the same three hidden costs: a SQL Server license nobody has re-negotiated since 2019,
July 16, 2026 -
Dynamics 365 Business Process Flow: Step-by-Step Guide
Microsoft Dynamics 365 Business Central Edition Insights, updates, and practical guides for Microsoft Dynamics 365 Business Central Home Dynamics 365 Business Process Flow: The Complete 2026 Guide (With Action Steps) Jeet B July 9, 2026 2:21 pm Most teams building a Dynamics 365 business process flow stop at stages and steps. That is why their
July 9, 2026 -
On-Premises NAV vs SaaS Business Central (2026) | Why Move Now
Microsoft Dynamics 365 Business Central Edition Insights, updates, and practical guides for Microsoft Dynamics 365 Business Central Home On-Prem vs. SaaS Business Central: Why The Earlier You Move, The More You Save (2026) Vishal R July 6, 2026 3:48 pm Every Dynamics NAV 2018 environment we audit in 2026 carries the same three hidden costs:
July 6, 2026 -
PowerApps Explained: Same Tool, Different Name
Microsoft Dynamics 365 Business Central Edition Insights, updates, and practical guides for Microsoft Dynamics 365 Business Central Home What Is PowerApps? Complete Guide (2026) Vishal R July 6, 2026 3:20 pm Most guides to PowerApps stop at the definition and leave you no closer to knowing whether it fits your business. This one goes the
July 6, 2026
