Staged first
Upgrades and extension changes are applied to a copy and checked, never to a live site that people depend on.
Keeping a Joomla site healthy — or moving it off, honestly.
Joomla still runs a great many established sites, and most of my Joomla work is one of two things: looking after one that works, or planning the move off one that no longer does.
Joomla sits between WordPress and Drupal: more structure than the first, less complexity than the second. Two things it has always done well out of the box are multilingual content and granular access control – both of which need plugins or custom work on WordPress, and both of which are why a good number of Joomla sites were built in the first place.
Most of the sites I see now were built somewhere between 2012 and 2018 and have been left alone since. The usual state is an old major version, a handful of extensions whose developers have moved on, and a template that cannot be updated without breaking the design. None of that is a crisis, but it is a decision that keeps getting postponed.
The honest position is that Joomla has a smaller developer community than it did, which affects what a site costs to maintain over the next five years. That is a real consideration, not a reason to panic – a well-built site serving its purpose does not need replacing because a platform is less fashionable.
So the work divides into two. Keeping a site secure, current and extended where it is genuinely doing its job. Or planning a migration properly, with the content structure mapped rather than pasted, and every URL redirected – which is where most platform moves lose their search visibility.
Moving between major versions with extension compatibility checked first, on a staging copy.
Security support without the upgrade that breaks the site.
Custom templates and overrides built to your brand rather than a purchased theme adjusted.
A design that updates cleanly instead of being frozen by customisation.
Custom components, modules and plugins where nothing in the directory does the job.
Functionality that survives upgrades, rather than core hacks that do not.
Joomla’s native multilingual system set up properly, with associations and language switching.
Several languages without the plugin stack the same job needs elsewhere.
User groups, access levels and view permissions configured for real organisational structures.
The right people see the right content, enforced rather than assumed.
Content types mapped to post types, media moved, URLs redirected and search visibility preserved.
A move to a platform that is cheaper to maintain, without the traffic loss.
Mostly about not breaking a site that has been running for a decade.
Upgrades and extension changes are applied to a copy and checked, never to a live site that people depend on.
Every extension checked for whether it is still maintained, before an upgrade finds out for you.
Template overrides and plugins instead of modifying core, so the next update does not erase the work.
Content structure translated deliberately, with a full URL map and redirects tested before launch.
An honest comparison of maintaining versus migrating, with both costs, before you commit.
What is installed, what was changed and why – because inherited sites of this age almost never come with notes.
Mostly organisations with a site nobody has looked at in years.
Running a major version that no longer receives security fixes, where the upgrade path is not obvious.
Membership bodies, associations and institutions using Joomla’s access levels seriously.
Where Joomla’s native language handling is doing real work and is not trivial to replicate.
Nobody in-house knows Joomla, and the person who built it is long gone.
Weighing another few years of Joomla against the cost of migrating properly.
A platform your team does not work in, on a site that still needs supporting.
Finding a Joomla developer is harder than it was, and harder still locally – most agencies stopped taking Joomla work years ago. That is precisely why inherited Joomla sites tend to sit untouched: not because the work is difficult, but because nobody will quote for it.
I work with organisations in Bangalore and across India on exactly these sites, as well as with clients in the UK, USA, Canada, the UAE and Singapore. The work is remote, and the first deliverable is usually an audit telling you what version you are on, what is installed, what is unmaintained and what your realistic options cost.
Working with organisations across the city and India.
Joomla work most agencies no longer quote for.
If leaving is right, it is done without losing traffic.
India, the UK, USA, Canada, the UAE and Singapore.
Serving Chennai, Bangalore, India, Canada, UK, USA, Dubai, Singapore.
Certain sectors adopted it early and stayed.
Typically needs: Departmental content, staff directories and role-based publishing rights.
How I help: Access levels configured per department, with upgrades handled around term dates.
Typically needs: Accessibility obligations, multilingual content and long procurement cycles.
How I help: Accessibility fixes, native multilingual setup, and upgrades documented for audit.
Typically needs: Member-only areas with several tiers of access.
How I help: User groups and view levels structured to match the membership, not approximated.
Typically needs: Practitioner and service content maintained by non-technical staff.
How I help: Simplified editing, structured content types and careful handling of enquiry data.
Typically needs: Product catalogues and downloadable specification documents.
How I help: Category structures and document handling, with search that works across both.
Typically needs: Ageing sites, limited budget, and a need to be certain about what replacing costs.
How I help: An honest maintain-versus-migrate comparison before anyone spends anything.
The first two stages usually change the plan, which is the point of having them.
I audit what is actually installed: Joomla version, PHP version, every extension and whether it is still maintained, template customisations and access-level structure.
You get: A written audit and an honest maintain-versus-migrate comparison with both costs.
Why it matters: Nobody should choose between upgrading and migrating without knowing what each involves on their specific site.
We settle the direction and scope. If it is staying, what gets upgraded and in what order. If it is moving, what the target structure is and how content maps onto it.
You get: An agreed plan and a fixed quote.
Why it matters: Projects drift when the platform decision is left open while work has already started.
For a redesign or migration, the templates and content structure are designed first – how existing content types translate and what the editing experience becomes.
You get: Designs and a content map you have approved.
Why it matters: Mapping content after the build has begun is how migrations lose things nobody notices for months.
The build: template overrides, extension work, or the migration itself, on a staging copy throughout.
You get: A working site on a staging URL.
Why it matters: These sites are usually live and in use, so nothing intermediate should reach visitors.
Testing across browsers and devices, access levels checked for every user group, multilingual associations verified, and for migrations the full redirect map tested.
You get: A tested site and, where relevant, a verified redirect map.
Why it matters: Permission errors and missing redirects are both silent until someone is affected.
Launch, then a walkthrough of whatever changed for your editors, with written notes. Upgrades continue under a care plan if you want one.
You get: A live site, documentation, and logins in your name.
Why it matters: Inherited sites are painful precisely because the last handover was not documented.
Joomla itself, and the platforms people most often move to.
Scoped from the audit, not offered as a package.
Joomla handles the basics competently – SEF URLs, metadata, sitemaps – but older installs often carry a decade of accumulated problems: duplicate URLs from menu structures, ItemID parameters splitting the same page across several addresses, and extensions generating pages nobody wanted indexed.
Migrations are the bigger risk. Moving platforms without a complete URL map is the most reliable way to lose search visibility, and it is entirely avoidable.
Older sites often hold genuinely useful information buried in modules and custom HTML where nothing can read it properly. Whether the site stays or moves, getting that content into real structure is what makes it legible to anything automated.
The practical reasons, rather than the adjectives.
Most agencies stopped taking Joomla work, which is why so many of these sites sit untouched. The work is not difficult; finding someone willing is.
If staying on Joomla is right for your site, I will say so. If the five-year maintenance cost makes migrating cheaper, I will say that instead, with both figures.
The URL map is built from a crawl of the live site and tested on staging. Losing visibility in a platform move is a planning failure, not an inevitability.
Overrides and extensions only. Plenty of inherited Joomla sites cannot be upgraded because someone edited core years ago, and that is not a trap I will set for the next person.