upnoow

Moodle upgrade · Moodle 5

Moodle upgrade services: update to the current version without breaking your site.

Upgrading Moodle is not just pressing a button. Versions change requirements, plugins need to be compatible and a failed update can leave the site unreachable. We plan and test the upgrade on a copy and go live with a rollback plan.

Customized Moodle platform shown on a laptop and a phone

10+ years

of experience

50+

projects delivered

Ongoing

support

Custom

development

Why upgrading is not trivial

Each Moodle version changes what it requires from the server, from the database and from plugins. Recent versions need newer PHP versions, and some releases change the folder structure that the web server must point to. A site that was working yesterday can fail after an update because one of these requirements was not met.

Also, you cannot always jump straight from an old version to the latest one. There are supported upgrade paths, and sites that are far behind may need intermediate steps.

How we do an upgrade

Our process is designed so that the risky parts happen on a copy and not on your real site:

Review of the current version, server, database and PHP.
Compatibility check of every plugin and customization against the target version.
Upgrade on a copy of your platform, with functional tests.
Fix or replacement of what does not work.
Full backup of files, database and the data folder before the real upgrade.
Go-live in a quiet window, with a rollback plan.
Monitoring afterwards.
A company training its team with Moodle

Upgrades planned around your calendar

Universities and training companies cannot upgrade in the middle of an exam period. We schedule the upgrade around your academic or business calendar, so that learners are never surprised.

Tell us your critical dates and we plan the work to stay away from them.

Moodle 5 and recent versions

We follow the new releases and publish what changes, including requirements, the new folder structure and what to check before updating. If your platform is on an older version, the first step is usually a plan with the intermediate versions and the plugins that must be replaced.

If an update has already gone wrong, see also our recovery work, which follows the same principle: work on copies, preserve the original and go back to production only when everything is verified.

Upgrade and support together

Upgrades are easier when they are part of regular maintenance, because versions do not pile up. Many of our clients combine support or managed hosting with scheduled updates, so that security fixes arrive on time and big jumps are avoided.

What changes between Moodle versions

Each release of Moodle brings new features, fixes security problems and sometimes changes what the platform requires from its environment. Newer versions require newer versions of PHP and of the database, and some releases change the structure of folders and the way the web server is configured. Plugins, which are written for specific versions, may stop working until their authors publish a compatible release.

That is why an upgrade is a project and not a click. The question is never only whether Moodle will update, but whether everything around it, from the server to every plugin and customization, will keep working.

Long-term and regular releases

Moodle publishes regular releases and long-term support releases. Regular releases receive fixes for a shorter period, and long-term support releases are maintained for longer, which suits organizations that prefer to update less often. Choosing the right line depends on how much change your team can absorb and how long you need each version to stay supported.

We help you decide, taking into account your plugins, your calendar and the support period of each version. For many institutions the best strategy is to stay on a long-term release and update on a planned schedule, avoiding both the risk of an unsupported version and the effort of following every release.

An illustrative project: an old platform with many plugins

This is a hypothetical example, and not a client case. A university runs a Moodle that is three major versions behind. It uses more than forty plugins, some installed by people who no longer work there. The platform is slow during exams and the server runs a version of PHP that no longer receives security updates.

The project begins with an inventory of the plugins, separating those that have a current release, those that have been replaced by features of Moodle itself and those that have been abandoned. The abandoned ones that matter are rebuilt or replaced, and the rest are dropped. The upgrade is carried out on a copy, in steps, with functional tests at each step. After the university approves, the same steps are repeated on production, in a window that avoids exams, with a verified backup and a plan to go back.

What we test before going live

Testing is the difference between an upgrade and a gamble. On the copy of your platform we check the following:

Login with every authentication method you use.
Course pages, activities and resources from a sample of real courses.
Quizzes, assignments and grading, including a full attempt and its grade.
Enrolment, groups and roles.
Scheduled tasks and email notifications.
Reports that management relies on.
Customizations, theme and integrations.
Performance with a realistic number of simultaneous users.

Planning the day of the upgrade

The final upgrade is scheduled when the platform is least used. We agree the time with you, tell your users in advance, put the site in maintenance mode, take a full backup of files, database and the data folder, and run the steps we rehearsed. After the upgrade we repeat the key tests and open the platform again.

If something unexpected happens, the rollback plan applies: we restore the backup and the platform returns to its previous state, so that learners and teachers find it working. We then analyze what went wrong and schedule a new attempt.

Common mistakes in upgrades

These are the causes behind most failed upgrades:

Updating the code without checking the PHP and database versions first.
Ignoring plugins until the site stops loading.
Upgrading on production without a rehearsal on a copy.
Choosing an update date that coincides with exams or course starts.
Skipping the backup of the data folder, which holds the files.
Having no plan to go back if something fails.

Why delaying upgrades costs more

Postponing updates feels safe because nothing breaks today. The cost accumulates in the background: security fixes that you do not receive, plugins that fall further behind, servers that run software that is no longer supported and, eventually, a jump of several versions that is much harder to plan than regular steps. Organizations that update on a schedule spend less and take fewer risks than those that update only in an emergency.

A planned update calendar, tied to your academic or business year, is one of the cheapest forms of protection for a learning platform.

A typical upgrade timeline

The duration depends on how far behind the platform is and how many plugins it uses. A common sequence is a first week for review and inventory, one or two weeks for the upgrade and tests on a copy, a few days for fixes and approval, and a planned window for the final upgrade. After the upgrade, we monitor the platform closely for the next days. We give you a calendar after the review, once we know what has to be done.

Upgrading with minimal disruption for learners and teachers

The success of an upgrade is measured by how little learners and teachers notice it. We schedule the final step at a time of low use, inform users beforehand, keep the downtime as short as possible and confirm that courses and activities work the way they did. If anything changes in how a feature looks or behaves, we tell your team in advance so that they can pass it on.

After the upgrade we stay alert for the following days, since problems that affect only a few users often appear a day or two later.

Upgrading plugins and customizations

The plugins are usually the hardest part. For each one, we check whether a compatible version exists, whether it has been replaced by a feature in Moodle itself and whether it is still needed. Customizations in the theme or in the code are tested and adapted. The result is a platform that is current and also simpler than before, with fewer components to maintain.

Upgrading as part of regular care

The easiest upgrade is the one that follows a regular rhythm. Organizations that update once or twice a year, on a schedule that suits their calendar, face small steps instead of large jumps. We help set up that rhythm, with a calendar of updates, a short test routine that your team can repeat and a budget for the work. Platforms that follow it rarely have emergencies, and when one occurs, the preparation makes it much smaller.

Documentation of each upgrade

After each upgrade we leave a short record: the versions before and after, the plugins that were updated or replaced, the problems found and how they were solved, and what to watch in the next weeks. This record saves time at the next upgrade, helps a new administrator to understand the history of the platform and gives management a clear account of what was done.

Related Moodle services

Managed Moodle: we take care of the server

Server, backups, SSL, security updates and support included. These are some of our monthly plans.

Popular L

US$66 /month

~400 students · ~40 concurrent

Corporativo XL

US$268 /month

~1.500 students · ~150 concurrent

Corporativo Max

US$668 /month

~3.000 students · ~300 concurrent

Elite M

US$944 /month

~5.000 students · ~500 concurrent

See all plans

Frequently asked questions about Moodle upgrades

Where we work

Ready to take the digital leap?

Tell us your idea and we will show you how to make it happen. No commitment.