Moodle™ upgrade to 5.3 LTS
We carry out the entire upgrade for you: we map out what needs to happen, adapt plugins, theme and server, test everything on a separate environment and only go live once you have signed it off. After that we stay available for aftercare.
How long does your version still get security fixes?
Moodle ships security fixes for each version up to a fixed date. After that, newly discovered vulnerabilities are no longer fixed. You want to be on a newer, supported version before that date.
| Current version | Security fixes end |
|---|---|
| Moodle 4.5 LTS | 4 October 2027 |
| Moodle 5.1 | 19 April 2027 |
| Moodle 5.2 | 4 October 2027 |
| Moodle 5.0, 4.4 and older | Already ended |
Moodle 5.3 LTS gets security fixes until 1 October 2029. All dates are in Moodle's official release overview.
What 5.3 asks of your environment
These are the main requirements. Not every point applies to every installation; in the intake we check which ones apply to you.
- You can upgrade directly to 5.3 from Moodle 4.4 or newer. On an older version, an intermediate step comes first.
- PHP 8.3 or higher.
- For the database, depending on which one you use: PostgreSQL 17 or higher, MySQL 8.4 or higher, or MariaDB 11.4 or higher.
- From 5.3 the Classic theme is no longer part of Moodle itself. If you use Classic or a theme built on it, that needs a solution.
How the upgrade works
Before you decide
Free intake
In 30 minutes we go through your current version, plugins, theme, hosting and planning.
Initial assessment within three working days
Within three working days of the intake you receive our initial assessment of the next steps. It sets out where deeper technical investigation is needed, and what that investigation covers and costs. If the upgrade is already clear enough to judge, we quote a fixed price straight away.
Paid investigation, only where needed
For an environment with many or custom plugins, a custom theme or a large version gap, we first look under the hood. That investigation is paid and only starts once you agree to the assessment.
Upgrade proposal
You receive a proposal with the approach, the order of work, the risks, the price and what we need from you or your host. With that, you decide whether we carry out the upgrade.
The upgrade
Test environment
We set up a copy of your Moodle and run the upgrade there first. Your production site keeps running as normal in the meantime.
Technical changes
Updating or replacing plugins, adapting the theme and bringing the server up to the new requirements.
Acceptance
You test on the test environment whether everything works the way you expect. We only continue once you sign it off.
Production rollout
At an agreed time, with a fresh backup that can be restored, we carry out the upgrade on production.
Aftercare
After go-live we stay available for questions and fix issues that only surface in day-to-day use.
What determines the cost?
No two Moodle environments are alike, so there is no single fixed price for every upgrade. What mostly drives the work:
- The number of plugins and how complex they are, especially if some are custom-built.
- A custom theme, or a theme that depends on what changes in 5.3.
- Your current version: the bigger the gap to 5.3, the more changes along the way.
- Infrastructure changes, such as a newer PHP or database version or a different web server setup.
That is why there are no amounts here. After the intake you hear what the next step covers and costs, before you commit to anything.
Wherever your Moodle runs
We carry out upgrades on your own servers, in cloud environments and with external hosting providers. First we assess whether the environment can handle 5.3: what access there is, whether PHP, database and web server can be changed, and whether there is a test environment and a backup that can be restored.
If the current environment cannot do it, we discuss changes by your hosting provider or a migration.
Is your Moodle fully managed by a Moodle service provider? Then the upgrade runs through them. If you want to switch, we take over the management and bring your Moodle to 5.3 with us.
How we take over Moodle management →Frequently asked questions
Do we need to upgrade now?
No, but start testing now. Plan to go live before the security support end date of your current version, once your plugins and theme are ready and acceptance testing is done. If your version no longer gets security fixes, it is more urgent. Waiting for a later release without LTS usually means a shorter support window and less time to prepare.
Will I get a price for the whole upgrade within three working days?
Not always. Within three working days you receive an initial assessment of the next steps. If the upgrade is clear enough to judge, it includes a fixed price. If not, it sets out which investigation is still needed and what that costs, and the upgrade price follows after that.
Does our Moodle have to be hosted with Sebsoft?
No. We also work on your own server, in the cloud or with an external host, as long as we get the access we need.
Prefer to start somewhere else?
Doing it yourself? The free upgrade checklist lists the steps for a safe upgrade. Get the upgrade checklist →
Want a broad picture of how your Moodle is doing first, including security and performance? That is the technical scan: an investigation with a report, separate from the upgrade itself. See the technical scan →
Is one specific plugin holding the upgrade back? See the plugin rescue →
Prefer to write first?
Tell us where your Moodle runs and what you know about your current setup. We will get in touch to schedule the intake. Only name, email and where your Moodle runs are required.