How to Upgrade from Joomla 5 to Joomla 6
Upgrade a production Joomla 5 site to Joomla 6 only after the Joomla 5.4 preparation and staging rehearsal are complete. The production job should follow the same tested sequence: freeze unrelated changes, take a fresh recovery backup, pass Joomla's required pre-update checks, run the Joomla Update component, and verify the whole application before ending the maintenance window.
Confirm Joomla 5.4 is ready for the major upgrade
Before touching production, confirm the site is on the prepared Joomla 5.4 state and that the target server meets Joomla 6 requirements. As of October 2026, Joomla 6.x lists PHP 8.3.0 as supported/minimum and PHP 8.4 as recommended. Verify third-party extension, template, and custom-code compatibility against the versions actually installed.
In Joomla 5.4, the Joomla 5 Behaviour - Backward Compatibility plugin must be disabled and Behaviour - Backward Compatibility 6 must be installed and enabled for Live Update to Joomla 6. If the site cannot operate on 5.4 with the old compatibility plugin disabled, stop and fix that problem first.
Create the production rollback point
- Schedule the maintenance window and pause content/deployment changes that would complicate rollback.
- Take a fresh backup of both Joomla files and the database.
- Store the backup somewhere that will survive a site/filesystem failure.
- Confirm the restore procedure and credentials are available.
- Record the starting Joomla, PHP, database, template, and critical extension versions.
Do not plan to “downgrade” Joomla by copying old core files back. Joomla's backward-compatibility policy does not support downgrading after an upgrade; restoration of the complete pre-upgrade state is the recovery plan.
Review the Joomla 6 target and start the update
- Go to System → Update → Joomla.
- Confirm the offered target is the Joomla 6 release you tested on staging.
- Review the Pre-Update Check and resolve required server/settings failures.
- Review potentially incompatible extensions and verify uncertain products with their developers and your staging results.
- Confirm the backup when Joomla asks and start the update.
- Leave the update process alone while Joomla downloads, extracts, updates the database, removes obsolete files, and finalizes.
If Joomla reports an error, preserve the exact message and timestamps before retrying. An interrupted major update can be partial, so repeated clicks are not a recovery strategy.
Verify Joomla core before testing the application
After the update completes, sign back into Administrator and confirm the installed Joomla version. Open System → Maintenance → Database and investigate any core schema warning. Clear relevant Joomla/external caches and review PHP and web-server logs for new errors.
If the site does not return cleanly, compare the failure with the staging rehearsal. If you cannot establish that core files and the database are in a consistent state, use the proven pre-upgrade restore rather than improvising a downgrade.
Test the complete Joomla 6 site before reopening normally
Run the same acceptance checklist used on staging: frontend routes, Administrator editing, authentication, users/permissions, menus/modules, template overrides, forms, search, email, scheduled tasks, command-line jobs, APIs, payments, memberships/ecommerce, backups, and security tooling. Test both anonymous and logged-in experiences where relevant.
Check background jobs after enough time has passed for them to run, and confirm CLI jobs use a Joomla 6-compatible PHP binary. Keep the pre-upgrade backup until production has passed functional checks and logs show no new critical errors.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.