# Business Central Upgrade Path: From NAV and Older BC Versions to Current > Source: https://netray.co/erp-help/business-central-upgrade-path-nav-to-business-central-versions > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System dynamics ## Erp Microsoft Dynamics 365 Business Central ## Module Upgrade paths / data upgrade ## Query business central upgrade path ## Alternate Queries - business central version upgrade - business central upgrade matrix - data upgrade to business central - upgrade dynamics nav to business central ## Applies To Dynamics NAV and Business Central on-premises. Exact supported source versions change by release, confirm in Microsoft's upgrade documentation. ## Steps ### Plan the upgrade path **Items:** - Identify your current product and exact version and build (for example NAV 2018 or an older BC release). - Look up the supported upgrade path for that version in Microsoft's upgrade documentation, and note any required intermediate version. - Decide the destination: on-premises current version, or SaaS through cloud migration. - Inventory customizations. C/AL customizations must be converted to AL extensions (or retired) before moving beyond the C/AL based versions. - Plan the data upgrade: restore a database copy, run the application conversion, synchronize, then run upgrade codeunits for each app. - Rehearse on a copy, validate balances against the source (trial balance, inventory valuation, open ledger entries), and time the run. - Cut over with a freeze window, final delta migration or upgrade, then user acceptance testing. ## Sections ### From NAV: through Business Central 14 **Body:** 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 **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### Can I upgrade directly from Dynamics NAV to the latest Business Central? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms business central upgrade path, business central version upgrade, business central upgrade matrix, data upgrade to business central, nav to business central upgrade, business central 14 upgrade, cloud migration business central, C/AL to AL conversion --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json