Business Central Upgrade Path: From NAV and Older BC Versions to Current
business central upgrade path
Also searched as
- business central version upgrade
- business central upgrade matrix
- data upgrade to business central
- upgrade dynamics nav to business central
Short answer
From Dynamics NAV the usual path goes to Business Central 14, the C/AL bridge version, then onward to later extension-based versions. From an older Business Central version you follow the documented upgrade matrix, sometimes in steps. The right route also depends on whether you move to SaaS, where cloud migration is an alternative to an in-place upgrade.
Applies to: Dynamics NAV and Business Central on-premises. Exact supported source versions change by release, confirm in Microsoft's upgrade documentation.
Plan the upgrade path
- 1Identify your current product and exact version and build (for example NAV 2018 or an older BC release).
- 2Look up the supported upgrade path for that version in Microsoft's upgrade documentation, and note any required intermediate version.
- 3Decide the destination: on-premises current version, or SaaS through cloud migration.
- 4Inventory customizations. C/AL customizations must be converted to AL extensions (or retired) before moving beyond the C/AL based versions.
- 5Plan the data upgrade: restore a database copy, run the application conversion, synchronize, then run upgrade codeunits for each app.
- 6Rehearse on a copy, validate balances against the source (trial balance, inventory valuation, open ledger entries), and time the run.
- 7Cut over with a freeze window, final delta migration or upgrade, then user acceptance testing.
From NAV: through Business Central 14
Business Central 14 is the last C/AL based release and is the bridge from Dynamics NAV. You first bring the NAV database to BC 14 (converting the application and data), and from there move to extension-based versions in which customizations are AL extensions rather than modified base objects. Older NAV versions may need an intermediate NAV upgrade first, as the documentation lays out per version.
The bridge matters because the later versions have no C/AL. Any customization written as direct code changes must be reimplemented as extensions using events, table extensions and page extensions. That redevelopment, not the data upgrade, is usually the largest part of the project.
From older Business Central versions
For Business Central versions on the extension model, Microsoft publishes which source versions can be upgraded directly to which targets. If your version is too old for a direct hop you upgrade to an intermediate version first. Always read the matrix for your exact pair rather than assuming that the latest version is reachable in one step.
Each hop requires the apps to exist in versions compatible with both sides, because the data upgrade runs the apps' upgrade logic. Third-party apps are the common blocker, so confirm with each publisher that a compatible version exists for the path and the target.
Cloud migration instead of in-place upgrade
To move to SaaS you do not have to upgrade the on-premises database in place. Business Central has a cloud migration feature that replicates data from supported on-premises versions to an online tenant, after which you rebuild or install the needed extensions online. It suits companies that want to leave the infrastructure behind, and it lets you test the target before cutover.
The trade-off is control. Online you accept Microsoft's update schedule and the extension model limits, and any heavy external integration to the database must change to use APIs. For regulated or air-gapped environments, staying on-premises on a current version is often the real answer.
Validating the result
After each rehearsal reconcile against the source: trial balance by dimension, customer and vendor ledger totals, inventory valuation, open orders and posted entries. Count records in the major tables. Differences usually point to a skipped upgrade codeunit or a data issue in the source that the old version tolerated.
Record the exact sequence and timings so the production run is a repeat of a rehearsal, not a first attempt.
Try it here, free
NAV to Business Central Upgrade Assessment
Answer ten questions about your Dynamics NAV environment to see how ready you are to upgrade to Business Central and what to tackle first.
Common pitfalls
- !Assuming a direct jump from any old version to the latest. Check the matrix for the exact pair.
- !Underestimating the effort of converting C/AL customizations into extensions.
- !Ignoring third-party apps that have no version for your path.
- !Not reconciling balances after each rehearsal, then finding differences in production.
- !Treating cloud migration as a lift-and-shift, when extensions and integrations still need rework.
How an ERP-grounded AI assistant handles this
Legacy C/AL code is hard to read and expensive to port. A private model running on your own servers can summarize each customization, suggest the matching event or extension object, and draft AL for developers to review, which keeps proprietary code out of public services. It speeds analysis and drafting, but testing and sign-off remain human work.
Frequently asked questions
Can I upgrade directly from Dynamics NAV to the latest Business Central?
Generally not in one step. NAV goes to Business Central 14 first, the C/AL bridge version, and then to extension-based versions. Confirm the supported path for your exact NAV version in Microsoft's documentation because older versions may need an intermediate NAV upgrade.
What is the Business Central upgrade matrix?
It is Microsoft's table of which source versions can be upgraded to which target versions. Look up your current and target version there, and follow any intermediate steps listed. It changes with new releases so check the current version of the documentation.
Do I have to rewrite my NAV customizations?
Beyond Business Central 14, yes. C/AL changes to base objects have to be reimplemented as AL extensions using events and extension objects, or removed if the standard product now covers the need. Plan this as a development project.
Is cloud migration better than upgrading on-premises?
Neither is better in general. Cloud migration removes infrastructure and gets you on the update cycle, while an on-premises upgrade keeps data and control in your environment. Regulated and air-gapped sites often stay on-premises. Decide on compliance, integration and cost.
Related
Upgrade to Business Central 25: How to Update SaaS and On-Premises
Business Central version 25 is the 2024 release wave 2. For SaaS you schedule or accept the update from the Business Central admin center after testing in a sandbox. On-premises you install the new server, convert the database, then synchronize and upgrade each extension. The real work is making every extension compile and upgrade cleanly on the new version first.
How-toBusiness Central Integration Events: How to Publish and Subscribe in AL
An integration event is a procedure marked with the IntegrationEvent attribute that has an empty body. Code elsewhere subscribes to it with the EventSubscriber attribute, so extensions can change standard behavior without modifying base objects. You publish with IntegrationEvent, subscribe with EventSubscriber, and pass var parameters when the subscriber needs to alter data.
Error fixBusiness Central Error Messages: What They Mean and How Errors Are Handled
Most Business Central errors come from a few AL patterns: TestField and FieldError for missing or invalid field values, Error for rule violations, and permission or locking messages from the platform. Developers can customize them with Error and ErrorInfo, collect many errors at once, or catch them with TryFunction. If the whole service is unreachable, check service health and environment state first.
AdvancedPlanning an AX 2012 to Dynamics 365 Finance and Operations upgrade
Moving from AX 2012 to D365 F&SCM is a platform change, not a version bump: X++ customizations go through a code upgrade to the new extension/overlayering model, and data moves through a structured data migration, both coordinated as an Upgrade project in Lifecycle Services (LCS). Plan it as a project with its own testing cycle, not a routine patch.
Error fixFixing "Cannot create a record in (table). The record already exists" in D365 F&SCM data entity imports
This is the standard kernel duplicate-key exception, thrown when the Data Management Framework tries to insert a staging row into a target table whose unique or alternate key already matches an existing record. It almost always means the entity's insert-vs-update logic did not recognize the target row as an update, not that you have a true accidental duplicate in your source file.
Error fixFixing "There are currently no batch servers available for processing" in D365 F&SCM
This message means the batch framework cannot find any AOS instance flagged as a batch server and available for the batch group the job is assigned to. The fix is almost always in server configuration (System administration > Servers) or batch group assignment, not in the batch job itself.
AI for ERPAI for Dynamics NAV 2009-2018, before or instead of a Business Central migration
Add AI to Dynamics NAV 2009-2018 without a Business Central migration: ground an LLM on C/AL tables through SQL Server, on-prem or private cloud.
AI for ERPAI for Dynamics 365 Business Central, on-premises or SaaS, beyond Copilot
AI for Business Central beyond Copilot: grounded question answering over BC's data via OData and APIs, for on-premises and SaaS tenants alike.
Stuck on Microsoft Dynamics 365 Business Central?
Talk to engineers who work inside Microsoft Dynamics 365 Business Central every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- NAV to Business Central Upgrade AssessmentAnswer ten questions about your Dynamics NAV environment to see how ready you are to upgrade to Business Central and what to tackle first.
- NAV to Business Central Data Migration Mapping WorksheetTrack each NAV table you plan to migrate, the target in Business Central, the method, volume and status, and total the effort.
- Business Central Routing and Production BOM Cost WorksheetPlan routing operations with setup time, run time, lot size and work center rate, and see operation cost per unit before you set up routings in BC.
ERP fixes and how-tos
- Upgrade Business Central 14 to 27: Path, Work and Release UpdatesHow to plan a Business Central 14 to 27 upgrade: stepping stones, C/AL to AL extension work, release waves, process-only reports, Format time and MB-800.
- Adding a Private AI Layer to Business Central On-PremisesAdd AI to Business Central on-prem without cloud: API v2.0, custom API pages, SQL replica, retrieval, local LLM, BC permission sets, approved write-back.
- Calling and extending the Business Central API v2.0Business Central API v2.0 explained: the endpoint URL, Azure AD app registration and OAuth 2.0 token, calling standard entities, and custom API pages in AL.
AI on your ERP
- AI for Dynamics GP and NAV, Before the Business Central DecisionDynamics GP mainstream support is ending and NAV is long retired from active development. Add a private LLM over GP or NAV data now, on-prem, without a forced Business Central move.
- AI for Dynamics NAV 2009-2018, before or instead of a Business Central migrationAdd AI to Dynamics NAV 2009-2018 without a Business Central migration: ground an LLM on C/AL tables through SQL Server, on-prem or private cloud.
Integrations
- How to add WhatsApp to Microsoft Dynamics 365 Business CentralHow to connect WhatsApp to Dynamics 365 Business Central: API v2.0 or custom API pages, webhooks, template messages, and two-way replies that post back safely.
- How to add AI agents to Dynamics 365 Business CentralHow to add AI agents to Dynamics 365 Business Central: API v2.0 and custom API pages as the tool layer, approval gates, SaaS vs on-prem, and build options.
Software
- Microsoft Dynamics 365 Business CentralDynamics 365 Business Central explained for manufacturers: modules, APIs, AL extensions, deployment, strengths, limits and alternatives for small and mid-size firms.
- Microsoft Dynamics 365 Finance and Supply ChainDynamics 365 Finance and Supply Chain Management explained for manufacturers: modules, data entities, OData, deployment, strengths, limits and alternatives.