Content, users, extensions
Count articles, categories, users and extensions. Record what is actually used.
A migration is not a single update click. The version you start from, the extensions you depend on and the URLs you have earned all change the plan. Use this checklist to prepare before a developer touches the live site.
The checklist is a starting point. A fixed scope follows the audit and an extension review.
The version number is the start of the plan, not the plan itself.
| Version | Status | What it means for a move |
|---|---|---|
| Joomla 3 | End of life since 17 Aug 2023 | No official security patches. A migration is not a routine update; it needs a content and extension plan. |
| Joomla 4 | End of life since October 2025 | Unsupported. Plan a move to Joomla 5 or 6 and test the template and extensions. |
| Joomla 5 | Security fixes until 12 Oct 2027 | Supported with security fixes only. Plan the move to 6 before that window closes. |
| Joomla 6 | Current major release | The target for a planned build, with extension compatibility checked first. |
Work through these in order; skipping one usually shows up later as a surprise.
Count articles, categories, users and extensions. Record what is actually used.
Take files and database backups and prove they restore before touching staging.
Build the new site away from the live site with a copy of the real content.
Replace abandoned extensions, test the rest and document what changed.
Record important URLs and plan 301s where the structure changes.
Check forms, search, mobile, users and redirects, then monitor after cutover.
“They are very knowledgeable about Joomla!® and were very helpful throughout the project, even though we were not 100% sure about what we wanted to do.”
Before you start the move.
Joomla 6 is the current major release. Joomla 5 receives security fixes until 12 October 2027. Joomla 3 and 4 are end of life.
Not as a simple one-click update. Joomla 3 to 4 was a migration, and a sensible path to 6 needs a content, extension and template plan.
Files, the database, custom templates and any extension configuration. Test that the restore works before changing the live site.
Check the extension developer’s current documentation, then test on a staging copy with your actual template and content—not on the live site.
Pick the next question that matches your situation.
Run the audit, collect the content and extension inventory, then ask us to confirm the scope and timeline.