Percona Server 8.0 EOL to 8.4 LTS — when and how should I migrate?
Plan whether to move directly to Percona 8.4 LTS, switch vendors, or buy time with commercial support now that 8.0 reached end of life.
Blockers
- runtime/percona-server-mysql-8-0 — EOL 2026-04-01
- Percona recommends 8.4.4 or later if you use spatial indexes; 8.4.0 through 8.4.3 can corrupt R-Tree indexes.
Who this is for
- enterprise
- compliance
- cost-sensitive
Candidates
Upgrade directly to Percona Server for MySQL 8.4 LTS
As of 2026-04-04, Percona Server for MySQL 8.0 has already reached end of life in Percona's lifecycle matrix on 2026-04-01. Percona documents a supported direct upgrade path from 8.0.x to 8.4.x LTS using in-place upgrade, logical dump and load, or replication. Percona also states it will not ship MySQL Innovation releases 9.0 through 9.6, so 8.4 is the main supported landing zone.
When to choose
Best for enterprise or compliance-sensitive teams that want the least disruptive path and can execute one focused upgrade now. The decisive factor is that Percona explicitly supports 8.0.x to 8.4.x LTS, while its published roadmap skips MySQL 9.0 through 9.6 Innovation releases.
Tradeoffs
Keeps tooling and operational practices closest to an existing Percona 8.0 estate and avoids an immediate vendor move, but it still requires application, client-driver, and automation cleanup for 8.4 behavioral changes.
Cautions
Do not target early 8.4 point releases if you use spatial indexes; Percona's upgrade guidance says 8.4.0 through 8.4.3 can corrupt R-Tree indexes and recommends 8.4.4 or later. Audit client compatibility for `caching_sha2_password`, and update any scripts that still use `CHANGE MASTER TO`, `START SLAVE`, `STOP SLAVE`, or `SHOW SLAVE STATUS`.
Buy Percona post-EOL support for 8.0 and delay the upgrade
As of 2026-04-04, this is a post-deadline option because Percona Server for MySQL 8.0 community lifecycle ended on 2026-04-01. Percona's MySQL 8.0 EOL page says it offers paid post-EOL support for up to three years after official end of life, including CVE fixes, bug fixes, 24x7x365 support, and SLAs as fast as 15 minutes for critical issues. This is the clearest official way to buy time without moving to Oracle's Innovation/LTS cadence immediately. Public pricing is not stated in the referenced official materials, so check official docs or sales for quote details.
When to choose
Best for teams with hard change freezes, regulated environments, or large estates that cannot complete validation immediately. The decisive factor is whether paying for a bounded extension is safer and cheaper than compressing an 8.4 migration into an already-missed deadline.
Tradeoffs
Reduces immediate operational risk and gives a controlled runway, but it extends dependence on an already-ended 8.0 branch and does not remove the eventual migration work.
Cautions
Treat this as a time-buying measure, not a destination. As of 2026-04-04, the community EOL has already occurred, so staying on 8.0 without a commercial support contract leaves you outside the normal patch stream.
Switch vendor to Oracle MySQL 8.4 LTS
As of 2026-04-04, MySQL 8.4 is Oracle's current LTS line. Oracle documents LTS support under its Lifetime Support Policy and says upgrades should follow LTS-to-LTS sequencing rather than skipping an LTS series.
When to choose
Best for organizations that want Oracle's own LTS and support model and are willing to standardize on Oracle packaging and repository management. The decisive factor is governance preference for Oracle's LTS lifecycle over Percona's open-source distribution plus services approach.
Tradeoffs
Gets you onto Oracle's published LTS cadence and support policy, but the core 8.4 migration blockers still remain because they come from upstream MySQL 8.4 behavior, not from Percona packaging alone.
Cautions
Future planning should assume LTS-to-LTS sequencing. Oracle's 8.4 documentation says 8.4.x LTS can upgrade to 9.7.x LTS, but cannot skip that LTS to jump directly to a later LTS series.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Percona Server 8.0 EOL to 8.4 LTS — when and how should I migrate?"