Microsoft Dynamics 365 Business Central Edition
Insights, updates, and practical guides for Microsoft Dynamics 365 Business Central
Dynamics NAV to Business Central Migration (2026): The Ultimate MasterGuide (From C/AL to Cloud)
- April 28, 2026
- 1:40 pm
Quick Answer : Dynamics NAV to Business Central migration takes 3–9 months and costs between $60K and $350K, depending on customization complexity.
There are three legitimate migration paths: Lift-and-Shift (C/AL to AL conversion), Re-Implementation (clean slate), or Hybrid (phased). NAV extended support officially ends January 11, 2028 and Microsoft has confirmed no further extensions.
Most mid-market migrations recover their full investment within 18–24 months through reduced infrastructure costs, eliminated BREP fees, and Copilot-driven productivity gains.
Table of Contents
- Why This Conversation Can’t Wait Anymore
- NAV vs. Business Central: The Honest Comparison
- The Real Pain Points You’re Not Saying Out Loud
- The Three Migration Paths
- The Migration Roadmap
- C/AL to AL Conversion: What Actually Breaks
- Business Central Licensing in 2026
- NAV End of Life 2028: What It Really Means
- Data Migration Realities
- What You Actually Gain
- Common Migration Mistakes
- Your 30-Day Action Checklist
- Regional Considerations: Canada & Vancouver
- FAQ
Why This Conversation Can't Wait Anymore
If you’re reading this, there’s a good chance you’re staring at a Dynamics NAV environment that has quietly become the most expensive, most fragile, and most business-critical system in your entire organization.
It runs payroll.
It runs inventory.
It runs the warehouse scanner that Linda in Receiving has been using since 2014.
And every time someone says the word “upgrade,” your stomach drops because last time you tried, the consultant disappeared, the custom objects broke, and finance threatened mutiny.
We’ve spent the last decade walking finance directors, IT managers, and solutions architects off this exact ledge. So let’s skip the marketing fluff. This is the no-fluff, deeply technical, brutally honest guide to migrating from Dynamics NAV to Microsoft Dynamics 365 Business Central in 2026 –
What it actually costs ?
What actually breaks ?
And how to do it without taking your business offline for a quarter!
Let’s address the elephant in the server room: Dynamics NAV is Dead.
Not “Evolving.” Not “Transitioning.”
DEAD!
- NAV 2018 mainstream support ended January 10, 2023.
- Extended support ends January 11, 2028 — and Microsoft has confirmed there will be no further extensions (source: Microsoft Lifecycle Policy).
- Every NAV version before 2018 (2009, 2013, 2015, 2016, 2017) is already out of all support windows.
- Microsoft Partners are no longer being trained on C/AL. The talent pool is evaporating in real time.
If you’re on NAV in 2026, you are essentially running a business on a platform that Microsoft, the partner ecosystem, and the developer community have collectively walked away from.
Every month you wait, your migration gets harder, your consultants get more expensive, and your risk profile gets uglier.
That’s the bad news. The good news? Business Central is genuinely the best mid-market ERP Microsoft has ever shipped and the migration path, while not trivial, is more mature than it has ever been.
Dynamics NAV vs Business Central: The Honest Comparison
Most blogs give you a feature-comparison table written by someone who has never opened the Development Environment. Here’s what actually matters to the people doing the work:
| Dimension | Dynamics NAV (Legacy) | Business Central (2026) |
|---|---|---|
| Development Language | C/AL (proprietary, monolithic) | AL (modern, extension-based, Git-friendly) |
| Customization Model | Direct object modification | Extensions (no base code touched) |
| Hosting | On-premise / self-hosted SQL | SaaS, Private Cloud, or On-Prem |
| Upgrade Cycle | Painful, every 3–5 years | Continuous (2 major waves/year, auto-applied) |
| UI | Windows Client / RTC | Modern web client, mobile, Outlook, Teams |
| Reporting | RDLC / Classic | Power BI native, Excel layouts, Word layouts |
| Integration | Web Services (SOAP), painful | REST APIs, Power Platform, Dataverse |
| Licensing | Perpetual + BREP | Per-user subscription (Essentials/Premium) |
| AI / Copilot | None | Native Copilot, sales/marketing/finance agents |
| Total Cost of Ownership | Hidden, ballooning | Predictable, transparent |
That last row deserves its own conversation. And if TCO is what your CFO keeps asking about, I’d strongly suggest reading our deep dive on Business Central Total Cost of Ownership before you build your business case. It will save you from the three classic ROI mistakes finance teams make when comparing on-prem to SaaS.
Real Client Snapshot: A 120-user manufacturer in Surrey, BC, replaced their NAV 2017 environment in 2025.
Pre-migration TCO : $187,000/year (BREP + SQL licenses + infrastructure + MSP).
Post-migration BC SaaS cost : $116,000/year.
Net savings: 38% — with Copilot included.
The Real Pain Points You're Not Saying Out Loud
At least three of these are keeping you up at night:
- “We have 800+ custom objects and nobody documented any of them.”
Your original NAV partner is gone. The developer who knew the costing logic retired. Half your modifications are in PROD only. - “Our last upgrade attempt failed and cost us $90K.”
You tried in 2021. You got burned. Leadership is allergic to the word “migration” now. - “We can’t afford downtime.”
You’re a manufacturer / distributor / professional services firm. Every hour offline = real revenue lost. - “We don’t know what we’ll lose.”
Reports, permissions, custom workflows, the weird invoice format the CEO insists on what survives the move? - “We’re scared of the cloud.”
Data sovereignty. Latency. “What if Microsoft goes down?” (Reality check: your on-prem server goes down more.) - “The licensing math doesn’t make sense yet.”
Per-user pricing feels like a downgrade until you actually count what you’re paying for SQL CALs, Windows Server, backups, and your MSP.
We’ll address every single one of these below. That’s A Promise!
The Three Migration Paths (And Which One You Should Actually Take)
There is no single “NAV to BC migration.” There are three legitimate paths, and choosing the wrong one is the single biggest reason migrations fail.
Path 1: Lift-and-Shift Technical Upgrade (C/AL to AL Conversion)
Microsoft provides official tooling : the Cloud Migration Tool, Code Conversion (txt2al), and Data Upgrade Codeunits — to bring your existing NAV database and customizations into Business Central as extensions.
- Best for: Heavily customized NAV environments where the customizations still deliver real business value.
- Timeline: 4–9 months.
- Risk: Medium-high. Custom code rarely converts cleanly. Expect 30–60% rewrite on complex objects.
- Cost range: $80K–$350K depending on object count and complexity.
Path 2: Re-Implementation (Clean Slate)
Stand up a brand-new Business Central tenant. Migrate master data and open transactions only. Rebuild customizations as proper AL extensions or replace them with standard BC features.
- Best for: NAV environments older than version 2017, or where customizations were band-aids for missing functionality that BC now ships natively.
- Timeline: 3–7 months.
- Risk: Low-medium. Predictable.
- Cost range: $60K–$200K.
This is the path we recommend for roughly 70% of NAV clients we assess.
Why?
Because most of your customizations are solving problems Business Central already solved out of the box and you’ve been paying to maintain redundant code for years.
Before you commit to rebuilding anything, please read our article that talks about 7 Standard Business Central Features You Are Paying For (But Probably Aren’t Using).
We have seen clients delete $200K worth of custom code in a single workshop after that conversation.
Path 3: Hybrid (Phased Migration)
Move financials first, keep NAV running for warehouse/manufacturing for 6–12 months, then migrate the rest. Connected via APIs.
- Best for: Large, complex environments where a single cutover is operationally impossible.
- Timeline: 12–18 months.
- Risk: High operational complexity, but low business risk.
- Cost range: $250K–$800K+.
Not sure which path fits your environment - Click Here To Find Out!
We'll review your NAV version, object count, and integration footprint and give you a straight answer.
NAV to Business Central Migration Roadmap & Timeline
Here’s the realistic, phase-by-phase breakdown. If a partner pitches you a 6-week migration for a customized NAV 2016 environment, run.
Phase 1 — Discovery & Assessment (Weeks 1–4)
- Object-level audit of your NAV database (typically 1,500–6,000 objects in a customized env)
- Code complexity scoring using Microsoft’s AL Code Analysis tools
- Integration inventory (every API, every CSV drop, every SQL job)
- License gap analysis (Essentials vs. Premium — manufacturing/service mgmt require Premium)
- Data volume analysis (databases over 150GB require special handling via the Cloud Migration Tool)
Deliverable: A migration blueprint document with effort estimates per object, not per “module.”
Phase 2 — Design & Decisions (Weeks 4–8)
This is where most migrations live or die.
You’re making decisions like:
- Which customizations get rebuilt, which get deleted, which get replaced by ISV apps from AppSource?
- Essentials or Premium licensing?
- SaaS, or do you genuinely need on-prem/private cloud (hint: 95% of you don’t)?
- What’s the data cutover strategy — full historical, or open transactions only?
Phase 3 — Build & Convert (Weeks 8–20)
- C/AL to AL conversion via
txt2al - Refactoring converted code into proper extensions
- Rebuilding reports (RDLC → Word/Excel layouts or Power BI)
- Rebuilding integrations as REST/OData v4
- Setting up CI/CD pipelines (yes, your ERP gets DevOps now)
Phase 4 — Data Migration & UAT (Weeks 16–24)
User Acceptance Testing is where I see the biggest 2026 game-changer: automated UAT scripts.
If you’re still doing UAT with a 200-row Excel test plan and three exhausted accountants clicking buttons for two weekends, you’re doing it wrong.
Get familiar with Page Scripting in Dynamics 365 Business Central before you start UAT — it will cut your testing cycle by 40% and catch regressions your humans will miss.
Phase 5 — Cutover & Hypercare (Weeks 24–28)
- Final data sync (typically over a long weekend)
- Go-live
- 4–6 weeks of hypercare with the implementation team on standby
- Knowledge transfer to internal team or managed services
For a much more granular week-by-week breakdown with real client examples and risk registers, our Business Central Implementation Timeline Guide For 2026 With Phases, Risks & Real Examples walks through three actual client projects — a 15-user professional services firm, a 40-user Distribution, and a 60-user multi-store organisation.
C/AL to AL Conversion: What Actually Breaks During NAV to Business Central Migration
Let’s get into the technical weeds, because this is where vague blogs fall apart.
What converts cleanly (~70% of typical custom code)
- Simple field additions to standard tables
- Custom pages that follow standard patterns
- Most report dataset logic
- Codeunit functions without heavy event subscribers
What requires manual rework
- Direct modifications to base objects (illegal in extension model — must become event subscribers or table extensions)
.NET interopcalls (deprecated — must be replaced with HTTP/JSON or Azure Functions)- File system access (sandbox doesn’t allow it — use Azure Blob Storage or streams)
COMMITchains in long-running processes (BC’s transaction model is stricter)- Custom printing logic (entirely new architecture)
- SQL passthrough queries (gone — must use APIs or AL queries)
What needs to be entirely re-architected:
- Anything using the classic Windows client UI patterns
- Background processing using NAS Services → must move to Job Queue + Azure Functions
- Heavy reporting jobs → should move to Power BI / Synapse Link for Dataverse
A Genuinely Useful Exercise :
Before migration, audit your NAV environment for manual processes that customizations were built to automate.
Half the time, BC’s standard features (approval workflows, recurring journals, document send profiles, dimension defaulting) make those customizations obsolete.
We covered exactly this in our guide on how to Reduce Manual Work in Business Central Without Customization (10 Proven Ways) — you really need to read this before you greenlight a single line of custom AL.
Business Central Licensing & Migration Cost (2026)
Business Central licensing in 2026
- Essentials: ~$70 USD/user/month — covers finance, sales, purchasing, inventory, projects, basic warehousing
- Premium: ~$100 USD/user/month — adds manufacturing and service management
- Team Members: ~$8 USD/user/month — read access + light write (timesheets, approvals, basic data entry)
- Device Licenses: available for shop floor / warehouse scanners
The math NAV customers always miss
When you’re on NAV, you’re paying for:
- BREP (annual enhancement plan): typically 16–20% of license value/year
- Windows Server licenses
- SQL Server licenses (this one hurts — Standard is ~$3,500/core)
- SQL CALs
- Backup infrastructure
- DR/HA infrastructure
- Internal IT ops time
- Your partner’s “keep the lights on” retainer
When you actually total this honestly, most 30–100 user NAV environments are paying $1,200–$2,000 per user per year in real, fully-loaded cost.
Business Central Essentials at ~$840/user/year, with Microsoft handling the infrastructure, is almost always cheaper not more expensive. The CFO conversation flips entirely once you build the model correctly.
That natural shift from infrastructure-heavy spending to predictable subscription cost is exactly why we now see CFOs leading the migration conversation, not blocking it.
January 11, 2028 isn’t just a calendar date —
It’s The Day Your NAV Environment Becomes A Compliance Liability!
What “End of Extended Support” actually triggers
- No more security patches. Any new vulnerability discovered after Jan 11, 2028 will never be patched. For SOC 2, ISO 27001, or PIPEDA-compliant organizations, this is an automatic audit failure.
- No tax/regulatory updates. Year-end payroll updates, tax form changes, e-invoicing mandates — none of it ships for NAV after EOL.
- No Microsoft support tickets. When something breaks at 2 AM during month-end close, you’re entirely on your partner.
- Cyber insurance complications. Most cyber insurance policies in 2026 already exclude unsupported software. Your premium spikes or coverage drops.
- Auditor red flags. External financial auditors increasingly flag unsupported ERP as a material control weakness.
The realistic timeline math
- A typical mid-market migration takes 6 months
- Add 3 months for partner selection + budgeting
- Add a 3-month buffer for scope creep (there’s always scope creep)
= You should be in active discovery by Q1 2027 at the latest.
If you’re starting in 2027, your partner options narrow dramatically. The good ones get fully booked.
Data Migration: The Part Everyone Underestimates
The Cloud Migration Tool in Business Central is genuinely good now (it was rough in 2020–2022). It supports:
- NAV 2015 and later directly
- NAV 2009 R2 / 2013 / 2013 R2 via intermediate upgrade
- Full table-level selection of what migrates
- Delta sync during cutover (huge improvement from earlier versions)
But here’s what the tool won’t tell you:
- Posted document history is huge — most clients only migrate 2–3 years of history and archive the rest
- Custom tables don’t migrate without corresponding AL extensions deployed first
- Dimensions get messy if your NAV setup wasn’t disciplined (this is the #1 data cleanup task)
- Item ledger entries with broken application chains will fail — fix in NAV first
- User permissions DO NOT migrate — rebuild from scratch (and honestly, you should)
You can read Microsoft’s own current guidance on the Cloud Migration Tool and the official NAV to Business Central upgrade documentation — both have been substantially updated for the 2026 wave.
What You Gain (Beyond Just "Being on Cloud")
Migration ROI conversations always focus on cost reduction. They should focus on capability gain:
- Copilot — natural language journal entries, sales line item suggestions, bank reconciliation explanations, marketing copy generation, sales email drafting. This is not vapor — it ships, it works, and finance teams are using it daily in 2026.
- Power Platform native integration — Power Automate flows trigger from BC events natively. No more middleware.
- Dataverse + Synapse Link — your BC data is queryable in Microsoft Fabric/Synapse for enterprise analytics without ETL.
- AppSource ecosystem — over 3,000 verified apps. Your NAV ISV add-on probably has a BC equivalent that’s better and cheaper.
- Mobile, Outlook, Teams embedded experiences — sales reps can post quotes from Outlook. Approvers approve from Teams. CFOs see dashboards on their phone.
- Continuous innovation — two major releases per year, automatic, tested, with version compatibility windows.
Common NAV to Business Central Migration Mistakes
Q: What’s the #1 mistake companies make in NAV to Business Central migrations?
A: Trying to replicate NAV exactly in Business Central. You’re paying to recreate the limitations you escaped. Rethink, don’t replicate.
Q: What’s the most expensive overlooked step?
A: Skipping data cleanup. Garbage in NAV becomes garbage in BC — just more expensive garbage.
Q: Where do most projects underrun their budget on testing?
A: UAT. Plan for 4–6 weeks of focused testing, not “we’ll do it on the side.”
Q: What’s the biggest partner-selection trap?
A: Choosing the cheapest partner. A NAV-to-BC migration done badly costs more than doing it twice.
Q: What kills user adoption fastest?
A: Not training users before go-live. The UI is different. Workflows are different. If your users hit the new system cold, adoption tanks.
Q: What’s the technical risk most teams forget?
A: Forgetting integrations until week 18. Inventory every integration in week 1. Every. Single. One.
Q: Should I migrate all my historical data?
A: No. You don’t need 15 years of history in BC. Archive it. Query it from a data warehouse if you ever need it.
Your 30-Day NAV Migration Action Checklist
If you take nothing else from this guide, do these in order:
- Run an object count on your NAV database. (
Objecttable — count modified vs. standard.) This single number determines 60% of your migration cost. - Inventory every integration. Every API, every file drop, every SQL job, every Excel import.
- Get a real licensing quote — not from your current partner, from at least two BC-specialized partners.
- Build a TCO model that includes the hidden costs of staying on NAV (BREP, infrastructure, risk, talent scarcity).
- Identify your 3 most painful current customizations and ask: does standard BC already do this?
- Pick a path — Lift-and-shift, Re-implementation, or Hybrid — based on honest assessment, not vendor preference.
- Set a target go-live date working backwards from your fiscal year-end (avoid go-lives in your busiest quarter).
Regional Considerations: Canada & Vancouver
For our clients across British Columbia and Western Canada, there are three local realities sharpening this timeline:
- Microsoft’s Canadian data centres (Quebec City and Toronto) mean your data stays in Canada — critical for PIPEDA compliance and increasingly for industry-specific regulations.
- The talent shortage for legacy NAV/C/AL developers in BC is acute. Local rates for NAV developers have nearly doubled since 2022. Local AL/Business Central talent is more available and more affordable.
- The Canada Digital Adoption Program (CDAP) funding window for digital transformation grants is still open for qualifying SMBs — and Business Central migrations explicitly qualify.
Whether you’re a distributor in Richmond, a manufacturer in Surrey, a professional services firm downtown, or a multi-entity group operating across Canada, the migration window is closing rapidly.
The partners with senior C/AL-to-AL conversion experience are getting fully booked into 2027.
Looking specifically for a Vancouver-based Business Central partner? - Click To Enquire
We'll review your NAV version, object count, and integration footprint and give you a straight answer.
The Bottom Line
Dynamics NAV got you here. It will not get you to where your business needs to go in the next decade.
Business Central is not just “the new NAV” —
it’s a fundamentally different, vastly more capable platform that happens to share lineage with the system you already know.
The migration is real work. It’s not free, it’s not instant, and anyone who tells you otherwise is selling you something. But done right — with a partner who actually knows both platforms, with a methodology that respects your business continuity, and with a roadmap built around your actual pain points — it is the single highest-ROI technology decision a NAV customer can make in 2026.
The question isn’t if you migrate.
It’s whether you do it on your terms, on your timeline, with a partner you trust or whether you do it in panic mode in 2027 when extended support officially ends.
FAQs
How long does a typical NAV to Business Central migration take?
Three to nine months for most mid-market environments (30–150 users), depending on customization volume and chosen migration path.
How much does a NAV to Business Central migration cost in 2026?
Between $60,000 and $350,000 for typical mid-market organizations. Re-implementations average $60K–$200K; lift-and-shift technical upgrades $80K–$350K; hybrid phased migrations $250K–$800K+.
When does Dynamics NAV support officially end?
NAV 2018 extended support ends January 11, 2028. All earlier NAV versions are already out of support.
Will I lose my customizations during migration?
No — but you’ll likely rebuild many of them as AL extensions, and you’ll discover that 30–50% of your customizations are now redundant because BC ships the functionality natively.
Can I stay on-premise with Business Central?
Yes, Business Central supports on-premise deployment, but you lose Copilot, automatic updates, and most Power Platform integrations. 95% of migrations go to SaaS.
What happens to my historical data?
You choose. Most clients migrate 2–3 fiscal years of transactional data and archive the rest in a queryable data warehouse.
Is Business Central ready for manufacturing, warehousing, and multi-entity?
Yes — these were weak points in 2018–2020 and are now mature in 2026. Premium licensing covers manufacturing and advanced warehousing natively.
Can I migrate from a very old NAV version like 2009 or 2013?
Yes, but it requires an intermediate upgrade step. Re-implementation is usually the more economical path for NAV versions older than 2015.
Does Business Central work with Power BI and Microsoft Fabric?
Yes, natively. BC data is available in Dataverse and queryable in Microsoft Fabric/Synapse with no ETL required.
Do I need to retrain my users?
Yes. Plan for 8–16 hours of role-based training per user. Adoption is the #1 predictor of migration ROI.
-
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
