Moving Off Moodle 4.5? What to Evaluate Before You Upgrade

Moodle 5.3 shipped as the next LTS on October 5, and 4.5's general support already ended a year ago. Before your team spends a quarter recertifying plugins for the same architecture, here's what the upgrade actually costs — and what's worth asking instead.

Folio Team · 4 min read

Moodle 5.3 — the next Long-Term Support release — shipped October 5, 2026. If your institution is running Moodle 4.5, the prior LTS, that's the version most deployments will plan their next move around, because most schools upgrade between LTS releases rather than tracking every point release in between.

There's no fire alarm here. Moodle 4.5's general support ended back in October 2025; it's on security-only support now, through October 2027. You have runway. But "we have runway" is exactly the moment an upgrade quietly becomes a checkbox project instead of a real evaluation — and this one is a bigger lift than usual.

What the 5.3 upgrade actually requires

This isn't a drop-in point release. Moodle 5.3 raises the floor on infrastructure your team will need to plan around:

  • PHP 8.3 minimum (8.4 also supported), with the sodium extension required and max_input_vars set to at least 5000.
  • Database version bumps across the board: PostgreSQL 17, MySQL 8.4, MariaDB 11.4, or SQL Server 2019 as the new minimums.
  • Every LTI-integrated tool and plugin re-certified against the new codebase before you can trust it in production.

That's a real infrastructure project on top of the usual content migration — hosting, database upgrades, and a plugin audit, before a single instructor notices anything different in their course.

Moodle is also catching up on AI — so that's not the real question

Worth naming honestly: Moodle 5.2 already shipped its own AI providers (Gemini, Bedrock, Ollama) and Explain/Summarize buttons. If your evaluation reason was "our LMS doesn't have AI," that gap is closing. Pitching against a missing feature that's actively being built isn't an honest comparison, and it's not where the real difference sits anyway.

The real question is architectural: what's built into the platform from the start versus stitched on afterward. Four are worth asking about specifically before you file the upgrade ticket:

Is academic integrity a bolt-on score, or built into how work is submitted? A similarity or AI-detection percentage from a third-party plugin is a probability an instructor has to interpret and a student can't meaningfully appeal. Integrity checked at the point of submission — verified sources, a real revision history — is a different kind of evidence, not a plugin someone has to keep updated and defending.

Is course registration actually fair, or a chain of plugins strung together? Enrollment, waitlists, and section fairness in most Moodle deployments run through whatever combination of plugins and manual overrides a registrar's office has accumulated over a decade. Worth asking whether that's a designed system or an inherited one.

Is the platform Arabic and RTL-native, or an add-on translation layer? Right-to-left layout, date and numeral conventions, and Arabic-script citation handling behave differently when they're a first-class part of the architecture instead of a language pack bolted onto a left-to-right design. If a meaningful share of your student body reads and writes in Arabic, this isn't cosmetic.

How many separate systems does "one course" actually touch? Assignments, a citation tool, a plagiarism checker, a separate writing environment, an AI add-on — each one is its own login, its own data silo, and its own point of failure. Counting the real number is usually the most useful five minutes of the whole evaluation.

We're not pitching a migration tool

To be clear about what this isn't: Folio doesn't import a Moodle course backup or plug into your existing Moodle install. It's a different kind of platform — built around a fair registration engine, integrity checked at the point of submission rather than scored after the fact, and Arabic-native from the ground up rather than translated on top — not a Moodle plugin or a like-for-like feature swap. Grades of record, transcripts, and SIS integration are real considerations either way, and they don't disappear just because the LMS underneath changes.

If you're already opening the hood for a PHP and database upgrade this cycle, that's also the cheapest moment to ask whether the architecture underneath is the one you'd choose today. Folio for Institutions is built to answer that question directly, not to make the upgrade decision harder.

Written by Folio Team. Published .

Keep reading

  1. How to Cite a Validated Scale in Your Methods SectionCiting the paper isn't enough. A reviewer wants the version, the item count, the response anchors, your own reliability, and proof you were allowed to use it. Here's the checklist.Research tips
  2. What three top journals actually require, and why formatting still trips people upCitation style, reference format, structure and length limits for JACS, Psychological Science and the American Economic Review, checked against each journal's own author instructions, with the detail in each that is easiest to miss.Citations
  3. Why Folio Surveyor gives you notes instead of writing your Methods sectionA Methods section is where a researcher states, under their own name, what was done. Surveyor no longer drafts it. It hands over the facts from the study's own records, and a list of what the data cannot say.Research tips

Folio is free to start.

Write with your own sources, check every citation, and keep a record of how the work was made.

Start writing free

All articles