Magento Open Source Adobe Commerce Storefront design & front-end Independent · not affiliated with Adobe
Magento Themes Store Storefront Lab
Published 13 Nov 2026 9 min read

Upgrading to Magento 2.4.9: what breaks, and in what order to fix it

A controlled Magento 2.4.9 migration depends on supported infrastructure, extension compatibility and staged verification, not merely running the upgrader.

Why 2.4.9 is not a routine version bump

Magento Open Source and Adobe Commerce 2.4.9 became the current general release on 12 May 2026. The application version is only one part of the change: Adobe lists a new set of supported platform components for 2.4.9.

Component Supported combination for 2.4.9
PHP 8.5
Database MariaDB 12.3 or MySQL 8.4
Search OpenSearch 3
Cache and sessions Valkey 9
Message queue RabbitMQ 4.3
Composer 2.10

Adobe describes these as the only supported combinations for on-premises 2.4.9. Elasticsearch and Redis are not on that list. A store moving from 2.4.6 or 2.4.7 may therefore face a PHP upgrade, a search-engine migration to OpenSearch and a cache and session migration to Valkey before Magento can be upgraded safely.

That distinction matters. An application upgrader cannot repair a deployment whose database, queue, search service or session store is outside the supported matrix. Treating infrastructure as a separate workstream is the difference between a controlled migration and a failed cut-over.

The order of operations

1. Establish the current version and the gap

Record the installed Magento edition, version, edition key where applicable and the Composer lock file. Check the versions of PHP, the database, search engine, cache and session store, RabbitMQ and Composer against the 2.4.9 requirements.

Do not infer the application version from the version shown in the admin footer alone. Compare it with the package versions in composer.lock and the database schema version. This establishes whether the project is receiving a straightforward incremental upgrade or has missed several dependency changes.

Then identify the path to 2.4.9. Magento releases have their own upgrade instructions, dependency constraints and known compatibility issues. The path should be planned from the version actually installed, not reconstructed from a generic “latest version” guide.

2. Inventory extensions, themes and integrations

List every first-party and third-party package, including payment, shipping, tax, ERP, PIM, analytics, review, loyalty, customer-service and fulfilment integrations. Check each one against 2.4.9 rather than assuming that a recent installation date means compatibility.

For each extension, look for:

  • A release that explicitly supports 2.4.9 and PHP 8.5.
  • Compatible constraints for the selected database, OpenSearch, Valkey and RabbitMQ versions.
  • Any required upgrade command, data migration or replacement configuration.
  • Changes to cron jobs, webhooks, queues, indexes or scheduled tasks.
  • Whether the extension replaces core classes or depends on a private package.

Do the same for custom themes and integration packages. A theme may work visually while failing on checkout because its Knockout component, RequireJS dependency or template override has changed. An extension may pass its own test suite but conflict with another extension that upgrades the same core class.

Identify previous customisations that have since been incorporated upstream. Keeping both an old override and the newer core implementation can produce subtle failures, particularly in checkout, tax calculation and order processing. The extension side of this audit is covered in more detail in the module layer.

3. Take a real staging copy

Create a staging environment using the intended production topology. The copy needs representative catalogue data, including variations, configurable products, bundle products, tier prices and promotional rules. Include realistic customer, order and invoice data where lawful and appropriately anonymised.

A catalogue containing only simple products will not reveal the same indexing, pricing or template problems as the production catalogue. Include the languages, currencies, tax rules and store views that the business operates. Keep sanitised test accounts ready for customer registration, checkout and admin workflows.

Capture the current behaviour before changing anything. Record sample catalogue URLs, admin search results, checkout totals, payment responses, order states and relevant cron output. A migration without a baseline makes it difficult to distinguish a pre-existing defect from a regression introduced during the upgrade.

Test the staging environment more than once if the upgrade involves moving data between search or session services. A successful rebuild on an empty index proves little if the production catalogue contains edge cases.

4. Move the infrastructure first

Provision PHP 8.5, either MariaDB 12.3 or MySQL 8.4, OpenSearch 3, Valkey 9, RabbitMQ 4.3 and Composer 2.10. Update the surrounding platform, including the web server, PHP-FPM workers, process supervision, cron, TLS termination and backup tooling.

Where Redis currently handles caching or sessions, plan the move to Valkey. Test application connectivity, serialisation, expiry behaviour and session continuity. Do not assume that running two cache systems side by side is safe; use one deliberate cut-over point and clear stale data where required.

For Elasticsearch deployments, move search to OpenSearch and rebuild indexes from the database rather than carrying an index across as though the engines were interchangeable. Validate the analyser behaviour, searchable attributes, filters, sorting and admin grid queries. Search relevance can change when an index is recreated, so compare representative queries rather than relying on the fact that results appear.

Check that background consumers can reach RabbitMQ and that queues contain no obsolete jobs from the previous application version. Upgrade cron and worker processes at the same time as the application so they do not execute old code against the new schema or vice versa.

Take backups and verify that they can be restored. A backup command that reports success is not evidence until a restore has been completed in a separate environment.

5. Run the application upgrade

Update dependencies only after the infrastructure satisfies the 2.4.9 requirements. Resolve Composer conflicts deliberately rather than suppressing them. A forced package update can leave Magento with incompatible interfaces even when installation completes.

Put the store into maintenance mode before changing the database schema or replacing code that workers and cron may still be using. Follow the official 2.4.9 instructions for the edition being deployed, including any data migrations that must run before or after the schema upgrade.

The deployment sequence will normally include the Magento setup upgrade, dependency-injection compilation, static-content deployment, cache invalidation and index rebuilding. Keep generated artefacts and index work in the documented order, and do not allow the application to serve traffic while workers are using mixed old and new code.

Watch the deployment logs rather than checking only the final exit status. Pay particular attention to schema errors, queue consumers, cron failures and permission changes on generated directories. These can appear after the upgrader has otherwise completed.

What commonly breaks

Extensions that rewrite core classes

The most serious compatibility failures often come from extensions that replace Magento core classes, plugins, observers or layout instructions. Composer may report that the packages are installed and compatible, yet two extensions can still modify the same behaviour in incompatible ways.

Symptoms include an admin form that will not save, duplicate totals, missing order comments, failed state transitions, queue jobs that stop consuming and payment or shipping methods that disappear. Check whether the extension has a specific 2.4.9 release, and whether it requires replacement configuration files or a new index.

Test extensions in combination, not one at a time. Disable the suspicious extension only on staging, then retest the affected workflow. If the fault disappears, inspect its compatibility notes and its overrides rather than assuming that the core application is at fault.

Custom themes and overridden templates

Custom themes are most likely to fail where they rely on removed variables, changed Knockout components, altered RequireJS modules or outdated layout XML. The failure may be confined to one template, such as a mini-cart, product options or checkout shipping methods.

Compare custom templates with the corresponding 2.4.9 Blank or Luma files. Do not replace every override blindly: many overrides still contain valid business logic. Extract the custom part, reconcile it with the current template and test the rendered result.

Pay attention to JavaScript errors in the browser as well as visual differences. A missing Knockout binding can leave a page looking present but unable to update totals or submit an order. Theme architecture and the choice between Luma, Blank and newer approaches are covered in front-end and speed.

Code written against old cache or search clients

Custom PHP, scripts and deployment tools may use client APIs and configuration names from the previous Redis or Elasticsearch setup. Those integrations need to work with Valkey and OpenSearch as supported by 2.4.9.

Search for direct cache calls, session access, index APIs, hard-coded service names and environment variables. Test the custom code with the new services rather than assuming that only Magento’s own configuration has changed. Pay attention to serialisation, key prefixes, index aliases and timeout handling.

Third-party integrations with pinned libraries

Payment gateways, ERP connectors, shipping services and API clients frequently pin Guzzle, Symfony, Laminas or other libraries. A Magento 2.4.9 upgrade may require newer versions that fall outside those pins.

Test outbound HTTPS requests, webhook verification, API authentication and error handling. A successful catalogue page says nothing about whether a scheduled synchronisation can still reach its provider. Confirm that sandbox or non-production credentials exercise the same libraries and response formats as the live integration.

Verification order

  1. Admin grids and catalogue search. Check product, customer, order and invoice lists, then test filters and searches. These expose database, indexing and grid-component failures quickly.
  2. Checkout. Run guest and customer checkouts, including delivery estimation, tax calculation, coupon application, payment, order placement and the customer order history.
  3. Admin order processing. Move a test order through invoice, shipment, credit memo and notification paths. Verify that totals, comments and status changes remain consistent.
  4. Customer account and forms. Test registration, login, password reset, address editing, wishlists and newsletter or subscription forms.
  5. Search and merchandising. Confirm that products, filters, sorting and category results work through both storefront search and admin search.
  6. Background work. Inspect cron runs, queue consumers, scheduled imports, synchronisation jobs and any error emails or logs generated after the deployment.
  7. Payment and integration callbacks. Exercise the provider’s test responses, including success, failure and delayed callbacks where the integration supports them.
  8. Security and operational checks. Confirm HTTPS redirects, secure cookies, file permissions, admin access, backup completion and monitoring.

Run the first two checks before reopening the store. A storefront can look healthy while checkout is silently broken, and an admin grid can expose a failed index or database migration that customers would otherwise encounter later.

Keep the store in maintenance mode until the critical paths pass and the queue is stable. Then release traffic gradually where the hosting platform permits it. Watch application logs, worker logs, slow queries and failed jobs during the first period of real traffic.

Do not rely solely on the store’s appearance or a single successful order. Verification should include the catalogue, administration, checkout, background jobs and external integrations because each uses a different part of the upgraded platform.

Choosing between 2.4.9 and 2.4.8

Support dates provide a useful decision boundary:

  • Magento Open Source and Adobe Commerce 2.4.9 receive regular support until 31 May 2029.
  • Version 2.4.8 receives regular support until 31 May 2028.
  • Version 2.4.7 receives regular support until 31 May 2027, followed by extended support until 31 May 2028.
  • Regular support for 2.4.6 ended on 11 August 2026.

A store already on 2.4.8 can stop there if its extensions remain supported and it has no requirement for 2.4.9. That avoids the immediate platform migration, but it does not remove the need to plan for the end of 2.4.8’s regular support.

A store on 2.4.7 has less time before regular support ends. A store on 2.4.6 should treat the supported-platform gap as urgent rather than postponing another infrastructure review.

The 2.4.10-alpha1 release that appeared on 13 October 2026 is a pre-release and is not a production target. Its presence does not change the practical choice between remaining on a supported general release or moving to 2.4.9.

Questions this page answers

What supported platform components does Magento 2.4.9 require?
PHP 8.5, MariaDB 12.3 or MySQL 8.4, OpenSearch 3, Valkey 9, RabbitMQ 4.3 and Composer 2.10.
Why must infrastructure be migrated before the application?
An application upgrader cannot repair a deployment whose database, queue, search service or session store is outside the supported matrix.
What data should a staging copy include?
It should include representative catalogue data, realistic customer, order and invoice data where lawful and appropriately anonymised, plus the relevant languages, currencies, tax rules and store views.
How should an Elasticsearch deployment move to OpenSearch?
Move search to OpenSearch and rebuild indexes from the database rather than carrying an index across as though the engines were interchangeable.

More in Hosting & operations

Editorial & corrections: [email protected]