This page has moved and will be redirected soon. See Migrated topics for the complete list.
Adobe Commerce only. Learn more.


The Upgrade Compatibility Tool is a command-line tool that checks an Adobe Commerce customized instance against a specific version by analyzing all modules installed in it. It returns a list of errors and warnings that must be addressed before upgrading to the latest version of Adobe Commerce.


The following diagram shows the expected workflow when running the Upgrade Compatibility Tool:

Upgrade Compatibility Tool Diagram

Who is the Upgrade Compatibility Tool for?

The following use case describes the typical process for an Adobe Commerce partner to upgrade a client’s instance:

  1. A partner’s Software Engineer downloads the Upgrade Compatibility Tool package from the Adobe Commerce repository and executes it during the beta phase of the newest Adobe Commerce release. See the Download the Upgrade Compatibility Tool topic for more information.
  2. The Software Engineer generates a vanilla instance for the specific version of Adobe Commerce that is currently installed. See the Contributor guide for more information on using the instance command to generate a vanilla installation.
  3. The Software Engineer sees that there are several customized areas broken in the inventory and catalog modules and they also get a complexity score of X. See the Developer guide for more information on the complexity score.
  4. With this information, the Software Engineer is able to understand the complexity of the upgrade and is able to relay this information back to the partner’s Account Manager.
  5. The Account Manager creates a timeline and cost for the Adobe Commerce upgrade, which allows them to get their manager’s approval.
  6. With their manager’s approval, the Software Engineer works on the required code modifications to fix the broken modules.
  7. The Software Engineer runs the Upgrade Compatibility Tool one more time with an Adobe Commerce pre-release to ensure there are no new issues and that their code changes fixed the problems found during the beta phase.
  8. Everything checks out and the Software Engineer pushes the code to a staging environment where regression tests confirm all tests are green, which allows them to release the latest Adobe Commerce version to production the same day that the Adobe Commerce pre-release is released.

Upgrade Compatibility Tool audience

A vanilla instance is a clean installation of a specified version tag or branch for a specific release version.


See prerequisites for more information.

You can run the Upgrade Compatibility Tool in any operating system. There is no requirement to run the Upgrade Compatibility Tool where your Adobe Commerce instance is located. It is necessary for the Upgrade Compatibility Tool to have access to the source code of the Adobe Commerce instance. For example, you can install the tool on one server and point it at your Adobe Commerce installation on another server.

If you are running the Upgrade Compatibility Tool against an Adobe Commerce instance with large modules and files, the tool might require a high amount of RAM, at least 2GB RAM.

Adobe Commerce best practices recommend to avoid having two modules with the same name. If this happens, the Upgrade Compatibility Tool will show a segmentation fault error.

To avoid this error it is recommended to run the bin command with the added option -m:

bin/uct upgrade:check /<dir>/<instance-name> --coming-version=2.4.1 -m /vendor/<vendor-name>/<module-name>

The <dir> value is the directory where your Adobe Commerce instance is located.

The -m option allows the Upgrade Compatibility Tool to analyze each specific module independently to avoid encountering two modules with the same name in your Adobe Commerce instance.

This command option also allows the Upgrade Compatibility Tool to analyze a folder containing several modules:

bin/uct upgrade:check /<dir>/<instance-name> --coming-version=2.4.1 -m /vendor/<vendor-name>/

This recommendation also helps with memory issues that can occur when executing the Upgrade Compatibility Tool.

Download the Upgrade Compatibility Tool

To download the Upgrade Compatibility Tool, run the following command:

composer create-project magento/upgrade-compatibility-tool uct --repository


To install the Upgrade Compatibility Tool, you must install the necessary prerequisites:

  • Adobe Commerce access keys
  • Composer
  • Node.js

Refer to the Upgrade Compatibility Tool install page.

Adobe Commerce access keys

You must have Adobe Commerce access keys to download and use the Upgrade Compatibility Tool. Add your Adobe Commerce access keys to your auth.json file, which is located at ~/.composer by default.

Check your COMPOSER_HOME environment variable to see where the auth.json file is located.

The public key corresponds to the username whereas the private key is the password:

Example of Adobe Commerce access keys

    "http-basic": {
        "": {
            "username": "YOUR_MAGENTO_PUBLIC_KEY",
            "password": "YOUR_MAGENTO_PRIVATE_KEY"


Clone the Upgrade Compatibility Tool repository and run composer install in your terminal to install dependencies.

If the Adobe Commerce access keys are not correctly configured, the Upgrade Compatibility Tool will not install and you will get errors when running the composer install command.


To install Node.js, see the Node.js documentation.

Third-party extensions

Adobe recommends that you contact your extension vendor to determine whether your extension is fully compatible with Adobe Commerce 2.4.x.

See Run the tool for information about executing the Upgrade Compatibility Tool.