MySQL 8.0 End of Life to 8.4 LTS Before April — when and how should I migrate?

MySQL teams need a decision card for whether to move from 8.0 to 8.4 LTS or to an Innovation release before MySQL 8.0 reaches end of life in April 2026, including support-window and operational-risk implications.

Move to MySQL 8.4 LTS by default unless you can keep upgrading on the 9.x Innovation track without pauses.

Blockers

Who this is for

Candidates

Move from MySQL 8.0 to MySQL 8.4 LTS as the default landing zone

As of 2026-03-15, MySQL 8.4 is the safest default target for most MySQL 8.0 estates. Oracle's support chart lists MySQL Database 8.0 Extended Support ending in April 2026, while MySQL Database 8.4 has Premier Support through April 2029 and Extended Support through April 2032, and the MySQL release model defines LTS as the stable track with only necessary fixes and no removals within the LTS series.

When to choose

Best for enterprise + compliance, low-ops + small-team, or high-scale + real-time fleets where you need a supported version before April 2026 but want the lowest behavior-change risk. Choose this when quarterly feature churn is a liability, when rollback flexibility matters, or when you need one major upgrade that buys a long support runway.

Tradeoffs

You get the longest clearly documented support window available from the current 8.0 decision point and a direct supported 8.0.x to 8.4.x upgrade path using in-place upgrade, logical dump and load, or replication. The tradeoff is that you delay 9.x features and still need to remediate 8.4 compatibility changes before cutover.

Cautions

Do not treat 8.4 as a no-op patch train. Oracle documents that `mysql_native_password` is disabled by default in 8.4, `default_authentication_plugin` is removed, several SSL and keyring-related options and variables were removed in 8.4.0, multiple InnoDB defaults changed, some identifiers can become illegal because of reserved-word changes, and upgrades to 8.4.4 or later should drop and recreate spatial indexes. Oracle also recommends running MySQL Shell's Upgrade Checker Utility before the upgrade.

Sources

Adopt the MySQL Innovation track only if you can keep upgrading after first landing on 8.4

As of 2026-03-15, MySQL 9.6 is actively supported for production use and is the current Innovation series documented by Oracle. The official MySQL release model says Innovation releases are supported only until the next major or minor release, so this path is for teams that deliberately accept a shorter support window in exchange for the newest features and fixes.

When to choose

Best for high-scale + microservices, real-time + enterprise, or monorepo-like application teams with strong CI, upgrade rehearsal, and connector validation where getting the newest server behavior matters more than long support runway. Choose this only when you can first move off 8.0 to 8.4 and then stay current on the 9.x Innovation track without long upgrade freezes.

Tradeoffs

You get the newest MySQL capabilities sooner and stay on the branch Oracle presents as the current production-ready Innovation release. The tradeoff is more operational churn, a shorter documented support horizon for each release, and a need for repeated upgrade work rather than one conservative LTS move.

Cautions

Oracle's release model explicitly says behavior changes are expected in Innovation releases, and the official downgrade matrix says downgrades within an Innovation series such as 9.6 to 9.5 are only supported for rollback purposes using logical dump and load or replication if no new server functionality has been applied to the data. Oracle also documents that `mysql_native_password` is removed as of MySQL 9.0.0, so any temporary dependency you tolerate on 8.4 must be removed before moving onto 9.x. For 8.0 estates, do not plan a direct jump to 9.x after the LTS boundary; Oracle's documented model requires first moving to 8.4.

Sources

Facts updated: 2026-03-15
Published: 2026-04-03

Related questions

Try with your AI agent

$ npm install -g pocketlantern
$ pocketlantern init
# Restart Claude Code, Cursor, or your MCP client, then ask:
# "MySQL 8.0 End of Life to 8.4 LTS Before April — when and how should I migrate?"
Missing something? Request coverage