A practical upgrade guide from Moodle 3.x to 4.x — breaking changes, visual improvements, plugin compatibility traps, and a realistic 8-week project plan.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
A plain-English look at agentic AI in L&D — what real agents do, where the hype is, and why an owned platform keeps you in control.
What adaptive learning really is, where personalized paths help versus where uniform compliance content is required, and how an owned platform delivers both.
How to mix instructor-led, virtual, and self-paced training for operational teams, and let one owned platform schedule and track all of it.
If your Moodle site looks like 2017, that's because it probably is 2017. The number of organizations still running Moodle 3.5, 3.7 or 3.9 in production is high enough that we've made an entire fixed-price package out of upgrading them.
This post covers what actually changes between Moodle 3.x and 4.x, the things that break, the things that improve, what the upgrade plan looks like, and the cost. It's pitched at the L&D lead or admin who knows their site is on an old version and needs to make the case for upgrading internally.
Moodle 4 was released in 2021 and has shipped multiple point versions since (4.1 LTS, 4.2, 4.3, 4.4, 4.5). The differences vs 3.x are bigger than the version number suggests.
Moodle 4's UI is a near-complete rebuild. The course experience uses a clean, modern card-and-section layout. Navigation is consolidated into a side drawer. The course index gives learners a clear at-a-glance view of where they are. The mobile experience is genuinely usable.
This is the change that matters most for learner engagement. The aesthetic critique of Moodle that was fair for a decade no longer is. Properly themed, Moodle 4 looks comparable to any modern SaaS LMS — it just costs you a fraction.
The new "course index" sidebar lets learners see their progress through a course in real time, with collapsible sections and visual completion indicators. Replaces the long-scroll layout that defined Moodle for years.
Activity completion rules have been simplified and clarified. The settings UI is less of a maze. New conditional-access logic is more powerful and less brittle.
Notifications and messaging have been properly reworked. The Moodle 3.x notification experience was famously hostile; 4.x is closer to what users expect from a modern web app.
Core integrations have been refreshed. H5P content is now better integrated; BBB and Zoom plugins have improved authentication and UX.
WCAG 2.1 AA conformance is much better in 4.x out of the box. For organizations with public-sector accessibility commitments or ADA exposure, this matters.
Moodle 4.x is meaningfully faster for typical learner workflows. Page-load times on common course pages are 25-40% lower vs 3.9 on equivalent hosting.
The honest list. None of this is fatal — all of it is manageable in an 8-week project — but it's why you can't just click "upgrade" in the admin panel.
The biggest single source of upgrade pain. Most third-party plugins built for Moodle 3.x need updates or replacements for 4.x. The major ones (BBB, H5P, Zoom, plagiarism checkers) have 4.x-compatible versions. The long tail of niche plugins often doesn't.
A pre-upgrade plugin audit is the most important piece of the project plan: list every plugin, classify each as "supports 4.x", "has an updated alternative", or "needs replacement or workaround." Skipping this step is how upgrades turn into 4-month projects.
Custom themes built for Moodle 3.x will not work on 4.x. The theme system itself changed significantly. Plan to rebuild the theme; this is one of the bigger workstreams in any upgrade.
If your previous deployment had custom local plugins or core hacks (which we don't recommend, but it's common), each of these needs to be assessed for 4.x compatibility. Some will need rewriting against new APIs.
The reporting framework changed. Custom reports built in 3.x usually need rebuilding in the new framework. Standard reports are generally fine.
The 3.x front-page model (where you composed a custom front page from blocks) has been deprecated in favor of a more modular approach. Front page setup needs revisiting.
Our Rapid Upgrade package is structured around this timeline. Here's what each week looks like for a typical mid-sized deployment.
Full audit of the existing 3.x site: plugins installed, theme details, custom code inventory, content scale, integration touch-points, user base structure. Output: a written upgrade-risk register identifying every plugin and custom component that needs action.
Staging AWS environment provisioned. New 4.x install, base theme started. Branding workshop with the client; theme design direction approved.
Custom theme built against Moodle 4.x. Updated plugins installed. Replacement plugins selected for those with no direct 4.x version.
Course data, user data, completion history, file uploads migrated from production 3.x to staging 4.x. Migration scripts validated. Spot-check sample courses for fidelity.
SSO, HRIS, payment provider — all connections re-validated on the new platform. Any custom report rebuilds.
Pilot user cohort hits the staging site. Real workflows tested. Bug list compiled and resolved.
Production cutover at a defined low-usage window (typically a Saturday evening). 3.x site preserved read-only for 30 days as a safety net. Admin training delivered. Documentation handed over.
End-to-end elapsed: 8 weeks for most mid-market deployments. Larger or more complex sites (multi-tenant, heavy plugin customization) extend to 10-12 weeks.
Our fixed-price for the Rapid Upgrade package is $15,000 including all of the above plus 30 days of post-launch support. That's the published price; many partners quote in the $22k-$35k range for the equivalent work.
After upgrade, ongoing managed service is typically $750-$1,500/month depending on scale and uptime requirements.
Three reasons the upgrade conversation has become more pressing this year.
Moodle 3.9 reached LTS end-of-life in December 2023. Moodle 3.11 reached end-of-life in November 2024. Any 3.x site still in production now is running unpatched against known vulnerabilities. For regulated firms this is a documented control failure.
Mobile traffic to internal learning platforms has grown steadily; in retail, healthcare and field-service contexts, mobile is now the dominant access mode. Moodle 3.x mobile UX is functional at best. Moodle 4.x is genuinely usable. The gap is large enough to affect engagement metrics measurably.
If the L&D team is benchmarking your current platform against modern SaaS LMS, the visual comparison with a 2017-era Moodle is always going to lose. The same conversation against a properly themed Moodle 4.x looks very different. Sometimes the entire "we need to switch to SaaS" conversation goes away once people see what an upgraded Moodle actually looks like.
Different problem, smaller scope. Point-version upgrades within 4.x are much less disruptive than the 3.x-to-4.x jump. Plugin compatibility is mostly preserved across point versions. Theme tweaks are usually minor.
For sites already on 4.x, the conversation is more about whether to move to the 4.5 LTS (current as of 2026) for the longer support window, or to wait for the next LTS cycle. We typically advise moving to the current LTS within 12-18 months of release.
For organizations still running Moodle 3.x in production, upgrading is no longer optional — security, mobile, and competitive aesthetics all argue the same direction. The work is well-scoped, the timeline is predictable, and the cost is a fraction of the SaaS alternative.
If you'd like a quote for upgrading your specific site — including a plugin audit and a written risk register before any commitment — book a scoping call. We'll tell you honestly if your current site is already in a good state and doesn't need work.