Free audit
We check the public site: version, template, extensions, security and migration signals, then send a written starting point.
Joomla 3 no longer receives official security patches, and its extensions and PHP support are falling behind. Staying put gets riskier every month. We have been working with Joomla since the Mambo days, and we move sites to a current, supported release with the content, URLs and search signals mapped.
No obligation. A fixed-scope quote follows once the audit and extension list are reviewed.
These are the signals that turn “we should update sometime” into a planned migration.
The 3.x line stopped receiving official security patches on 17 August 2023.
An old release may not run on the PHP version your host now requires.
Unmaintained components and modules can block upgrades and widen the attack surface.
An outdated template makes it harder to meet modern mobile and performance expectations.
A cleaned site on an unsupported release is more likely to be targeted again.
That is a reason to audit first, not a reason to guess at a rebuild.
A staged process, with the live site protected until the new one is tested.
We check the public site: version, template, extensions, security and migration signals, then send a written starting point.
We build the new site on a private copy. The live site is not edited while the new one is being prepared.
Articles, categories, media, users and key URLs are mapped. We add 301 redirects where a URL must change.
Forms, search, e-commerce, menu structure and mobile layouts are checked before launch.
We plan the cutover, monitor for issues and agree the post-launch support window in the SOW.
Not just a version number. A site your team can run and your visitors can trust.
Upgrade to Joomla 6, with the extension and PHP compatibility checked before launch.
Articles, menus, media, users and key landing pages are mapped rather than rebuilt by hand.
URL changes are documented and redirected so search equity is not silently lost.
We identify maintained alternatives or scope a focused rebuild where no replacement fits.
Admin access, updates, backups and baseline security settings are reviewed as part of the handover.
We explain what changed, what to update and how to avoid the next unsupported-release trap.
“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.”
The answers we give before a project starts.
We map existing URLs and metadata, carry them into the new site and add 301 redirects where a URL must change. That is designed to reduce ranking risk, but no responsible agency can guarantee search positions.
A small brochure site often takes 1–2 weeks. Larger sites, stores and custom extensions need longer. The audit identifies the likely scope before we commit to a date.
We check the extension list during the audit, find maintained alternatives where possible and rebuild the function only when no suitable replacement exists. That work is itemised in the quote.
We build on staging and switch over at the end. The cutover is planned, backed up and tested; a short maintenance window may still be agreed for DNS or email changes.
No. If WordPress is a better fit for your team, we can scope a Joomla-to-WordPress migration. The audit gives you the facts to compare.
Pick the next question that matches your situation.
The public audit gives you a written starting point before you commit to a migration. If you already have a brief, send it and we will confirm the scope.