Upgrade Your Old Moodle Without Breaking It.
Still running Moodle 3.9, 3.11, or 4.1? Every month you wait, the upgrade gets riskier — plugins go stale, PHP versions expire, security holes stay open. We upgrade you safely to Moodle 5.3 LTS for a fixed $200: full plugin audit, staging test, then a clean production cutover.
Wherever You Are, We Get You Current
Every path includes a plugin & theme compatibility audit on a staging clone first.
Moodle 3.x → 4.5 LTS
The rescue job. 3.9 and 3.11 are end-of-life — no security patches. We step you through 4.x to the long-term-support release your institution can sit on for years.
Moodle 4.x → 5.3 LTS
The sensible jump. Plugin audit, PHP 8.2/8.3 readiness check, theme compatibility, and database tuning — then cutover with zero downtime.
Broken Upgrade Rescue
Tried it yourself and got the white screen? Half-finished upgrade with database errors? We diagnose, roll back safely, and complete it properly.
How a Safe Upgrade Actually Works
The reason upgrades go wrong is skipping steps 1–3. We never do.
1. Audit
We inventory your Moodle version, PHP version, every plugin and theme, custom code, and database size. You get a written list of what upgrades cleanly, what needs replacing, and what needs rebuilding — before you pay anything beyond the fixed quote.
2. Staging clone
We clone your entire site — database, moodledata, code — to a private staging server and run the full upgrade there. Every plugin is tested, every critical workflow clicked through. Your live students see nothing.
3. Cutover & warranty
Only when staging is perfect do we touch production — usually a scheduled low-traffic window. Then 30 days of warranty: anything upgrade-related that breaks, we fix free.
What "We'll Upgrade Next Year" Costs You
Security patches stop
Moodle 3.9 and 3.11 no longer receive security fixes. Every disclosed vulnerability after end-of-life is an open door — and student data is exactly what attackers harvest from education sites.
PHP versions expire under you
Hosts retire old PHP versions. When your host forces PHP 8.2+, a Moodle 3.x site doesn't just look old — it white-screens. Then it's an emergency, not a plan.
The gap compounds
3.9 → 5.3 directly is not supported; it takes stepped upgrades with plugin rebuilds in between. Each year you wait adds a step, a risk, and cost. The cheapest upgrade is the one you do now.
Upgrade Questions
Will I lose courses, grades, or student data?
No. Upgrades never delete content — the risk is broken plugins and themes, not lost data. We take full database + filedir backups before starting, test everything on staging, and guarantee zero data loss.
What if a plugin has no version for the new Moodle?
The audit finds these before we start. Options: replace with a maintained equivalent, patch the plugin ourselves (we write Moodle plugins), or rebuild the functionality. You'll approve the plan before we proceed — no surprises mid-upgrade.
How long will my site be down?
Typically under an hour, scheduled in your lowest-traffic window. The heavy work happens on staging beforehand; production cutover is just the final sync and switch.
Should I go to 5.3 LTS or stay on 4.5 LTS?
5.3 is the current LTS — security support runs to October 2029 — and it is the default recommendation for most sites. 4.5 LTS remains supported to October 2027 if a critical plugin has no 5.3 release yet. We'll recommend based on your plugins; both are supported paths.
Is $200 really fixed? What if my site is huge?
$200 covers standard upgrades. Very large sites (multi-GB databases, dozens of custom plugins) get a fixed custom quote after the free audit — still fixed, still agreed before work starts. The audit itself costs nothing.
Find Out Exactly What Your Upgrade Needs — Free.
Send us your Moodle version and hosting details. We'll reply with a plugin audit checklist and a fixed $200 quote (or an honest custom quote) within 1 business day.
Get My Free Upgrade AuditRather stay current forever? Monthly support plans from $79