Ryz Labs/Migrations/MySQL 8.0 end of life
Migrations

MySQL 8.0 End of Life: Upgrade Plan for MySQL 8.4 LTS

MySQL 8.0 left Oracle Extended Support in April 2026. Find your servers, clear the upgrade checker, and move replicas first onto MySQL 8.4 LTS.

Short answer: MySQL 8.0 left Oracle Extended Support in April 2026 and moved to Sustaining Support, so do not count on new security fixes. Upgrade to MySQL 8.4 LTS, supported until April 2032; 8.4 cannot be skipped.

VersionEnd of lifeStatus on November 21, 2026
MySQL 8.0April 2026Past end of life
MySQL 8.4April 2032Supported

Oracle Extended Support for MySQL 8.0 ended in April 2026, and the MySQL end-of-life notice states that "as of April 21, 2026, MySQL 8.0 is covered under Oracle Sustaining Support." In practice, 8.0 has left the period in which Oracle shipped new 8.0 binaries, so do not plan around further security fixes for it. Upgrade to MySQL 8.4 LTS, which Oracle's Lifetime Support Policy covers with Extended Support until April 2032, by clearing the MySQL Shell upgrade checker and then upgrading replicas before the source.

Key dates

VersionReleasedEnd of lifeStatus on November 21, 2026
MySQL 8.0April 2018 (GA)Premier ended April 2025; Extended ended April 2026Sustaining Support only
MySQL 8.4 LTSApril 2024 (GA)Premier to April 2029; Extended to April 2032Premier Support, recommended target
MySQL 9.7 LTSApril 2026 (GA)Premier to April 2031; Extended to April 2034Premier Support, next LTS after 8.4

Dates from the official calendar, checked November 21, 2026. Oracle publishes them by month only, in its Lifetime Support Policy for Technology Products (effective November 13, 2026). The only day-level date is the April 21, 2026 Sustaining Support statement on the mysql.com notice, which also advises moving to 8.4 LTS or 9.7 LTS. The MySQL manual describes the LTS model as "5 years of premier support and 3 years of extended support." We list only the LTS series here; short-lived Innovation releases are not a sensible landing spot for a production estate leaving 8.0.

Why 8.4 and not 9.7? The official upgrade paths are blunt: "A bugfix or LTS series cannot be skipped." From 8.0 the only supported LTS hop is to 8.4. You can continue to 9.7 later, but 8.4 is the mandatory first stop, and its window to April 2032 is long enough that many teams will stay there for years.

What end of life means for your systems

Your 8.0 servers keep accepting connections and committing transactions. What is gone is the steady flow of 8.0 maintenance releases that closed security bugs and crashes. Oracle's notice had said 8.0 binaries would be provided "until EOL in April 2026," and Sustaining Support is the phase that follows Extended Support in Oracle's lifecycle table. Plan as if every vulnerability disclosed from now on stays unfixed on 8.0.

Managed database services set their own MySQL timelines, and some sell paid extended support for older engine versions. Those terms vary and change. Check your provider's documentation for current dates and prices; this page deliberately quotes none of them.

Find your exposure

The primary is easy to find. The forgotten copies are the problem: a read replica feeding a BI tool, a staging server restored from a snapshot, a mysql:8.0 container in a docker-compose file every developer runs, and the backup host whose client binaries define what your dumps look like.

For the repository side, drop a Dockerfile or compose file into the EOL deadline radar. The free tool reads the pinned versions and gives back each one with its official support cutoff.

What changes in the upgrade

The MySQL 8.4 manual's "What Is New in MySQL 8.4 since MySQL 8.0" section lists the removals and changed defaults. These are the ones that tend to break an 8.0 estate.

mysql_native_password is off by default

Starting with 8.4.0, the deprecated mysql_native_password plugin is no longer enabled by default. Accounts that still use it, and older client libraries that only speak it, will fail to authenticate. The manual allows turning it back on with mysql_native_password=ON in the [mysqld] section or --mysql-native-password=ON, but treat that as a temporary bridge while you move those accounts to a supported plugin and update drivers. The default_authentication_plugin variable is also gone; use authentication_policy instead.

MASTER and SLAVE statements are removed

CHANGE MASTER TO becomes CHANGE REPLICATION SOURCE TO, SHOW MASTER STATUS becomes SHOW BINARY LOG STATUS, RESET MASTER becomes RESET BINARY LOGS AND GTIDS, and START SLAVE, STOP SLAVE, SHOW SLAVE STATUS and RESET SLAVE become their REPLICA forms. MASTER_HOST, MASTER_LOG_POS and related options are now SOURCE_HOST, SOURCE_LOG_POS and so on. Failover scripts, orchestration tools, monitoring checks and runbooks written against the old words will error out on 8.4.

AUTO_INCREMENT on FLOAT and DOUBLE must be fixed first

Support for AUTO_INCREMENT on FLOAT or DOUBLE columns is removed entirely in 8.4. The manual is explicit that you must fix those tables before upgrading, otherwise the upgrade fails. Find them in information_schema.columns and convert them to an integer type during the compatibility phase.

Foreign keys on non-unique keys are rejected

The new restrict_fk_on_non_standard_key variable is ON by default, so creating a foreign key that references a non-unique or partial key now fails with ER_WARN_DEPRECATED_NON_STANDARD_KEY. Existing schemas may carry such keys from years of ad hoc migrations; your migration tooling will hit the error the next time it recreates one. Fix the referenced keys rather than switching the variable off permanently.

Removed variables, statements and tools

FLUSH HOSTS is gone (use TRUNCATE TABLE performance_schema.host_cache or mysqladmin flush-hosts), as are --skip-host-cache, expire_logs_days (use binlog_expire_logs_seconds) and binlog_transaction_dependency_tracking, because the source now always uses writesets. The mysql_upgrade, mysqlpump and mysql_ssl_rsa_setup programs are removed, along with the --ssl option, have_ssl, the SET_USER_ID privilege, and the keyring_file and keyring_encrypted_file plugins. The manual says starting mysqld with --expire-logs-days now results in an error, so diff every my.cnf against the removal list before cutover.

New reserved words

MANUAL, PARALLEL, QUALIFY and TABLESAMPLE are now reserved. A table or column with one of those names, used unquoted in application SQL, will produce syntax errors. The upgrade checker's reservedKeywords check finds them.

InnoDB defaults moved

Several InnoDB defaults changed between 8.0 and 8.4: innodb_adaptive_hash_index went from ON to OFF, innodb_change_buffering from all to none, innodb_io_capacity from 200 to 10000, innodb_log_buffer_size from 16 MiB to 64 MiB, and on Linux innodb_flush_method now prefers O_DIRECT. If you never set these explicitly, query plans and I/O patterns can shift after the upgrade. Decide deliberately: pin the old values for the first cut, or benchmark the new defaults under production-like load.

The upgrade plan

MySQL gives you three supported ways from 8.0 to 8.4: in-place upgrade, logical dump and load, and replication. MySQL Clone is not on the list for that path. A common pattern pairs in-place upgrades on replicas with a final switchover, which keeps the write interruption to the switchover itself.

Inventory and baseline

For every server, record version, role in the topology, data size, storage engine mix, character sets in use, authentication plugins per account (SELECT user, host, plugin FROM mysql.user;) and the client libraries that connect. Capture baseline query latency, replication lag and slow-log digests so you can compare after the move.

Compatibility testing

Run the MySQL Shell upgrade checker against each 8.0 instance: mysqlsh -- util checkForServerUpgrade user@host:3306 --target-version=8.4.0 --output-format=JSON --config-path=/etc/mysql/my.cnf. The account needs PROCESS and SELECT. Errors must be fixed before you upgrade; warnings are advisory. Checks such as reservedKeywords, utf8mb3, zeroDates, sysvar, removedFunctions and authMethodUsage map closely to the changes above. Then restore a recent backup onto an 8.4 test server and run the application's test suite and a replay of real queries against it.

Staged rollout

The replication upgrade guide says to upgrade all replicas before the source, working bottom-up from the replicas farthest from it, because an older source can feed a newer replica but not the reverse. For each replica: stop it, swap binaries, start mysqld (the server upgrades the data dictionary itself at startup under the default --upgrade=AUTO), and resume with START REPLICA. Point a slice of read traffic at an upgraded replica first and compare latency against the baseline.

Cutover and rollback

When every replica runs 8.4, switch writes over to one of them, then upgrade the old source as a standalone server and rejoin it. Plan the way back before you need it: the downgrade documentation supports 8.4 to 8.0 only through logical dump and load or replication, and only for rollback when no new server functionality has touched the data. In-place downgrade is not supported, so keeping an 8.0 replica attached for a defined period is the practical rollback.

Cleanup

Remove any temporary mysql_native_password=ON setting once every account has moved, retire the 8.0 replicas and images, update CI service containers to 8.4, and rewrite runbooks with SOURCE and REPLICA terms. Then decide when the later LTS hop to 9.7 belongs on your roadmap.

PhaseGoalKey techniqueExit criteria
Inventory and baselineEvery 8.0 server, account plugin and client knownVersion queries, mysql.user audit, slow-log digestsTopology diagram and baseline metrics signed off
Compatibility testingZero upgrade checker errorsutil checkForServerUpgrade, restore to an 8.4 test serverChecker clean, test suite and query replay green on 8.4
Staged rolloutAll replicas on 8.4Replicas first, bottom-up, read traffic sliceLag and latency within baseline on upgraded replicas
Cutover and rollbackWrites served by 8.4Switchover to an upgraded replica, 8.0 replica kept for rollbackSource upgraded and rejoined, rollback path tested
CleanupNo 8.0 left in any environmentConfig diff, image and CI updates, runbook rewriteNo 8.0 references in IaC, images or CI

Risk matrix

RiskLikelihoodImpactMitigationEarly warning
Apps or tools fail to log in after mysql_native_password is disabledHighHighMove accounts off the legacy plugin and update drivers before the upgradeauthMethodUsage findings in the checker
Failover or monitoring scripts use removed MASTER/SLAVE syntaxHighMediumGrep tooling and rewrite to SOURCE/REPLICA statementsSyntax errors on the first upgraded replica
Upgrade aborts on AUTO_INCREMENT FLOAT or DOUBLE columnsLowHighConvert those columns to integers before the binary swapinformation_schema query returns rows
mysqld will not start with a removed option in my.cnfMediumHighDiff config against the 8.4 removals, run the checker with --config-pathsysvar errors in checker output
Query performance shifts under new InnoDB defaultsMediumMediumPin old values first or benchmark with production-like loadSlow-log digest regressions on upgraded replicas
Reserved keyword collisions break queriesLowMediumRename or quote identifiers flagged by reservedKeywordsParser errors in the query replay
No clean way back to 8.0 after cutoverMediumHighKeep an 8.0 replica attached and avoid 8.4-only features until stableReplication errors on the 8.0 rollback replica

Typical team shape

This upgrade is database-heavy. It wants a senior MySQL specialist with replica-first upgrades and switchovers, an application developer who owns driver updates, authentication changes and query regression testing, and a platform engineer for images, configuration management and the failover tooling. Large or sharded estates often add another MySQL specialist, letting rehearsals on one cluster overlap with live cutovers on another. For hiring, see SQL developers or DevOps engineers, and DevOps consulting covers pipeline and infrastructure work.

Ryz engineers work on your team, reporting to your leads. Many teams begin with a pod of 3 to 5 senior engineers (a tech lead plus engineers), and a full pod is about seven. Once you say go, engineers can typically start in under two weeks. On budget: Ryz engineers on your team start from $7,000 per month (our published range is $7,000–$15,000 per engineer per month, mostly mid-level to senior), quoted per team. Tell us about your topology and scope your team.

Related

FAQ

Is MySQL 8.0 still safe to run after end of life?

It will keep serving queries, but under Sustaining Support you should not count on new 8.0 security fixes, so known issues pile up over time. Limit network exposure, tighten account privileges, keep scanning, and get the upgrade checker running against every instance so the move to 8.4 has a starting point.

Which version should we upgrade to?

MySQL 8.4 LTS. Oracle's support policy runs its Extended Support to April 2032, and the manual does not allow skipping an LTS series, so 8.4 is the required next stop from 8.0 even if 9.7 LTS is your eventual goal.

How long does the upgrade take?

The biggest factors are the number of servers and replication chains, total data size if you choose dump and load, how many accounts and drivers still rely on mysql_native_password, the amount of tooling written with MASTER and SLAVE syntax, and how much performance testing the new InnoDB defaults need. Replica-first upgrades keep write downtime to the switchover.

Can we pay for extended support?

Oracle's own lifecycle table ended Extended Support for 8.0 in April 2026 and lists only Sustaining Support after that. Cloud and managed database providers run separate programs with their own dates and fees. Read your provider's own terms and fees before counting on one.

What does it cost to bring in engineers?

Take the number of engineers, multiply by the months you need them, then by a monthly rate between $7,000 and $15,000 per engineer depending on seniority. We quote the team as a whole and you see the plan and the people before anyone starts.

Questions we didn't answer? Email info@ryzlabs.com.

Thanks — your message has been sent. We’ll get back to you soon.

Something went wrong while sending your message. Please try again or email info@ryzlabs.com.

Explore Ryz Labs

Software development servicesAI development companyIndustriesStaff augmentationAI pod teamsNearshore software developmentHire engineers by roleEngineer ratesGuidesBuyer guidesCase studiesHow we vet engineers

Ryz Labs

Senior engineers on your team. AI pod teams that ship.

Tell us what you're building. You get a scoped plan, a price and the names of the people who would do the work.

  • Only the top 1% of tens of thousands interviewed make it
  • On US business hours, including New York hours
  • Trusted by Fortune 500 engineering teams

Tell us who you need

A Ryz partner replies with a scoped team plan.

Start a conversation →

Prefer to talk? Book a 15-min call →