{"title":"Business Central upgrade considerations and preparation for v26 and later","url":"https://jonas-paprotka.de/docs/dev-itpro/upgrade/upgrade-considerations-v26/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-considerations-v26, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-considerations-v26","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"This article provides tips and considerations to prepare a solution when you're planning to upgrade to Business Central 2025 release wave 1 and later.","date":"2026-08-31","meta":{"topic":"article"},"outline":[{"level":1,"title":"Business Central upgrade considerations and preparation for v26 and later","slug":"business-central-upgrade-considerations-and-preparation-for-v26-and-later","at":0,"chars":8673},{"level":2,"title":"Deprecated or redesigned functionality","slug":"deprecated-or-redesigned-functionality","at":469,"chars":1506},{"level":2,"title":"Deleted objects","slug":"deleted-objects","at":1975,"chars":970},{"level":3,"title":"Effect on upgrade","slug":"effect-on-upgrade","at":2653,"chars":292},{"level":2,"title":"Schema changes in subscription billing extension","slug":"schema-changes-in-subscription-billing-extension","at":2945,"chars":889},{"level":2,"title":"Performance and upgrade considerations for installed extensions","slug":"performance-and-upgrade-considerations-for-installed-extensions","at":3834,"chars":2257},{"level":3,"title":"General guidelines","slug":"general-guidelines","at":4726,"chars":226},{"level":3,"title":"Data retention after uninstallation","slug":"data-retention-after-uninstallation","at":4952,"chars":631},{"level":3,"title":"Clean up orphaned extension data","slug":"clean-up-orphaned-extension-data","at":5583,"chars":508},{"level":2,"title":"Important deployment-related changes in version 23.0","slug":"important-deployment-related-changes-in-version-230","at":6091,"chars":1326},{"level":2,"title":"Transition to AL-based permissions and permission sets","slug":"transition-to-al-based-permissions-and-permission-sets","at":7417,"chars":1116},{"level":2,"title":"Related information","slug":"related-information","at":8533,"chars":140}],"text":"# Business Central upgrade considerations and preparation for v26 and later\nThis article provides important information and tips for things to consider when you prepare to upgrade to 2025 release 1 (version 26), 2025 release 2 (version 27), 2026 release 1 (version 28), or 2026 release 2 (version 29). The information that's relevant for you depends on which version you're upgrading from, and how much your solution differs from the Business Central base application.\n## Deprecated or redesigned functionality\nBusiness Central occasionally deprecates features in application and platform. In most cases, features are replaced by more modern and sustainable features. If you're upgrading a solution that depends on the deprecated or changes functionality, you might have to change application code as part of the upgrade process.\nFor example, sometimes code is refactored so that fields are no longer used. Or the functionality is moved from the base application to an extension. Typically, if you have custom extension code that depends on these fields, you have to create a new version of the extension to handle the change.\nLearn more about the deprecated features in:\n Deprecated Features in Application<deprecated-features-w1>\n Deprecated Features in the Platform - Clients, Server, and Database<deprecated-features-platform>\n Obsoleted elements in system application 26.0<https://learn.microsoft.com/dynamics365/business-central/application/system-application/obsoletion/obsolete_by_26.0>\n Obsoleted elements in base application 26.0<https://learn.microsoft.com/dynamics365/business-central/application/base-application/obsoletion/obsolete_by_26.0>\n Obsoleted elements in base application 27.0<https://learn.microsoft.com/dynamics365/business-central/application/base-application/obsoletion/obsolete_by_27.0>\n Obsoleted elements in base application 28.0<https://learn.microsoft.com/dynamics365/business-central/application/base-application/obsoletion/obsolete_by_28.0>\n## Deleted objects\n> APPLIES TO: Upgrade from v24.0 and earlier only\nMany tables and fields are deleted from the base application and other Microsoft extensions in Business Central. These objects were in the Obsolete::Removed state for more than one major release. For a complete list of the deleted objects, consult Deleted objects in 2025 release wave 1<deleted-objects-25w1>.\nThis change aligns with the cleanup cycle that occurs every fifth release. Learn more in the blog post Essential cleanup guide for partners: 2025 release wave 1<https://www.microsoft.com/en-us/dynamics-365/blog/it-professional/2025/02/06/essential-clean-up-guide-for-partners-2025-release-wave-1/>.\n### Effect on upgrade\nComplete these tasks before upgrading to version 26 later:\n1. Refactor custom code in non-Microsoft extensions, including upgrade code, to replace or remove references to these objects.\n2. Upgrade versions 24 or earlier to 25 before upgrading to version 26.0 and later.\n## Schema changes in subscription billing extension\n> APPLIES TO: Upgrade from v25.0 only\nVersion 25.0 introduced the Subscription & Recurring Billing extension. In version 26 and later, the extension is renamed to Subscription Billing. Several tables and fields in the extension are renamed, causing breaking changes when upgrading the extension from version 25.0 to 26.0 or later.\nTo upgrade the extension, you must synchronize the extension's database schema with the tenant database schema using a force sync operation. Force sync can cause data loss if custom code depends on the renamed tables and fields in the extension. To avoid data loss, refactor the custom code to match the extension's latest database schema before upgrading. For a list of renamed tables and fields, see known-issues#renamed-tables-and-fields-in-subscription-billing-extension-cause-synch-errors-on-upgrade.\n## Performance and upgrade considerations for installed extensions\nInstalling a large number of apps (extensions) in your Business Central environment can negatively impact performance and upgrade operations.\nInstalling a large number of apps (extensions) in your Business Central environment can negatively impact performance in several ways:\n Slower environment startup - Each installed extension adds to the initialization time when the environment starts or restarts. The system must load and initialize all installed extensions, even if they're not actively used.\n Longer upgrade times - Environment upgrades must process all installed extensions, which increases the overall upgrade duration. This impact grows with the number of extensions installed.\n Increased risk exposure - Extensions from untrusted sources can introduce security vulnerabilities or unexpected performance issues.\n### General guidelines\n Install only the extensions that are required for your business processes.\n Ensure that extensions come from sources you trust.\n Regularly review installed extensions and remove those no longer needed.\n### Data retention after uninstallation\nWhen an extension is uninstalled, its data remains in your database by design. This allows you to reinstall the extension later without data loss. However, this preserved data can have negative consequences:\n Increased database size - Orphaned extension data consumes database space that could be used for active business data.\n Slower runtime performance - The database must manage companion tables for uninstalled extensions, which can slow down data operations.\n Longer upgrade times - Environment upgrades process all tables in the database, including those from uninstalled extensions.\n### Clean up orphaned extension data\nUse the Delete Orphaned Extension Data page to identify and remove data from uninstalled extensions. This maintenance task:\n Frees up database capacity\n Reduces the row size in companion tables used to store extension data\n Speeds up data operations on affected tables\n Reduces upgrade complexity and duration\nLearn more:\n ../developer/devenv-unpublish-and-uninstall-extension-v2\n How Application Configurations Affect Performance<../performance/performance-application>\n## Important deployment-related changes in version 23.0\nThis section includes important deployment changes that are helpful to know when from coming from a version 22 and earlier deployment. These changes were introduced in version 23.0. These changes don't affect the upgrade process, just the deployment.\n The default port for client services port for Business Central Server changed to 7085 instead of 7046. You can still use 7046, but you have to change the port number in the Business Central Server instance configuration. See Configuring Business Central Server<../administration/configure-server-instance>.\n NET Core no longer supports Server principle names (SPN). This change affects the delegation from the Business Central Web Server to the Business Central Server when they're on different computers.\n  The affected scenarios are described in Deploying Business Central in a Two-Computer Topology<../deployment/deploy-two-computer-environment> and Deploying Business Central in a Three-Computer Topology<../deployment/deploy-three-computer-environment>.\n  Learn more about setting up delegation in Configuring Delegation for Business Central Web Server<../deployment/configure-delegation-web-server>. You can do this task anytime, but after upgrade, users won't be able to sign in to the web client until you do.\n## Transition to AL-based permissions and permission sets\nBusiness Central 2021 release wave 1 (v18) introduced a new model for permissions. In versions earlier than v18, permission sets and permissions are defined only as data, which means they're stored in the tables of the application and tenant databases. Starting with v18, permission sets and permissions can be defined in AL objects as part of extensions. This model is the default and recommended model for permissions and permission sets. Predefined permission sets provided in Microsoft extensions and most customization extensions are now defined by AL objects. See Entitlements and permission sets overview<../developer/devenv-entitlements-and-permissionsets-overview>.\nIf you haven't already, we recommend you transition your Business Central solution to this AL-based permissions model. You can continue to use the legacy data-defined permission sets after upgrade&mdash;these permission sets aren't affected by upgrade. However, this capability will be removed in a future version. See Upgrading Permission Sets and Permissions<upgrade-permissions>.\n## Related information\nupgrading-the-application-code\nupgrading-the-data\nDeprecated Fields, and Fields Marked as Obsolete<deprecated-fields>"}