# Upgrade to Business Central 25: How to Update SaaS and On-Premises > Source: https://netray.co/erp-help/upgrade-to-business-central-25-how-to-update-business-central > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer 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. ## Kind how-to ## System dynamics ## Erp Microsoft Dynamics 365 Business Central ## Module Upgrade / 2024 release wave 2 (v25) ## Query upgrade to business central 25 ## Alternate Queries - how to update business central - business central 2024 release wave 2 upgrade - update business central on-premises to version 25 - business central update environment admin center ## Applies To Business Central 2024 release wave 2 (v25), online and on-premises. Confirm your exact source version against Microsoft's supported upgrade path table before starting. ## Steps ### Update to version 25 safely **Items:** Inventory everything installed: per-tenant extensions, AppSource apps and customizations. In SaaS use the Extension Management page, on-premises list apps with the administration shell. Read Microsoft's release plan and the deprecation and breaking change notes for the version, and list anything that touches your extensions. SaaS: create a sandbox copy of production in the admin center (Environments), then update the sandbox to the new version and test there. Online, you can see the available target versions and set the update window on the environment. Fix and republish extensions. Update runtime and platform/application dependencies in app.json, recompile against the new symbols, and add or fix upgrade code for any schema changes. Check partner and AppSource apps for a compatible version. An app without one blocks the upgrade or must be uninstalled first. SaaS: set the update window in the admin center and let Microsoft run it, or update on your chosen date when the version is offered. Back up first through the environment's database export or copy if policy requires it. On-premises: install the v25 server components, restore a copy of the database, run the database conversion, then synchronize and upgrade the tenant and each app. Test on a copy before production. After the update, run a defined smoke test: post a sales and purchase document, run a batch job, test integrations and reports, then check the event log and Extension Deployment Status. ## Sections ### SaaS: how the update actually works **Body:** In SaaS Microsoft owns the platform, and each environment is updated to a new major version according to a published schedule. Admins can choose an update window within the allowed period and can see in the admin center when a new version is available for a given environment. Sandboxes can usually go first, which is the point: you find extension breakage in the sandbox, not in production. If an extension fails to upgrade or a required app is incompatible, the environment can remain on the previous version until it is fixed, and Microsoft has deadlines after which an environment is updated anyway. Do not leave this to the last month. The Extension Deployment Status page and admin center notifications show which app blocks you. ### On-premises: the upgrade outline **Body:** The on-premises process is a technical upgrade: install the new server and web client, point it at a copy of the database, convert the application database, synchronize the tenant schema, then upgrade each app's data with its upgrade codeunits. System and base application packages must be published first, then your extensions in dependency order. Use the Business Central administration shell, and check the documentation for the exact cmdlet names and parameters for your source version. Plan for the SQL Server version and Windows or .NET prerequisites of the new version, as requirements move between releases. Dry-run the full sequence on a copy, time it, and write down the order. A rehearsal is the only reliable way to estimate the downtime window for a large database. **Code:** # Outline only - verify cmdlets and parameters in the docs for your versions Invoke-NAVApplicationDatabaseConversion -DatabaseServer -DatabaseName Sync-NAVTenant -ServerInstance BC250 -Mode Sync Publish-NAVApp -ServerInstance BC250 -Path .\MyApp.app -SkipVerification Sync-NAVApp -ServerInstance BC250 -Name MyApp -Version 1.2.0.0 Start-NAVAppDataUpgrade -ServerInstance BC250 -Name MyApp -Version 1.2.0.0 Get-NAVAppInfo -ServerInstance BC250 -TenantSpecificProperties ### Extensions, upgrade code and what usually breaks **Body:** Most failed updates come from extensions, not the base product. Typical causes: an event publisher the extension subscribes to changed signature or was removed, a table field was made obsolete, an API or code that was marked for removal finally went away, or the extension needs a data upgrade it does not have. Compile against the new symbols early and treat each error as a work item. Data upgrade logic lives in codeunits with Subtype = Upgrade, using OnCheckPreconditionsPerCompany, OnUpgradePerCompany and OnValidateUpgradePerCompany triggers. Use upgrade tags so the logic runs once. If you changed table schemas, make sure the extension declares the right ObsoleteState and, for destructive changes, understand when the data is lost, which depends on the schema sync mode. ### A test plan that catches real problems **Body:** Build a regression list of the processes the company cannot do without: order to cash, procure to pay, production orders, month-end close, bank reconciliation, key reports and every integration. Run it in the updated sandbox with realistic data volume and with the profiles your users actually use. Include performance. A new version can change queries, and extensions that were fine at the old version sometimes surface slow queries. Compare a few heavy operations such as posting a large batch, running MRP or a planning worksheet calculation, before and after. If you run on-premises, look at SQL wait statistics, not only user complaints. ## Pitfalls - Updating production before a sandbox of the same data has passed the full regression list. - Forgetting AppSource and partner apps. A single incompatible app can hold the whole environment back. - Assuming a direct jump is supported from any old version. Check the supported upgrade path table for your exact source version. - Skipping upgrade tags in upgrade codeunits, so migration logic runs twice or not at all. - Leaving the SaaS update to the forced deadline. A failed extension upgrade then happens under pressure. - Not recording the order of publish, sync and upgrade for on-premises, which makes the production run slower than the rehearsal. ## Ai Angle Version upgrades are mostly diffing: which events, fields and APIs your extensions use versus what the new version changed. An assistant with a private index of your AL source (hosted on your own infrastructure for on-prem customers) can list the extension objects that reference changed or obsolete symbols and draft fixes for developers to review. It does not run the upgrade, which stays a controlled human process. ## Faq ### Is Business Central 25 the same as 2024 release wave 2? **Answer:** Yes. Microsoft numbers major releases, and the October 2024 release (2024 release wave 2) is version 25. Minor updates continue between major versions in SaaS, so the exact build number shown in the client can be higher than 25.0. ### How do I update Business Central online? **Answer:** In the Business Central admin center open Environments, select the environment, and use the update options to see the available version and set the update window. Update a sandbox copy first. The platform handles the update itself, but extensions must be compatible. ### Can I upgrade on-premises Business Central directly from an old version to 25? **Answer:** It depends on the source version. Microsoft publishes supported upgrade paths, and older versions often need an intermediate step. Check the documented table for your exact version and test the whole path on a database copy before scheduling production. ### What breaks most often when updating Business Central? **Answer:** Custom and third-party extensions. Changed event signatures, removed obsolete elements and missing upgrade logic are the usual causes. The base product upgrade itself is rarely the problem, so test extensions first. ## Search terms upgrade to business central 25, business central 2024 release wave 2, how to update business central, business central version 25, update business central on premises, business central admin center update, business central extension upgrade, business central sandbox update test --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json