Donations, memberships, events and mailings keep working while we upgrade your Joomla site to Joomla 6. We make CiviCRM compatible through extensions and hooks, not core edits, so the next CiviCRM update doesn't undo the work.
Excellent
| Joomla | 5.4 → 6.0Template and extensions updated with it | Plan |
| CiviCRM | 6.19 · “Joomla 5+”Joomla 6 layer as extensions + hooks | Layer |
| PHP | 8.2 → 8.3bcmath, intl, zip, mbstring enabled | Host |
| Cron | cli bootstrapChecked on the new stack, hard time limit | Fix |
| Payments | 2 processorsDonation + recurring contributions tested | Test |
| CiviCRM extensions | 12 installed10 compatible · 2 update | 2 to do |
Both sites run CiviCRM on Joomla 6 with the same compatibility layer – and kept it through a CiviCRM update.
The hard partCiviCRM only ships for Joomla 5. Compatibility built as extensions and hooks, proven through a CiviCRM update.
The hard partMembership applications and donations are CiviCRM contribution pages – each one tested after the upgrade.
The current release is CiviCRM 6.19 (October 2026). Its Joomla download is labelled “Joomla 5+”. Official Joomla 6 compatibility is still an open task in CiviCRM's Joomla issue tracker (dev/joomla#61): the CiviCRM Joomla plugins have to move to Joomla's new event system.
We close that gap for your site today – without patching CiviCRM core files.
Compatibility code lives outside CiviCRM core, so you can keep installing CiviCRM releases.
We install a CiviCRM update on staging and check that every fix is still in place afterwards.
Scheduled jobs send mailings, reminders and membership renewals. We check that cron runs, logs and stops cleanly on Joomla 6.
Everything that collects money, members or email addresses is tested end to end.
Donation pages, recurring contributions, membership sign-ups and payment processors, tested end to end.
Event registration, personal campaign pages and their Joomla menu items keep working.
Mailing lists, subscriptions, bounce processing and cron, on the new stack.
Installed CiviCRM extensions reviewed for the new CiviCRM and PHP versions.
CiviCRM lives in several places and can use its own database next to Joomla's.
Front-end CiviCRM pages are reached through Joomla menu items and long task URLs.
Your supporters keep donating on the live site until the switch.
Joomla, PHP and CiviCRM versions, and every extension the site relies on.
Full backups of the Joomla and the CiviCRM database, staging on the target stack.
Joomla 6 compatibility via extensions and hooks, starting from CiviCRM's Joomla 5 package.
Template, calendar, editor, backup and download extensions updated together with CiviCRM.
Cron checked, payments tested, and a CiviCRM update installed to prove the fixes stay.
Joomla is moving plugins to its event system. The CiviCRM Joomla plugins still use the old style – the open dev/joomla#61. The pattern of the change, in a plain plugin:
SubscriberInterface lists the eventsclass PlgUserExample extends CMSPlugin { public function onUserLogin($user, $options = []) { // $user is an array, $options too return true; } }
final class Example extends CMSPlugin implements SubscriberInterface { public static function getSubscribedEvents(): array { return ['onUserLogin' => 'onUserLogin']; } public function onUserLogin(User\LoginEvent $event): void { $user = $event->getAuthenticationResponse(); } }
| Risk | Why | What we do |
|---|---|---|
| Cron stops silently | CiviCRM's tracker lists Joomla package issues that break the command-line bootstrap, so scheduled jobs stop without an error (dev/joomla#66 and #67). | Cron checked after every update, with logging and a hard time limit so runs can't pile up. |
| PHP & database versions | CiviCRM 6.16+ needs PHP 8.2 or newer; Joomla 6 needs PHP 8.3+ and MySQL 8.0.13+ or MariaDB 10.4+. PHP extensions such as bcmath, intl, zip and mbstring must be enabled. | A hosting checklist before we start. |
| Files, paths & databases | CiviCRM spans three folders and can use its own database (CiviCRM fixed an upgrade bug for that setup in dev/joomla#60). | Backups and the migration cover all of it. |
| Menu items & clean URLs | Supporters and emails use long task=civicrm/… URLs through Joomla menu items. | We keep the links that are already out there. |
The latest CiviCRM releases with our notes for Joomla sites, and guides for doing it yourself.
CiviCRM 6.19 ships for “Joomla 5+”. Official Joomla 6 support is still an open task (dev/joomla#61). We run it on Joomla 6 today with a compatibility layer outside CiviCRM core.
Fix Regressions in SearchKit, FormBuilder, KCFinder Integration, CKeditor4
CiviCRM on Joomla 6: The Complete Guide (2026)
Can you run CiviCRM on Joomla 6? Official support status, your three options, server requirements and a safe upgrade checklist – from a team running it live.
Is CiviCRM Compatible with Joomla 6? Status for CiviCRM 6.19
CiviCRM 6.19 ships for Joomla 5+, and official Joomla 6 support is still open. What that means for your site, what works today and when to upgrade.
CiviCRM with a Separate Database on Joomla: The Upgrade Bug and the Fix
If CiviCRM uses its own database, older Joomla upgrades could point it at the Joomla database. How to spot it, fix CIVICRM_DSN, and which release fixed it.
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.
“We use their services for our companies websites maintenance, development and updates … for last 5 years.”Maintenance · 5 years
“They worked on a full staging environment … including full backups, a clear rollback plan, and post-deployment support.”Joomla 4 → 5 upgrade
“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
“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
Not yet. CiviCRM's Joomla download is labelled “Joomla 5+”, and Joomla 6 compatibility is an open issue in CiviCRM's tracker (dev/joomla#61). We have CiviCRM running on Joomla 6 for clients using extensions and hooks.
No. We don't edit CiviCRM core files. As part of every project we run a CiviCRM update on staging and confirm the fixes are still in place.
No. We work on a full backup of both the Joomla and the CiviCRM database and compare the data before and after the upgrade.
Yes. We update the template and extensions such as calendars, editors, backups and download managers in the same project. See Joomla 6 migration.
We can – our maintenance & support plans cover Joomla, CiviCRM updates and cron monitoring.
“Fantastic help with migration from Joomla 3 to Joomla 6.”