Adobe Commerce Is Moving from MySQL to MariaDB
Adobe Commerce Technology Update Adobe Commerce Is Moving from MySQL to MariaDB Adobe Commerce has established MariaDB as its default and recommended database direction. This practical guide explains what the transition means, which Commerce versions are affected and how merchants can migrate without turning a planned infrastructure change into a production incident. By Hikmadh Commerce Team Adobe Commerce Database Migration Guide Approximately 12-minute read Adobe Commerce database direction MySQL Final certified path MariaDB Default direction The database change should be treated as a planned application and infrastructure project—not as a simple production server swap. 2.4.8 Final MySQL generation begins MySQL 8.4 remains available, but MariaDB planning should begin. 2.4.9 Last Commerce version supporting MySQL Future releases are expected to progress with MariaDB. 8.4 Final supported MySQL version Adobe does not plan to certify later MySQL releases. 30 Apr 2026 MySQL 8.0 support milestone Affected earlier Commerce releases need a supported database path. What changed Version impact Why MariaDB Compatibility risks Migration plan Testing checklist Business planning Final perspective Adobe Commerce is entering a new database chapter. For many years, merchants and implementation partners treated MySQL and MariaDB as two closely related options within the Magento ecosystem. That position has now changed. MariaDB is no longer simply an alternative that happens to appear in the compatibility matrix. It is becoming the database platform around which future Adobe Commerce releases are being planned. The change was not accompanied by a large product keynote or a major marketing campaign. Adobe communicated the direction through its support guidance and system requirements documentation. That quiet delivery can make the change appear less urgent than it is. In practice, database support affects application upgrades, security planning, hosting architecture, extension compatibility, performance testing and the ability to receive effective vendor support. Merchants do not need to panic or immediately replace a stable production database. They do need to understand their current position. A business running Adobe Commerce 2.4.6 with MySQL 8.0 has a different level of urgency from a business already operating 2.4.8 with MariaDB 11.4. Migration decisions should therefore begin with accurate discovery, not assumptions. The key takeaway Know your Adobe Commerce version, confirm the real database engine running underneath it and place MariaDB migration on the roadmap before support limitations force the decision during an incident. What exactly has Adobe Commerce changed? Adobe’s support guidance establishes a clear end point for MySQL within the Adobe Commerce product line. Adobe Commerce 2.4.8 and 2.4.9 are identified as the final Commerce versions that support MySQL. Within those versions, MySQL 8.4 is the final MySQL release Adobe plans to certify. Versions released after MySQL 8.4 are not expected to receive Adobe Commerce certification or support. For earlier Commerce versions, MySQL 8.0 reached the relevant Adobe support milestone on April 30, 2026. Adobe does not intend to validate a newer MySQL major version for the 2.4.5, 2.4.6 and 2.4.7 release lines. On-premises merchants using those versions are therefore advised to move to a MariaDB version compatible with their exact Commerce release and patch. This does not mean every store on an older Commerce release became completely unsupported on the same day. Adobe Commerce application lifecycle support and third-party database dependency support are related but separate. A Commerce release may remain within an Adobe support period while its MySQL dependency no longer meets the required supported configuration. Why this distinction matters When a production issue reaches Adobe Support, the environment may need to be aligned with Adobe’s tested dependency matrix before the issue can be investigated or validated. Remaining on an unsupported database combination can therefore increase operational risk even when the Commerce application itself is still within a support programme. What the database change means for each Commerce version The correct action depends on the exact Commerce release, patch level, deployment model and current database version. Commerce environment Current position Recommended planning response 2.4.5–2.4.7 with MySQL 8.0 Adobe will not certify a newer MySQL major version for these Commerce release lines. MySQL 8.0 is no longer the long-term supported dependency path. Identify the MariaDB release supported by the exact Commerce patch, test the application and schedule a controlled migration. 2.4.8 with MySQL 8.4 The configuration can remain supported, but MySQL 8.4 is the final MySQL destination in the Adobe Commerce roadmap. Use the available runway to complete discovery, extension testing and MariaDB migration planning before the next major Commerce upgrade. 2.4.8 with MariaDB The store is already operating in the database direction Adobe is carrying forward. Confirm the database release against the latest patch matrix, maintain backups and include database upgrades in normal platform lifecycle planning. 2.4.9 on premises MySQL 8.4 may still appear as a supported option, but MariaDB is the recommended long-term platform. Prefer MariaDB for new infrastructure and avoid building a new long-term platform around the final MySQL release. 2.4.9 on Cloud Current Cloud requirements have already moved towards MariaDB without presenting MySQL as the database destination. Coordinate the required database service version with Adobe Cloud Support and follow the Cloud upgrade procedure. Adobe’s requirements continue to change as new Commerce patches and database releases become available. At the time of writing, the requirements for Adobe Commerce 2.4.9 recommend a newer MariaDB release than the versions commonly used by 2.4.7 or 2.4.8 environments. This is why a team should never choose a destination database version from a generic MariaDB download page alone. The authoritative destination is the MariaDB version listed for the exact Commerce version and patch being deployed. Teams should check the matrix during initial planning and check it again immediately before staging and production implementation. Why is the ecosystem moving towards MariaDB? Adobe has documented the technical direction but has not published a detailed commercial explanation covering every reason behind it. It is reasonable for the community to discuss Oracle ownership, licensing models, enterprise support terms and the independent governance of MariaDB. However, these points should not be presented as Adobe’s confirmed motivation unless Adobe explicitly states them. The observable technical direction is