This article provides an overview of the full upgrade process for Business Central in a multitenant deployment. For more detailed steps, see Upgrading the Data: Multitenant Mode.
Prerequisite tasks
| Step |
More info |
Done |
| In the old deployment, convert custom V1 extensions to V2 extensions. |
See... |
|
| Export permissions and permission sets from the old deployment. Important: Make sure computer uses the same codepage as the data. |
See... |
|
| Export encryption keys from the old deployment. |
See... |
|
| Prepare for transitioning from codeunit 1. |
See... |
|
| Install Business Central components. |
See... |
|
Upgrade the application and prepare it for data upgrade
| Step |
More info |
Done |
| Upgrade the application code. |
See... |
|
| Mount the upgraded application on the Business Central Server instance. |
See... |
|
| Import upgrade toolkit (.fob) |
See... |
|
| Publish system and test symbols from the installation media, and generate application symbols. |
See... |
|
| Publish the new Microsoft extension versions from the installation media. |
See... |
|
| Upload a Business Central partner license. |
See... |
|
Prepare the tenant database for data upgrade
| Step |
More info |
Done |
| Backup the tenant database. |
See... |
|
| Uninstall all V1 extensions. |
See... |
|
| Dismount the tenant from the old server instance. |
See... |
|
Run the data upgrade on the tenant
| Step |
More info |
Done |
Mount the tenant on the Business Central Server instance. Important: Use the -AllowAppDatabaseWrite parameter. |
See... |
|
| Synchronize the tenant. |
See... |
|
| Synchronize all extensions. |
See.. |
|
Run the data upgrade. Important: If there are V2 extensions, you must use the -FunctionExecutionMode Serial parameter. |
See... |
|
| Install the new V2 extensions that were not installed in the old tenant. |
See... |
|
Post-upgrade tasks
| Step |
More info |
Done |
| Import permissions and permission sets. |
See... |
|
| Import encryption keys |
See... |
|
| Upload the customer license. |
See... |
|