Joomla maintenance depends on the core version, extensions, template and the functions the business uses. Build an update plan from that inventory, then check compatibility, recovery and the result. This page covers ongoing care rather than repeating the hosting offer.
Review core, extensions and template together, agree the supported work and check the site after the change.
- Site inventory
- Compatible changes
- Functional checks
Record the current site before choosing a path
- Joomla version, PHP/database environment and the intended target version.
- Extensions, templates, customisations, vendor support and update subscriptions.
- Menus, permissions, multilingual content, forms and any integrations used by the site.
- The recovery point, test destination and person who can approve the change.
Use checks as part of the review
Joomla's official version-update guide describes compatibility and backup checks and reviewing the site after an update. Check availability and guidance for the installed and target versions; a tool's compatibility result does not replace checking a custom extension with its vendor.
An update workflow with an owner
- Confirm the supported path. Review the core, extension and runtime requirements for this site.
- Resolve blockers. Identify lapsed licences, unsupported components and customisations needing developer work.
- Agree the recovery route. Confirm the files and database covered and any new data that could be affected by a restore.
- Test the intended change. Use an appropriate staging copy and authorised test activity before publication where required.
- Validate and document. Review public pages, menus, media, forms, permissions and the site-specific functions, then record the versions and remaining actions.
A major-version migration can be a project
A replacement template, incompatible extension or custom integration can make the work larger than routine patching. Agree redevelopment, content migration and acceptance testing separately. No blanket Joomla-version support commitment is made here; compatibility is assessed before service is confirmed.
Know the care boundary
Supported Joomla core and extension update care is part of the published hosting offer under the agreed scope. Vendor licences, unsupported software and additional troubleshooting can require a separate decision or quote. See the care coverage guide.
Joomla maintenance questions
Are all extensions covered automatically?
Support, compatibility and licence access need review. Custom or discontinued extensions may need separately scoped work.
Will changing the PHP version also update Joomla?
The runtime and application are separate parts of the change. Confirm their compatibility and the intended sequence for the specific site.
Can an old Joomla site move straight onto a current plan?
Start with an assessment. An unsupported version or dependency can require an upgrade or migration project before the hosting arrangement is confirmed.
Related Joomla guidance
- Managed Joomla hosting
- Website migration process
- Backup and recovery planning
- Joomla security and patching
Review your Joomla maintenance coverage
Tell us the public site URL, platform and the work you need. We will confirm the scope and responsibilities before quoting.
Ask about your site