Migrating from MySQL 5.7 to 8.0: Steps, New Features, and Alternative Paths

According to DB‑Engines, MySQL remains the world’s most popular open‑source database, but MySQL 5.7 will enter end‑of‑life in October 2023, meaning no further updates or security patches. Over half of surveyed MySQL users are still on 5.7, leaving many installations only months from unsupported status.

Why Upgrade to MySQL 8.0

MySQL 8.0, released in 2016, is now the only supported MySQL version. It introduces major SQL enhancements such as lateral‑derived joins, common table expressions (CTEs), and an INTERSECT clause, making complex queries easier to write and maintain.

New commands include EXPLAIN ANALYZE for detailed query performance data and INVISIBLE INDEX for safe index testing without risking destructive rebuilds. The default character set has also switched to UTF8MB4, providing full Unicode 9.0 support for international applications.

Upgrade Process and Validation

The migration is one‑way; you must verify that your applications and schemas can handle the changes. MySQL Shell’s util.checkForServerUpgrade() runs 21 tests to detect issues such as reserved keyword conflicts, non‑native partition engines, circular directory references, and deprecated system variables.

Depending on the test results, you may need only minor adjustments or a more extensive code refactor before the upgrade can proceed safely.

Alternative Strategies

Beyond a direct upgrade, consider three broader options:

Do nothing : Continue running MySQL 5.7 despite lack of support, accepting the security and compliance risks. Some organizations choose this when the application is isolated from the internet and a future upgrade is planned.

Move to a DBaaS : Use a cloud‑managed MySQL service to offload infrastructure maintenance while still staying on the MySQL platform.

Switch to another database : Evaluate alternatives such as PostgreSQL, which now supports the MERGE command (added in PostgreSQL 15) and offers a large open‑source ecosystem. Migration may require some SQL rewriting, but if you are already updating to MySQL 8.0, a full switch can be worthwhile.

Choosing PostgreSQL

PostgreSQL is the most common external option, with strong community support and commercial/DBaaS offerings. Its recent MERGE support reduces the amount of code change needed compared to older PostgreSQL versions. However, verify compatibility with the specific PostgreSQL distribution you select.

Conclusion

Upgrading from MySQL 5.7 to 8.0—or adopting a DBaaS or PostgreSQL—will be a priority for many developers and DBAs in the coming months. By assessing your current workload, testing with util.checkForServerUpgrade(), and weighing the cost‑benefit of each path, you can plan a smooth transition and avoid the pitfalls of running an unsupported database.