New Pro + Launch: pick a template and our developers set up your site in 2 business days.
See how it works
Upgrade · Joomla 6 migration

Joomla 3, 4 and 5 sites, moved to Joomla 6 without breaking what works

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.

from 3.x · 4.x · 5.xPHP 8.3+MySQL 8.0.13+MariaDB 10.4+
Audit summaryexample.orgExample
Joomla3.10.12 → 6.0Rebuild + data migrationPlan
PHP / DB7.4 → 8.3 · MySQL 5.7 → 8.0Host upgrade before go-liveHost
Extensions38 found21 have a Joomla 6 release · 9 replace · 5 port · 3 remove17 to do
Overrides64 files in html/41 differ from the Joomla 6 core layoutsRebuild
Custom code2 plugins · 1 moduleJFactory, JRequest, legacy MVC, jQuery-only JSPort
URLs4,212 indexedKept, or 301-redirected from a mapMapped
Result: fixed quote + migration planStaging first
Your upgrade path Joomla
  1. J3.10Joomla 3No support
  2. J4.4Joomla 4No support
  3. J5.4Joomla 5Fixes to 12 Oct 2027
  4. J6Joomla 6Where you end up
Proof, not promises

Upgrades that are live today

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.

All projects
Your upgrade path

Where you start decides the work

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.

Route3.10→4.4→5.4→6.x

Or 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.

What breaks

  • Bootstrap 2 templates and their overrides
  • Extensions with no Joomla 4+ release (K2, old forms, galleries)
  • Custom code on JFactory, JRequest, legacy MVC
  • MooTools and jQuery-only scripts
  • 0000-00-00 dates on MySQL 8 strict mode

What we do

  • New template on T4 / Bootstrap 5, or yours rebuilt
  • K2 items, categories, extra fields and tags moved to articles + custom fields
  • Custom extensions ported to namespaced MVC
  • Dates, collation and tables fixed (utf8mb4, InnoDB)

Usually the biggest job

  • Template and overrides
  • Replacing abandoned extensions
  • URL changes from the new router – mapped to 301s
Route4.4→5.4→6.x

Joomla Update with the pre-update check at every step, on a staging copy.

What breaks

  • Extensions that lean on the backward-compatibility plugin
  • APIs deprecated in Joomla 4 and removed later
  • PHP 8.2+ deprecations: dynamic properties, ${var} strings
  • Hosting still on PHP 8.1 or MySQL 5.7

What we do

  • Every extension checked against its vendor's Joomla 6 release
  • Custom code fixed to run without the compatibility layer
  • PHP 8.3 compatibility scan and fixes
  • Hosting checklist for your provider

Usually the biggest job

  • Third-party extensions with late or no updates
  • Custom plugins and modules
Route5.x→5.4→6.x

Joomla Update offers 6.0 only from the latest 5.4 release. The pre-update check lists extensions without a Joomla 6 version.

What breaks

  • Extensions without a Joomla 6 release yet
  • Code still on APIs deprecated in Joomla 5
  • Hosting below PHP 8.3

What we do

  • Upgrade on staging, extension by extension
  • Patch or replace what has no update – outside the core
  • Test forms, logins, payments, cron and emails

Usually the biggest job

  • Waiting extensions: CiviCRM, VirtueMart, page builders
  • Often days, not weeks
Before we quote

What the audit checks

You get the findings as a written report with a fixed quote. Nothing is a guess on day one of the migration.

Extensions

Every component, module, plugin and template, with its Joomla 6 status and the plan for it.

  • #__extensions inventory
  • vendor J6 release + update server
  • keep · update · replace · port · remove

Template & overrides

Each override compared with the new core layout it replaces, so nothing silently falls back.

  • templates/*/html/** diff
  • layouts/joomla/** changes
  • Bootstrap / jQuery dependencies

Custom code

Your own plugins, modules and scripts, scanned for PHP 8.3 and for removed Joomla APIs.

  • PHPCompatibility 8.3 scan
  • J* classes, legacy MVC, events
  • raw SQL → query builder + bind()

Database

The things that make an update fail half-way, found and fixed on a copy first.

  • #__schemas version per extension
  • utf8mb4 · InnoDB · zero dates
  • orphan tables and columns

Server

What your host has to provide before go-live, as a checklist you can forward.

  • PHP 8.3+ · MySQL 8.0.13+ / MariaDB 10.4+
  • PHP extensions, memory, limits
  • cron → Joomla CLI / scheduler

URLs & integrations

Rankings and connected systems kept working after the switch.

  • indexed URLs → 301 map
  • sitemap, canonicals, hreflang
  • payments, SSO, APIs, mail
How it runs

Six steps, each with something you can check

You can follow every step on staging. Agencies get repo access and can review every change.

  1. Audit

    Extensions, overrides, custom code, database, server and URLs, on a copy of your site.

    You getAudit report, migration plan, fixed quote
  2. Staging & backups

    Full backup, staging on the target PHP and database, template and custom code in Git.

    You getStaging URL, repository access
  3. Core & extensions

    Joomla Update step by step, or a clean Joomla 6 with your content migrated. Extensions updated, replaced or ported.

    You getChange log per extension
  4. Template & code

    Overrides rebuilt against the new layouts. Custom extensions ported to namespaced MVC, the DI container and the Web Asset Manager.

    You getCommits you can review
  5. Test

    Your test list plus ours: forms, logins and ACL, payments, search, emails, cron, redirects, speed before and after.

    You getTest report with what was fixed
  6. Go live

    Content freeze, final sync of new content, orders or members, switch, redirects live. The pre-switch backup is kept for rollback.

    You getGo-live checklist, rollback backup
For developers

We port code, we don't wrap it

Custom extensions are rewritten to current Joomla APIs, not kept alive on compatibility layers that the next major release removes.

  • Namespaced MVC with services/provider.php
  • Events through SubscriberInterface
  • Database through the container, queries with bind()
  • Scripts and styles through the Web Asset Manager
  • PHP 8.3: typed properties, no dynamic properties
// 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]);
Same module, before and after the port. No jQuery, no SQL built from request data.
Extensions

What happens to the extensions you run

The ones we meet most. Your audit lists every extension on your site.

ExtensionThe issueWhat we do
K2com_k2No release for Joomla 4 or later.Items, categories, extra fields, tags and images moved to articles with custom fields; old URLs redirected.
CiviCRMcom_civicrmThe Joomla package targets Joomla 5.Joomla 6 compatibility through extensions and hooks – no CiviCRM core changes, tested through a CiviCRM update. CiviCRM upgrade →
VirtueMartcom_virtuemartVirtueMart 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_kunenaForum moves need structure changes, not just data.Migrated to EasyDiscuss with a fixed migration tool; sub-categories became tags. Case study →
Page builders & old templatesLayouts 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 DownloadUsually have Joomla 6 releases.Updated in order, settings checked, tested on staging.
Who we work with

Agencies, in-house teams and site owners

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.

Agencies

We work under your name, in your repository and your ticket system.

  • White-label, NDA on request
  • One quote per site, or for a batch of client sites
  • Your client talks to you – we stay in the background

Developers

Hand us only the hard part and keep the rest.

  • One extension, one integration, or a review of your code
  • Commits and pull requests you approve

Site owners

One team for the whole job, explained without jargon.

  • A fixed quote before work starts
  • Maintenance after launch if you want it
What clients say

Clients on our Joomla upgrades

Brent Williams
Brent WilliamsChief Insider at Multifamily Insiders
“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
Professional, Reliable Joomla Upgrade – Highly Recommended
Gary BirkUS
“They worked on a full staging environment … including full backups, a clear rollback plan, and post-deployment support.”
Joomla 4 → 5 upgrade
Saurav Wadhwa
Saurav WadhwaManaging Director of IBBZ Accounting
“We use their services for our companies websites maintenance, development and updates … for last 5 years.”
Maintenance · 5 years
Communication was excellent throughout the process
Fred B.US
“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
A loyal client of thepixel for 3+ years
Abdullahi BusuriManaging Director, AdminPlans
“They consistently provide exceptional support and deliver outstanding results.”
Development · upgrades · servers
Fantastic help
IKPCZ
“Fantastic help with migration from Joomla 3 to Joomla 6.”
Joomla 3 → 6 migration
A perfect job reproducing our styles and all the articles
Carin HandsunUS
“We had a joomla 3.x site with a discontinued template … we are very impressed.”
Joomla 3 → 5 upgrade
FAQ

Joomla 6 migration questions

Not here? Ask in the forum or send us your project.

Can we go from Joomla 3 straight to Joomla 6?

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.

Will our URLs change?

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.

How long does the live site go down?

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.

Do you modify Joomla or extension core files?

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.

Can you work in our Git repository and on our hosting?

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.

Our host is on PHP 8.1. Is that a problem?

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.

Get a quote

Send us the site. We reply in under 12 hours

“Fantastic help with migration from Joomla 3 to Joomla 6.”
IKP · Joomla 3 → 6 migration
  1. 01Tell us the site URL, your Joomla version and the extensions you depend on.
  2. 02We audit a copy: you get the report and a fixed quote.
  3. 03You decide. Nothing starts before you agree to the plan.
Cron Job Starts