How to Perform Magento Update to Latest Version 2026 Guide

Magento 2 upgrade to latest version ensures your store stays secure, fast, and compatible with the latest features. But without the right preparation, it can lead to broken modules, data issues, or even downtime.

In this guide, we’ll walk you through the three main methods:

• Upgrading Magento using command line (via Composer)
• Manually updating Magento
• Using Web Setup Wizard

Let’s start with the reason why every Magento store owner should keep their version up to date.

---

Magento Upgrade Methods: Which One Should You Use?

All in all, the right method depends on your current Magento setup, technical expertise, store complexity, and how much downtime or risk you're willing to accept.

Here's a quick comparison to help you decide before following the detailed instructions below:

Our recommendation: If your store already uses Composer—which is the standard for modern Magento installations—the Composer upgrade method is the safest and most future-proof approach. If you're running an older Magento version without Composer or have a highly customized store, consider either a manual upgrade (only if necessary) or a migration-based approach to reduce upgrade risks.

---

Why Should You Perform the Magento 2 Upgrade?

After the discontinuation of Magento 1, businesses and online retailers turned to its successor, Magento 2. It introduced a range of new features and enhanced flexibility, offering businesses a robust platform to adapt to evolving customer needs and industry demands.

A Magento 2 upgrade to latest version is not optional, but rather a necessary part of running a stable and secure eCommerce site. When you stay on an outdated version, your store is more likely to face:

• Security risks
• Performance issues
• Extension and theme conflicts
• Compatibility problems with newer PHP or MySQL versions

That’s why Adobe Magento continues to release new versions of Magento with improvements across performance, security, and platform support.

For example, one of the latest versions of Magento is Magento Open Source 2.4.8. Here are the key highlights of Magento 2.4.8:

• Full support for PHP 8.4 and MariaDB 11.4
• MySQL 8.4 LTS compatibility
• OpenSearch as the new default search engine (replacing Elasticsearch)
• Dependencies like league/flysystem, monolog, and less.php have been upgraded. Old libraries such as jQuery/fileUploader and ExtJS have been replaced by Uppy and jsTree.
• A new TinyMCE editor (7.3.0) for better content editing

If you’re still using an older version, such as 2.4.5 or earlier, a Magento 2 upgrade helps ensure long-term stability and prevents unexpected issues in the future.

---

What to Prepare Before The Magento 2 Upgrade?

It’s worth noting that each Magento 2 upgrade release is compatible with specific versions of PHP, database systems, libraries, and extensions. So before jumping into the upgrade, it’s essential to ensure your environment meets the requirements of Magento 2.4.9 (or any version you’re targeting).

1. Backup your Magento store completely

Before making any changes, you should back up both the Magento file system and the database of your Magento site. This includes:

• /pub, /app, /vendor, and /generated folders
• Your theme and extension files
• Media files (product images, banners)
• Your Magento MySQL database

It will matter the most when the Magento version upgrade fails or breaks your site; a full backup allows you to roll back quickly without data loss.

2. Check if your server meets Magento system requirements

Each Magento version is accompanied by updated system requirements, particularly regarding PHP, database engines, and supported libraries. Upgrading without verifying these may result in critical errors or broken functionality.

Below is a breakdown of system requirements for Magento 2.4.6, 2.4.7, and 2.4.8, so you can compare them and make necessary adjustments before proceeding to the Magento 2 upgrade to latest version.

Component	Magento 2.4.6	Magento 2.4.7	Magento 2.4.8
PHP	8.1	8.1	8.4 (8.1 removed)
MySQL	8.0	8.0	8.4 LTS
MariaDB	10.4 / 10.6	10.6	11.4
Elasticsearch	Supported	Supported (deprecated)	Deprecated
OpenSearch	Optional (1.2)	Recommended (2.5)	Default (2.11)
Composer	2.x	2.x	2.x
TinyMCE Editor	5.x	5.10.2	7.3.0
JS Libraries	jQuery/fileUploader, ExtJS	Partial replacement	Replaced with Uppy + jsTree

Magento 2.4.8 completely drops support for PHP 8.1, and Elasticsearch is now fully deprecated. If your environment still uses them, you’ll need to upgrade your server stack before upgrading Magento.

If you want to check your current environment, run these SSH commands:

php -v         # Check PHP version
mysql -V       # Check MySQL version
composer -V    # Check Composer version

You can also check the search engine used by inspecting your env.php configuration or checking Admin > Configuration > Catalog > Catalog Search.

3. Review extensions, custom modules, and theme compatibility

Many store owners forget this step. After a Magento 2 upgrade, incompatible extensions or themes may break your frontend or cause conflicts. You should do this:

• Review each installed module (especially those from third parties)
• Visit the extension provider’s site to confirm Magento 2.4.9 support
• Update modules if newer versions are available
• If you’ve made core code customizations, test those in a staging environment.

For custom-built features, consider asking your developer to conduct a code audit.

4. Plan for maintenance mode and cron control

Magento upgrades to latest version require you to:

• Enable maintenance mode to prevent frontend visitors from seeing errors
• Disable cron jobs temporarily to avoid scheduling conflicts during setup

You’ll run these steps later in the Composer or the manual Magento 2 upgrade process, but it's good to understand them ahead of time.

5. Ensure SSH access and Composer setup

Upgrading Magento is a straightforward process that you can manage using the command line interface (CLI). To get started with your upgrade, you'll need a few things:

• SSH access to your server
• Magento CLI privileges (bin/magento)
• A working installation of Composer 2.x

If you’re unsure about these, contact your host or developer to confirm CLI access. Once everything is prepared, you’re ready to begin the upgrade.

---

How to Upgrade Magento to Latest Version

Now that you have prepared everything before the upgrade, let's go into each of the three methods using command line, manual process, and Web Setup Wizard:

Method 1. How to Perform Magento 2 upgrade using command line

For most Magento stores, Composer is the recommended method to perform upgrades. It gives you better control over dependencies, extensions, and system updates, especially for stores with custom development or third-party integrations.

1. Enable maintenance mode

To get things started, activate maintenance mode to restrict access to your store while the Magento 2 upgrade is in progress.

Follow this guideline to install the application, which enables you to use the Magento maintenance CLI command. Then, the steps become much easier. All you have to do is copy and paste the following command for maintenance mode enablement:

bin/magento maintenance:enable [--ip=<ip address> ... --ip=<ip address>] | [ip=none]

The “–ip=<ip address>” option allows you to exclude a specified IP address from maintenance mode, which is helpful for situations like developers working on maintenance. For instance, this command line will enable maintenance mode for everyone except 192.0.2.10 and 192.0.2.11:

bin/magento maintenance:enable --ip=192.0.2.10 --ip=192.0.2.11

Once you've put the application into maintenance mode, it's crucial to halt all message queue consumer processes. You can identify these processes by running the command “ps -ef | grep queue:consumers:start”, followed by executing the “kill <process_id>” command for each consumer. In a multi-node setup, you should perform this task on each node.

2. Disable cron jobs

Starting the upgrade procedure while asynchronous processes, like message queue consumers, are active can potentially lead to data corruption. Therefore, we must disable the cron jobs.

Different Magento editions will require distinct command lines to perform the task. In other words, for those of you who are using Adobe Commerce on cloud infrastructure, paste this snippet:

./vendor/bin/ece-tools cron:disable

Meanwhile, Magento Open Source users will need the following source code:

bin/magento cron:remove

You then start all message queue consumers manually to ensure that all messages are consumed using:

bin/magento cron:run --group=consumers

When the cron job finishes, you can execute the ps aux | grep 'bin/magento queue' to keep track of the task process.

3. Create a composer backup

At this step, create a backup for your composer.json file with this command line:

cp composer.json composer.json.bak

4. Manage the packages

Moving forward, we will include or exclude specific packages based on your requirements. Specifically, when migrating from Magento Open Source to Adobe Commerce, you will need to remove the Magento Open Source package.

composer remove magento/product-community-edition --no-update

5. Update your instance

Then, update your installation by utilizing the specified syntax for the composer require-commerce command:

composer require-commerce magento/<product> <version> --no-update [--interactive-root-conflicts] [--force-root-updates] [--help]

As you can see, there are a few command options included, and each takes on a special role:

• <product>: The package for the upgrade should be either product-community-edition or product-enterprise-edition for on-premises installations.
• <version>: The version of Adobe Commerce or Magento Open Source to which you are performing the upgrade, such as 2.4.3.
• --no-update: Deactivates the automatic updating of dependencies.
• --interactive-root-conflicts: This enables you to interactively review and modify any outdated or customized values from prior versions that do not align with the version you are upgrading to.
• --force-root-updates: Replaces all conflicting custom values with the standard Magento values.
• --help: Provides comprehensive information regarding the plugin’s usage.

6. Upgrade metadata

We’re almost there! But, before that, we have to update the metadata. Here are the steps:

Step 1: Open your composer.json file and modify the name, version, and description according to your requirements.

Step 2: Paste in the update command line:

composer update

Step 3: Clean the var/ and generated/ subdirectories:

rm -rf var/cache/*
rm -rf var/page_cache/* 
rm -rf generated/code/*

Step 4: Make adjustments to the database schema and data as necessary

bin/magento setup:upgrade

Step 5: Turn off maintenance mode

bin/magento maintenance:disable

Step 6: If your store uses Varnish for page caching, don’t forget to restart it:

service varnish restart

7. Double-check your work

That’s everything for the Magento 2 upgrade to latest version! Open a new tab and fill in your store’s URL to verify the success. If the upgrade does not go as planned, your storefront will not load correctly.

Another scenario is that you may receive a message saying, “We're sorry, an error has occurred while generating this email.” To solve the problem, here’s how:

• Switch to a user with root privileges, then reset file system ownership and permissions.
• Empty the following directories: var/cache/, var/page_cache/, and generated/code/.
• Review your store on a new browser.

Now that the codebase is updated, apply any database changes required by the new Magento version: bin/magento setup:upgrade. This may also regenerate indexes or apply patch data.

If your store is in production mode, recompile and redeploy static files:

bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f

This step ensures your store’s frontend and admin panel load correctly.

Once you’ve confirmed that the site is working, take it out of maintenance mode:

bin/magento maintenance:disable

At this point, you can re-enable cron jobs and run a full test of your store:

• Check the homepage, product pages, checkout, and admin panel
• Verify that all installed extensions still work properly
• Monitor logs (var/log/system.log) for any errors

If anything goes wrong, you can restore from the backup and review Composer or server logs for issues.

Method 2. How to perform Magento 2 latest version update manually

If you’re not using Composer—or prefer to upgrade Magento manually—you can do so by downloading the latest release package and replacing your current installation. This method is more technical and should only be used if Composer is not available or if you're working in a non-Composer Magento setup.

1. Download the latest Magento 2 version

First, download the latest version of Magento 2 and extract the zip file into your store’s root directory. Extract the file and click “Yes” if the system prompts to replace any existing files.

2. Run SSH Commands

After unzipping the Magento upgrade folder, it’s time to make use of these SSH commands:

php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
php bin/magento cache:clean
php bin/magento indexer:reindex

These commands will refresh the database schema, upgrade dependencies, and clear caches. Once this process is complete, you can verify the functionality of both the Magento 2 frontend and admin panel to ensure that everything operates correctly following the upgrade.

Important note:  A manual Magento 2 upgrade carries a higher risk if done incorrectly. Always test this on a staging site first before applying it to your live store.

Method 3. Magento Web Setup Wizard: Legacy option only

The Web Setup Wizard in Magento 2 provides a simplified way to manage extensions, modules, and perform system upgrades directly from the Admin Panel, eliminating the need to manually edit the source code.

However, please note that starting from Magento 2.4.0, the Web Setup Wizard is no longer supported for upgrades. If you’re using Magento 2.3.7, 2.3.6, or any 2.3.x version, you can still use this method. For Magento 2.4.0, 2.4.7, 2.4.8, or 2.4.9, we recommend upgrading via Composer or using the LitExtension migration service instead.

If your Magento version is older than 2.4.0, follow the steps below for a safe Magento 2 upgrade using the Setup Wizard:

• Firstly, go to System > Tools > Web Setup Wizard from the admin panel.

• Then, enter the Authentication Keys into the System Configuration and save to continue.
• Finally, activate the System Upgrade. Be aware that you may receive a request to update PHP to the latest version as part of the procedure.

Note: If your store still uses Magento 1, check out how to migrate Magento 1 to Magento 2 here.

---

Perform Post-Upgrade Checks Before Going Live

The upgrade is complete, but you shouldn't assume your store is ready for customers right away. No matter which method you use, it's simportant thoroughly test your store before switching traffic to the new version.

We recommend using the following checklist to verify that every critical part of your Magento store is working correctly:

For Composer and manual upgrades, you should also rebuild Magento's generated content before performing these checks:

php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy -f
php bin/magento cache:clean
php bin/magento cache:flush
php bin/magento indexer:reindex

---

Common Magento Upgrade Issues and Fixes

Upgrading Magento can bring its own set of challenges, but you’re not alone. Many users encounter similar issues, particularly when working with Composer, server settings, or custom code. The table below summarizes the most common Magento upgrade errors, their likely causes, and recommended solutions:

---

Need Help Upgrading Magento Without the Technical Hassle?

Upgrading Magento is not always a simple version update, especially if your store has custom themes, third-party extensions, payment modules, or complex product data. For non-technical store owners, the hardest part is not only running the upgrade commands, but also making sure the new Magento version works properly after launch.

If you don’t want to handle server requirements, extension conflicts, backup, data transfer, testing, and post-upgrade checks on your own, LitExtension can help you manage the process with its professional Magento upgrade services.

With LitExtension, your Magento store can be upgraded in a more structured way, from preparing the new environment and migrating store data to checking products, customers, orders, URLs, and other key store elements before going live. This helps reduce technical risks and gives you a clearer path to move to the latest Magento version without disrupting daily business operations.

---

Your Magento Upgrade, Done Right!

---

Upgrade Magento 2 to Latest Version: FAQs

---

Final Words

A Magento upgrade is a critical part of maintaining a secure, high-performing online store. However, they often involve more than just updating files, especially when dealing with custom modules, third-party extensions, and evolving system requirements.

While the upgrade process can be complex, especially for customized stores, careful planning and the right upgrade method — whether through Composer, manual file replacement, or professional migration services like LitExtension — can make a major difference.

Before you start, always remember:

• Check compatibility carefully (PHP, MySQL, extensions, custom code)
• Use a staging environment first
• Back up everything
• Allocate realistic time and resources for testing and debugging

If you want a faster, safer Magento upgrade to 2.4.9 or any version without the technical hassle, feel free to explore our Magento Upgrade Services. Our experts are here to help you move to the latest Magento version smoothly and securely.

Find more eCommerce insights via our LitExtension blog or Facebook community group.