If your online store runs on Magento or Adobe Commerce, version 2.4.8 deserves a place on your roadmap. It raises the PHP floor, drops Elasticsearch in favour of OpenSearch and updates the database and caching stack. Stores on older versions can no longer assume that their server setup will carry over.
This Adobe Commerce 2.4.8 guide summarises the platform requirements from Adobe’s own release notes and turns them into an upgrade plan. It is written for store owners and project managers, with enough detail for developers. Check the official release notes for exact figures, because they are updated regularly.
| Platform area | Adobe Commerce 2.4.8 |
|---|---|
| PHP | 8.4 added, 8.3 supported, 8.2 interim only, 8.1 removed |
| Search | OpenSearch 2.19; Elasticsearch support dropped |
| Database | MySQL 8.4 LTS and MariaDB 11.4 LTS added |
| Composer and cache | Composer 2.8.x; Valkey 8.x support added |
What changes in Adobe Commerce 2.4.8
Adobe’s 2.4.8 release notes, last updated on 19 August 2026, describe these platform changes:
- PHP: PHP 8.4 compatibility is added and PHP 8.3 remains supported. PHP 8.2 is compatible only as an interim step for upgrading. PHP 8.1 is removed, and Adobe says you must upgrade to PHP 8.3 before moving to 2.4.8.
- Search: Adobe Commerce is optimised for OpenSearch 2.19 and drops Elasticsearch support, with Elasticsearch 7 and 8 options deprecated.
- Databases: MySQL 8.4 LTS and MariaDB 11.4 LTS are added and recommended, while MySQL 8.0 and MariaDB 10.6 are still supported. The default collation moves to utf8mb4.
- Composer: updated to 2.8.x.
- Caching: Valkey 8.x support is added.
The notes also report hundreds of quality fixes, with security details in Adobe’s security bulletin. Secondary sources say 2.4.8 is supported until April 2028, but we could not confirm that on Adobe’s own lifecycle page, so verify it before you plan around it.
What the OpenSearch change means in practice
Search is how many shoppers find products, so the move from Elasticsearch to OpenSearch deserves its own plan. OpenSearch is a search engine that began as a fork of Elasticsearch, and Adobe’s notes now optimise for version 2.19 while deprecating the Elasticsearch options. For a store, the practical consequences are:
- A new search service to install and run, or a managed one from your host or a cloud provider.
- A reindex of the catalogue, which takes time on large product sets.
- A check of search extensions, such as autocomplete, synonyms or merchandising tools, since they may rely on engine-specific features.
- A before-and-after comparison of results, so relevance does not change by surprise.
Schedule the search move on staging early. It is usually the step that surprises teams most, because it involves infrastructure and not just code.
Why the PHP requirement matters most
PHP is the engine under your store, and the support dates are not negotiable. PHP 8.1 reached the end of its security support at the end of 2025, and the PHP project did not issue regular fixes for it during the critical October 2026 flaws. Our PHP vulnerability guide explains what happened, and our PHP 8.5 features guide lists current support dates. In short, a store on an old PHP version is exposed twice: to security risk and to a harder upgrade later.
What the database and caching updates mean
The release notes also add MySQL 8.4 LTS and MariaDB 11.4 LTS, set the default collation to utf8mb4 and add Valkey 8.x support for caching. You do not have to adopt every option on day one, since MySQL 8.0 and MariaDB 10.6 remain supported, but it is wise to know where you are heading.
A database version change should be rehearsed on a copy of production, because it touches every table. Pay attention to the collation change if your catalogue holds names or descriptions in several languages, such as Arabic and English, and test sorting and search on those fields. For caching, ask your host whether Valkey is available, and test cache clearing and session behaviour after any change. As always, keep a full backup and a rollback path ready before touching the database layer.
Who needs to act now
You should plan if any of these is true:
- Your store runs on PHP 8.1 or older.
- You use Elasticsearch for catalogue search.
- You are on an older 2.4.x version, since one secondary source reports that support for 2.4.4 ended in April 2026. Confirm your version’s status with Adobe.
- You rely on extensions that have not been updated recently.
A realistic upgrade plan
Step 1: Inventory your stack
List your Magento version, PHP version, database, search engine, caching layer, Composer version and every third-party extension, plus custom modules and theme.
Step 2: Check extension compatibility
Ask each vendor for a 2.4.8-compatible version, or test it yourself. Replace extensions that are abandoned. Extensions are the most common source of delay.
Step 3: Move PHP first
Upgrade your server to PHP 8.3 and fix compatibility errors in custom code, before changing Magento itself. This makes the later step smaller and reveals problems early.
Step 4: Plan the search migration
If you use Elasticsearch, schedule a move to OpenSearch and rebuild your indexes on staging. Test search, filters and sorting carefully, since they drive product discovery.
Step 5: Upgrade on staging, then production
Clone production to staging, run the upgrade with Composer, test the purchase flow and compare performance. Plan a maintenance window for production, with a backup and a rollback plan.
Questions to ask your Magento partner
A good partner should be able to answer these before you approve the work:
- Which version are we on, and what is the supported upgrade path to 2.4.8?
- Which extensions are not yet compatible, and what are the alternatives?
- How will search move from Elasticsearch to OpenSearch, and how will we check relevance?
- Where will the upgrade be rehearsed, and with what data?
- What is the rollback plan, and how long does a rollback take?
- Who will monitor the store for a week after cut-over?
Ask for the answers in writing, with dates. Vague replies on the first three questions usually mean the audit has not happened yet, and any quote given before an audit is a guess.
Costs, timing and risk
Upgrades like this are rarely quick. The effort depends on how many extensions and custom modules you have, how far behind your current version is and how heavily search and integrations are used. We cannot give a fair estimate without looking at your code, but we can say what drives it: the number of third-party extensions, the amount of custom code, the state of your test coverage and the size of your catalogue.
Keep the old environment available until the new one has run for a few days. Schedule the production cut-over outside peak trading, and avoid doing it just before a major sale. If you cannot avoid a sale period, freeze other changes first so that any problem has only one possible cause.
What to test
- Catalogue browsing, search and filters.
- Cart, checkout and every payment method.
- Customer accounts, orders and emails.
- Admin tasks, imports and cron jobs.
- Third-party integrations such as ERP, shipping and tax.
- Page speed and server load.
Is it time to rethink the platform?
A major upgrade is a natural moment to ask whether you still need Adobe Commerce. Sometimes the answer is yes, for complex catalogues, B2B rules and heavy integrations. Sometimes a lighter platform fits. Our Shopify vs WooCommerce comparison explains how we think about that choice, and our Magento development team can assess your store honestly.
Keeping a Magento store healthy after the upgrade
An upgrade is a milestone, not the end of maintenance. After the cut-over, keep applying patch releases and security updates, review extensions every quarter and watch performance and error logs. Keep your PHP, database and search versions on supported dates, using the same yearly review we recommend for every platform. Stores that treat upgrades as small, regular tasks tend to avoid the large, expensive rescues that follow years of delay.
A simple timeline for planning
For many stores a sensible sequence is: audit and estimate in the first month, PHP and infrastructure changes in the second, extension updates and custom code fixes in the third, a full test cycle on staging in the fourth and the production cut-over in the fifth, outside peak trading. Larger stores with many integrations may need longer.
Block time for the unknown, because every real store has surprises. Share the timeline with marketing and operations, so campaigns are not planned for the week of the cut-over, and agree a change freeze that begins before the final test.
What to document as you go
Upgrades go better with notes. Record each extension and its version, every custom module and what it does, the server and search configuration, scheduled jobs and integrations with other systems. Write down each issue you meet and how it was fixed. Next time, the upgrade starts from a clear picture, and a new developer can take over without weeks of archaeology. Good documentation is one of the cheapest forms of risk reduction on a complex store.
Planning a Magento or Adobe Commerce upgrade?
We can inventory your stack, test extensions, move PHP and search and run the 2.4.8 upgrade on staging before production.
Frequently Asked Questions
Which PHP version does Adobe Commerce 2.4.8 need?
Adobe’s release notes say PHP 8.1 is removed and you must upgrade to PHP 8.3 before moving to 2.4.8. PHP 8.4 is supported, and PHP 8.2 works only as an interim step.
Does Adobe Commerce 2.4.8 still support Elasticsearch?
No. The release notes say it drops Elasticsearch support and is optimised for OpenSearch 2.19, with Elasticsearch 7 and 8 options deprecated.
Should I upgrade directly from an old 2.4.x version?
Plan it as a project: move PHP first, check extension compatibility, upgrade on staging and test the purchase flow. Ask your developers to confirm the supported upgrade path from your current version.

