Guide
By Marcio Maciel · Co-founder · Digital Business Engineering
Published July 17, 2026
MySQL 8.0 reached end of support from Oracle on April 30, 2026. Adobe Commerce / Magento 2.4.5 and 2.4.6 operations that still depend on that database accumulate compound risk with the platform release line end of support. On-premises, Adobe recommends migrating the database server to a compatible MariaDB version. On Adobe Commerce on Cloud, the documented requirement is to keep platform dependencies on versions supported by the lifecycle policy. The cost of updating the database and/or Adobe Commerce / Magento to supported versions belongs in the TCO. Magecore updates infrastructure and Adobe Commerce / Magento on Cloud and on-premises.
Oracle documentation states that MySQL 8.0 reached end of support on April 30, 2026. After that date, the 8.0 line no longer receives the regular security-fix cycle operations expect from an actively supported database.
Adobe confirms the same date in its database compatibility guidance for Adobe Commerce. For the 2.4.5, 2.4.6, and 2.4.7 lines, Adobe states that after MySQL 8.0 EOS it will not validate or maintain compatibility with MySQL versions released after 8.0 on those releases. Extended Adobe Commerce platform support, when available, does not extend support for third-party dependencies such as MySQL.
Cloud and on-premises are not the same case. Adobe’s system requirements matrix separates Commerce on Cloud from Commerce on-premises: service versions tested on hosted Cloud can differ from versions supported for self-managed installs.
Staying on Adobe Commerce / Magento 2.4.5 or 2.4.6 with MySQL 8.0 on-premises combines two risks: a database outside Oracle support and a platform line Adobe will not align to newer MySQL. Unpatched database CVEs, audit pressure (PCI and internal policy), and reactive incident cost start competing with the evolution budget.
On Cloud, risk shows up when services or the Adobe Commerce / Magento line fall outside what the lifecycle policy still covers. Even with MariaDB in the template, an outdated platform and dependencies remain P&L operational risk, not only an infra line item.
There is no single mandatory path. Order and scope depend on Cloud versus on-premises and on the real state of the install.
The useful next step is mapping real state: Adobe Commerce / Magento version, Cloud or on-premises, database engine and version, applied patches, PCI constraints, and recent reactive cost. That is what lets you choose database-only, platform-only, or both in one window.
Assessment here prioritizes risk and TCO. It does not presuppose architecture migration or a distribution switch. The free diagnostic and the Precision Assessment exist to turn “MySQL 8.0 is out of support” into a plan with P&L numbers.
Related questions
It is an AI-assisted multidimensional diagnostic that identifies margin leaks and technical debt in Adobe Commerce / Magento operations, delivered in 1 to 3 weeks.
The deliverable includes a map of invisible costs, prioritized interventions with financial impact, and a clear recommendation: migrate, optimize, or keep the current platform.
For migrations to modular architecture with observability, 25% to 50% reduction in infrastructure TCO over 12 months is a realistic target for mid-size operations.
The exact percentage depends on the starting point: operations with high reactive legacy costs tend toward the upper range; each case is quantified in the diagnostic.
Next steps
