Moodle upgrades without the exam-week surprise
We move universities and training teams to Moodle 4.5 LTS or the current 5.x release. Every upgrade is rehearsed on a copy of your site first, so the real one has a known duration and a tested way back.
Why an old Moodle version is a risk
Moodle publishes a new major release every six months. Standard releases get security fixes for about 18 months; long-term support (LTS) releases, such as Moodle 4.5 LTS, get them for three years. Once your version drops out of security support, newly found vulnerabilities in it are no longer patched.
Staying behind also gets more expensive over time. Hosting providers retire the PHP and database versions old Moodle needs, plugin authors stop maintaining older branches, and the gap to the current version, and the work to close it, keeps growing.
Not sure where your version stands? Moodle lists every release’s support dates on its releases page, and you can see your exact version under Site administration → Notifications.
Why Moodle upgrades fail
The upgrade script itself rarely fails. Upgrades go wrong because of what has piled up around Moodle since the last one:
Plugins with no compatible release
Third-party plugins that were never updated for the target version, and break the upgrade or the pages that use them.
Core hacks
Direct edits to Moodle’s own code. The upgrade silently overwrites them, and the features they powered stop working.
Version jumps you can’t make in one go
Each Moodle release can only be upgraded to from a minimum earlier version, so an old site may need an intermediate stop.
Server requirements
Newer Moodle needs newer PHP and database versions, so the server often has to be upgraded in the same window.
Custom themes
Moodle 4.0 changed navigation and introduced the course index. Themes built for 3.x often need real rework, not a recompile.
Years of data
Large log and grade-history tables can stretch some upgrade steps from minutes to hours, which nobody discovers until the night itself.
Our Moodle upgrade process
- 01
Upgrade audit
We inventory every plugin and its compatibility with the target version, compare your code against a clean Moodle to find core changes, and check the server and data size. You get a written upgrade plan with risks and a recommended path.
- 02
Fix what would break
We update or replace incompatible plugins, move core changes into plugins, and bring your theme up to the new version’s navigation.
- 03
Rehearse on a copy
We run the full upgrade on a copy of your production site, more than once, and time it. That gives you a real downtime figure, not a guess.
- 04
Test with your people
Your staff check the things that matter on the upgraded copy: key courses, quizzes, gradebooks, enrolments, SSO and reports.
- 05
Cutover with a rollback
The live upgrade runs in a window you choose, outside teaching and exam periods. Database, files and code are backed up first, and the rollback is tested, not assumed.
- 06
Aftercare
We watch errors, scheduled tasks and performance in the days after launch, and fix anything that surfaces.
Moodle 4.5 LTS or Moodle 5.x?
Moodle 4.5 LTS suits institutions that want to upgrade rarely: it’s supported with security fixes for three years from its release, so you can stay on it and plan your next major upgrade calmly.
The current 5.x release suits teams that want the newest features and are ready to upgrade roughly every year to stay inside support. Its support window is shorter, but each step is smaller.
The right choice depends on your plugins as much as on Moodle: if a plugin you rely on doesn’t support 5.x yet, 4.5 LTS is the safer target. The audit tells you which situation you’re in.
When to schedule a Moodle upgrade
Most universities upgrade once a year in the summer break, when teaching and exams are over and courses for the next year aren’t live yet. Work back from that window:
- Audit and plan a few months ahead, so plugin replacements and theme work aren’t rushed.
- Rehearse several weeks ahead, leaving time to fix what the rehearsal finds.
- Freeze changes to the live site shortly before the cutover.
If you’re already out of security support, don’t wait for summer: we can plan a shorter, lower-risk upgrade between terms.
Moodle upgrades: common questions
How long does a Moodle upgrade take?
The project, from audit to cutover, usually takes a few weeks to a few months, depending on how many custom plugins and core changes need work and how many versions you’re jumping.
The downtime itself ranges from under an hour to most of a day on large sites with years of data. We measure it during the rehearsal, so you know it before you announce the window.
Can we skip versions, for example go straight from 3.x to 4.5?
Not always. Each Moodle release only upgrades from a minimum earlier version, so older sites may need an intermediate stop. We plan the path during the audit, and the intermediate steps happen in the same maintenance window, so your users only see one upgrade.
What happens to plugins that don’t support the new version?
For each one we update it, replace it with a maintained alternative or with a core Moodle feature, or port it ourselves. You decide, plugin by plugin, with the cost of each option in front of you.
Will we lose courses, grades or user data?
No. The upgrade converts your existing data in place, and we take a full backup of the database, files and code before the cutover. The rehearsal on a copy is where problems are found, not your live site.
Can you upgrade a site another vendor customized?
Yes. That’s the most common case we see. The audit compares your code against a clean Moodle so every customization is found before the upgrade, not after.
Do we need to upgrade the server too?
Often. Newer Moodle versions need newer PHP and database versions. We check your server against the target version’s requirements during the audit and include any server work in the plan.
Moodle development
Custom plugins, themes, integrations and performance work, built upgrade-safe so you don’t end up here again.
Tell us which Moodle version you’re on.
Tell us your Moodle version, roughly how many users you have and what’s going wrong. An engineer, not a salesperson, replies within one business day.
