How to Prepare a Joomla 5 Site for Joomla 6

A Joomla 5 to Joomla 6 upgrade should begin as a compatibility project, not with the Update button. Prepare the site on Joomla 5.4, prove that the server and third-party software meet Joomla 6 requirements, resolve compatibility-plugin checks, and rehearse the complete upgrade on staging. The goal is to make the production upgrade repeat a process you have already proven.

Bring the site to a clean Joomla 5.4 starting point

  1. Update Joomla 5 through its supported update path until the site is on the current Joomla 5.4 release you intend to use as the migration starting point.
  2. Install supported updates for extensions, templates, languages, and packages.
  3. Resolve existing PHP errors, failed extension updates, database warnings, and broken update sites before introducing a major-version change.
  4. Remove software you no longer need only through its supported uninstall process and only after confirming that its data and dependencies are no longer required.

Do not combine unrelated cleanup, hosting migration, redesign work, and the Joomla 6 upgrade in one uncontrolled change. A stable starting point makes failures much easier to isolate.

Verify the Joomla 6 environment and extension inventory

Joomla's current 6.x technical requirements list PHP 8.3.0 as the supported minimum and PHP 8.4 as recommended. Check the current Joomla requirements for the database engine, web server, PHP modules, and memory as well. Confirm the actual web PHP runtime; command-line PHP can be different.

Then inventory every third-party component, module, plugin, template, package, library, template override, and custom integration. Check each developer's Joomla 6 and PHP support for the exact version you plan to run. Joomla's Pre-Update Check uses information supplied through extension/update metadata; missing or favorable metadata is not a substitute for vendor confirmation and real testing.

Set the Joomla 5.4 compatibility plugins correctly

For the Joomla 5.4 to 6.x transition, Joomla requires Behaviour - Backward Compatibility (the Joomla 5 compatibility plugin) to be disabled and Behaviour - Backward Compatibility 6 to be installed and enabled. Joomla's Pre-Update Check treats these as required settings for Live Update.

  1. Confirm Behaviour - Backward Compatibility 6 exists and is enabled.
  2. Disable the Joomla 5 Behaviour - Backward Compatibility plugin.
  3. Test Administrator and the frontend while still on Joomla 5.4.
  4. If the site breaks, re-enable the Joomla 5 plugin and identify the extension or custom code still depending on it.
  5. Resolve that incompatibility before attempting Joomla 6.

Do not disable unrelated Behaviour plugins such as Taggable or Versionable just because their group name is similar.

Run the Pre-Update Check and prove the rollback

Open System → Update → Joomla and review the target Joomla 6 release, required settings, server requirements, and extension compatibility information. Treat red required checks as stop conditions and investigate uncertain extension results rather than clicking through them.

Create a complete backup of the files and database and perform a test restoration. Joomla does not support downgrading after an upgrade; if a major upgrade must be reversed, the safe recovery path is restoration of the matching pre-upgrade backup. Know where that backup is stored and how long restoration takes before scheduling production.

Rehearse the exact production upgrade on staging

Clone a recent production state to isolated staging and reproduce the planned PHP/database environment. Prevent staging from sending real customer email, processing live payments/webhooks, being indexed, or running production scheduled jobs.

Perform the Joomla 5.4 to 6 upgrade using the same method and sequence planned for production. Then test Administrator, frontend, authentication, editing, menus, modules, templates and overrides, forms, search, email, scheduled tasks, CLI jobs, APIs, payments, memberships, and other critical workflows. Review PHP/server logs even when pages look normal. Production is ready only when the staging rehearsal is repeatable and its unresolved risks are understood.


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.

Open a Support Ticket