Two sites moved from Joomla 3 to Joomla 6
The hard partapartmentassociations.com rebuilt on T4 with jReviews, multifamilypress.com moved from K2 to Joomla articles, plus a custom "My articles" component.
Cookies, your choice
We use Google Analytics to see which pages help people, only if you allow it. Cookies for login, security (reCAPTCHA) and support chat are always on. Privacy policy
We have built on Joomla since 1.0. Before we quote, we audit every extension, template override and line of custom code. The migration runs on staging, and the live site switches only when your test list passes.
| Joomla | 3.10.12 → 6.0Rebuild + data migration | Plan |
| PHP / DB | 7.4 → 8.3 · MySQL 5.7 → 8.0Host upgrade before go-live | Host |
| Extensions | 38 found21 have a Joomla 6 release · 9 replace · 5 port · 3 remove | 17 to do |
| Overrides | 64 files in html/41 differ from the Joomla 6 core layouts | Rebuild |
| Custom code | 2 plugins · 1 moduleJFactory, JRequest, legacy MVC, jQuery-only JS | Port |
| URLs | 4,212 indexedKept, or 301-redirected from a map | Mapped |
Two sites moved straight from Joomla 3 – one with K2, one built with a page builder – and a large community rebuilt with new forums and access rules.
The hard partapartmentassociations.com rebuilt on T4 with jReviews, multifamilypress.com moved from K2 to Joomla articles, plus a custom "My articles" component.
The hard partEvery Quix page-builder page rebuilt on the T4 Framework – none left – with SEO improved, in 15 working days.
The hard partKunena to EasyDiscuss, WordPress content into Joomla, surgeon verification and ACL for four user groups.
Joomla only updates one major version at a time, from the last minor release. What breaks on the way depends on the version you run today.
Joomla 5 left bug-fix support on 13 October 2026 and gets security fixes until 12 October 2027. Joomla 3 and 4 get none.
3.10→4.4→5.4→6.xOr a clean Joomla 6 install with your content migrated, when the template and key extensions are Joomla 3 only. We pick the route in the audit.
JFactory, JRequest, legacy MVC0000-00-00 dates on MySQL 8 strict mode4.4→5.4→6.xJoomla Update with the pre-update check at every step, on a staging copy.
${var} strings5.x→5.4→6.xJoomla Update offers 6.0 only from the latest 5.4 release. The pre-update check lists extensions without a Joomla 6 version.
You get the findings as a written report with a fixed quote. Nothing is a guess on day one of the migration.
Every component, module, plugin and template, with its Joomla 6 status and the plan for it.
Each override compared with the new core layout it replaces, so nothing silently falls back.
Your own plugins, modules and scripts, scanned for PHP 8.3 and for removed Joomla APIs.
The things that make an update fail half-way, found and fixed on a copy first.
What your host has to provide before go-live, as a checklist you can forward.
Rankings and connected systems kept working after the switch.
You can follow every step on staging. Agencies get repo access and can review every change.
Extensions, overrides, custom code, database, server and URLs, on a copy of your site.
Full backup, staging on the target PHP and database, template and custom code in Git.
Joomla Update step by step, or a clean Joomla 6 with your content migrated. Extensions updated, replaced or ported.
Overrides rebuilt against the new layouts. Custom extensions ported to namespaced MVC, the DI container and the Web Asset Manager.
Your test list plus ours: forms, logins and ACL, payments, search, emails, cron, redirects, speed before and after.
Content freeze, final sync of new content, orders or members, switch, redirects live. The pre-switch backup is kept for rollback.
Custom extensions are rewritten to current Joomla APIs, not kept alive on compatibility layers that the next major release removes.
services/provider.phpSubscriberInterfacebind()// helper.php – Joomla 3 $db = JFactory::getDbo(); $id = JRequest::getInt('id'); $query = "SELECT title FROM #__content WHERE id = " . $id; $db->setQuery($query); $title = $db->loadResult(); JHtml::_('jquery.framework'); JFactory::getDocument()->addScript(JUri::root() . 'media/mod_example/js/example.js');
// src/Helper/ExampleHelper.php – Joomla 6 use Joomla\CMS\Factory; use Joomla\Database\DatabaseInterface; use Joomla\Database\ParameterType; $app = Factory::getApplication(); $db = Factory::getContainer()->get(DatabaseInterface::class); $id = $app->getInput()->getInt('id'); $query = $db->getQuery(true) ->select($db->quoteName('title')) ->from($db->quoteName('#__content')) ->where($db->quoteName('id') . ' = :id') ->bind(':id', $id, ParameterType::INTEGER); $title = $db->setQuery($query)->loadResult(); $app->getDocument()->getWebAssetManager() ->registerAndUseScript('mod_example', 'mod_example/example.js', [], ['defer' => true]);
The ones we meet most. Your audit lists every extension on your site.
| Extension | The issue | What we do |
|---|---|---|
| K2com_k2 | No release for Joomla 4 or later. | Items, categories, extra fields, tags and images moved to articles with custom fields; old URLs redirected. |
| CiviCRMcom_civicrm | The Joomla package targets Joomla 5. | Joomla 6 compatibility through extensions and hooks – no CiviCRM core changes, tested through a CiviCRM update. CiviCRM upgrade → |
| VirtueMartcom_virtuemart | VirtueMart 4 runs up to Joomla 5; VirtueMart 5 is the Joomla 6 line. | Joomla 5.4 + VirtueMart 4.8 first, Joomla 6 when VirtueMart 5 is stable. VirtueMart upgrade → |
| Kunenacom_kunena | Forum moves need structure changes, not just data. | Migrated to EasyDiscuss with a fixed migration tool; sub-categories became tags. Case study → |
| Page builders & old templates | Layouts stored in builder-specific formats. | Updated if the vendor supports Joomla 6, otherwise rebuilt on T4 with the content kept. |
| JCE, Akeeba Backup, DPCalendar, Phoca Download | Usually have Joomla 6 releases. | Updated in order, settings checked, tested on staging. |
Much of our work comes from other developers: agencies with client sites on Joomla, and teams who know their site but want senior Joomla hands for the hard part.
We work under your name, in your repository and your ticket system.
Hand us only the hard part and keep the rest.
One team for the whole job, explained without jargon.
“They do a good job of walking through each new project to fully understand the scope, and then are responsive throughout.”Several projects, several years
“They worked on a full staging environment … including full backups, a clear rollback plan, and post-deployment support.”Joomla 4 → 5 upgrade

“We use their services for our companies websites maintenance, development and updates … for last 5 years.”Maintenance · 5 years
“We asked ThePixel to migrate our website from Joomla 4 to Joomla 6. … I would highly recommend using ThePixel for website work.”Joomla 4 → 6 migration
“They consistently provide exceptional support and deliver outstanding results.”Development · upgrades · servers
“Fantastic help with migration from Joomla 3 to Joomla 6.”Joomla 3 → 6 migration
“We had a joomla 3.x site with a discontinued template … we are very impressed.”Joomla 3 → 5 upgrade
Not with Joomla Update – it moves one major version at a time (3.10 → 4.4 → 5.4 → 6). For many Joomla 3 sites a clean Joomla 6 install with the content migrated is faster and cleaner. The audit decides which.
Only where they have to, for example after K2 or with the modern router. Every indexed URL is checked, and anything that moves gets a 301 so rankings carry over.
The work happens on staging. On switch day there is a short content freeze while we sync new content, orders or members – usually minutes, planned with you.
No. Fixes go into overrides, plugins and hooks, so Joomla and extension updates keep working. Our CiviCRM work is the example: no core changes, tested through an update.
Yes. We work in your repository with commits or pull requests you review, and deploy to your staging and live servers – or set up staging for you.
Joomla 6 needs PHP 8.3 or newer and MySQL 8.0.13+ or MariaDB 10.4+. We give you a checklist for your host, or move the site to a host that meets it.
“Fantastic help with migration from Joomla 3 to Joomla 6.”