Small and medium business | Business Central, N...

upgrade on-prem bussines central effects on database or not what measures we need

(8) Share

Report

Posted on by LA-02071030-0

359

if we upgrade on-prem business central from this version 21.2.49946.49990 to some higher version it effects or not

1.database

2.or any other customization

3.published extension

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

Jainam M. Kothari 15,887 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hello,

Upgrading your on-premises Business Central from version 21.2.49946.49990 to a higher version can affect several areas:

Database: The upgrade process typically includes schema changes, new tables, or modified fields. Microsoft provides upgrade scripts to handle this, but custom tables or fields may require manual adjustments or migration steps.

Customizations: If you've made code customizations directly in the base application (C/AL or AL), these may break or need to be reworked due to changes in the application structure or deprecated features in newer versions.

Published Extensions: Extensions may need to be recompiled or updated to be compatible with the new version. If the upgrade introduces breaking changes in the AL language or base application APIs, your extensions might fail to publish or run until updated.

Was this reply helpful? Yes No
Suggested answer

Mansi Soni 8,981 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Hello,

Yes, upgrading your on-prem Business Central from version 21.2 to a higher version can impact all three areas:

1. Database – The schema may change during the upgrade, requiring a technical data upgrade. Always back up the database and run the upgrade routines.

2. Customizations (C/AL or AL) – Any code customizations need to be reviewed and possibly refactored to be compatible with the new version.

3. Published Extensions – Extensions may need to be recompiled or upgraded if there are breaking changes in the new platform or base app. Always validate extensions post-upgrade.

Testing in a sandbox or staging environment before production upgrade is strongly recommended.

Hope this answer will help you as well!

Regards,
Mansi Soni

Was this reply helpful? Yes No
Suggested answer

Andrés Arias 5,168 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

Yes, the version upgrade can impact all three areas.

At the database level, developments and extensions changes can occur at the database level, upgrades can affect developments and extensions.

I recommend performing an end-to-end validation in a test environment. And only with such confirmation perform the upgrade.

I hope I can help.

Regards,

Andres

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 100,001 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

This will have an impact, but there is no way around it. BCv21 is no longer supported. If you do not upgrade to the latest supported version, there will be security issues.

Therefore, you need to complete all upgrade tests in the test environment before upgrading the production environment.

Thanks

ZHU

Was this reply helpful? Yes No
Gerardo Rentería Ga... 26,098 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi
An upgrade definitely impacts all of the above, both technically and functionally. It can impact any extension due to incompatibility issues that you must address before migrating.
Best
GR

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,171 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Yes, upgrading Business Central On-Prem from version 21.2 to a higher version will affect the database and extensions. Here’s what to consider:

1. Database:

The schema might change between versions.

You need to run data upgrade steps after restoring the database to the new version.

Backup the DB before upgrade is essential.

2. Customizations (C/AL or AL):

Old C/AL customizations must already be moved to AL by v21.

You must check that all AL code compiles and runs under the new version (API changes, deprecated functions, etc.).

3. Published Extensions:

Recompile and re-publish all extensions against the new platform.

Some extensions may need updates due to breaking changes or obsoleted objects.

🛠 Measures to take before upgrade:

Backup everything (DB, extensions, settings).

Test upgrade in a sandbox first.

Review Microsoft’s release notes.

Rebuild symbol references for all extensions.

✅ Mark this answer as verified if it helps you.

Was this reply helpful? Yes No