Applies to Joomla 6.x → 7.0 · site owners and the people who run the upgrade Updated 16 Oct 2026

This is the checklist we'll use for Joomla 7 upgrades. It's the same process that worked for 5 → 6 on our own site and client sites, adjusted for what the 7.0-dev branch already shows. Most of it happens months before the upgrade, on Joomla 6. The upgrade day itself should be boring.

Phase 1: on Joomla 6, months before

  • Get to the latest 6.x and stay current. Every 6.x release fixes things in a backward-compatible way, and the last 6.x is the version Joomla 7's upgrade is tested from.
  • Inventory the extensions, with version, vendor and last release date:
    # terminal
    php cli/joomla.php extension:list --type=component
    php cli/joomla.php extension:list --type=plugin
    # core extensions are listed too: System → Manage → Extensions, filtered by author, shows only third-party ones
  • Ask each vendor about Joomla 7. Write the answers down. "No plan" means "find a replacement", and replacing an extension takes longer than upgrading Joomla.
  • Collect the deprecation log on a staging copy: Global Configuration → Logging → Log Deprecated API, then use the site. administrator/logs/deprecated.php lists every call that Joomla 7 is set to remove, with the file responsible.
  • Switch the compat plugin's "Classes Aliases" off on staging and click through. Whatever breaks needs fixing before Joomla 7, where the compat plugin starts disabled.
  • Fix custom code and the template using the log. The fixes run on Joomla 6 too, so deploy them to live as normal updates, one at a time. See Joomla 7 breaking changes.
  • Deal with old password hashes: count the accounts still on MD5/PHPass and decide whether to delete them or to email them a reset link before the upgrade.

Phase 2: when Joomla 7 and your extensions are ready

  • Wait for the first bug-fix release (7.0.1 or 7.0.2) unless you have a reason not to. On a business site, "first" has no value of its own.
  • Check that every extension has a Joomla 7 release, and update them on Joomla 6 first if the vendor ships versions that run on both.
  • Make a fresh staging copy from live, with outgoing mail caught and payment plugins in test mode.
  • Back up live, and restore that backup somewhere once. Then you know it works.

Phase 3: the upgrade, on staging first

# terminal – on the staging copy
php cli/joomla.php core:update:check
php cli/joomla.php core:update                 # latest 6.x first
php cli/joomla.php core:update:channel next    # offer the next major version
php cli/joomla.php core:update                 # → 7.0.x
php cli/joomla.php update:joomla:remove-old-files
php cli/joomla.php maintenance:database        # every table must be up to date
php cli/joomla.php cache:clean

Two lessons from the 5 → 6 upgrade apply here as well:

  • If the CLI crashes before the update starts, an enabled plugin that uses removed classes is crashing the console application. Disable it for the upgrade and enable it afterwards (with its Joomla 7 version installed).
  • "Files updated" is not "upgrade finished". The database maintenance report is. If finalisation fails, run it again with the new code before you test anything.

Phase 4: test like a visitor, then like an editor

TestPass when
Every page type (home, category, article, contact, search, login, 404, each component)renders, no PHP errors in the server log
Forms: contact, registration, password reset, any extension formssubmit, and the mail arrives in the catcher
Shop / donations / bookingsa full test transaction in sandbox mode
Editors' work: create, edit, publish, upload an image, restore a versionworks for a normal editor account, not just a Super User
Plugins that act on events (SEO, redirects, notifications)they still do their job; legacy plugins fail silently
Scheduled tasks and cronscheduler:list shows them, and each one ran successfully once
URLsthe old sitemap's URLs all return 200 or a deliberate 301
Logsdeprecated.php and the PHP error log are quiet

The fifth row is the one people skip. A legacy plugin doesn't throw an error on Joomla 7, it just isn't called. Check the result of each plugin (the redirect happens, the email is sent, the meta tag is there), not the absence of errors.

Phase 5: live

  1. Pick a quiet time. Freeze content edits for the duration.
  2. Back up live again (files and database).
  3. Run the same commands as on staging, or deploy the upgraded staging copy with live's configuration values.
  4. Clear Joomla's cache and the CDN.
  5. Repeat the visitor tests from phase 4 on live, and watch the PHP error log for an hour.
  6. Keep the pre-upgrade backup for at least a month.

Leave the compat plugin off

If something fails after the upgrade, enabling Backward Compatibility 7 may bring it back, and that's fine as a stop-gap. Note which extension needed it, and get it fixed or replaced. What it carries is already on the next removal list (parts of it are tagged "removed with 8.0"), so a site that depends on it is deferring the same problem to the next major version.