Moodle to Custom LMS Migration: A 2026 Playbook

Direct Answer

Moving off Moodle or LearnUpon makes sense when plugin maintenance, rigid branding, or per-learner fees are capping your growth, not before. A clean migration preserves SCORM packages, user records, and grades through standard exports; it does not preserve plugin behavior, custom CSS hacks, or LearnUpon's workflow automations, which get rebuilt by hand. Budget 8-20 weeks and, with us, $25,000–$50,000 for a typical migration-and-rebuild, less if the scope is tight.

• What transfers automatically? — Short answer: Courses (via .mbz backup), SCORM/xAPI packages, user records, grades, completion data
• What has to be rebuilt? — Short answer: Plugin-dependent features, LearnUpon automation rules, custom theming, SSO integrations
• Typical timeline — Short answer: 8-20 weeks for a focused MVP; longer for large, plugin-heavy instances
• Typical cost — Short answer: $10,000–$20,000 for a contained migration; $25,000–$50,000 for a full custom rebuild, more if it is genuinely complex
• Who should NOT migrate yet — Short answer: Anyone still validating course-market fit, or anyone under roughly 200 learners, where the SaaS math still wins outright

Why This Guide Exists

Search "moodle to custom lms migration" and you get three kinds of pages: a Moodle forum thread from someone fighting with .mbz files, a personal blog post about one university's switch to Canvas, and a vendor services page selling a "custom LMS" that's actually a WordPress theme with a badge. None of them tell you what actually survives a migration, what a realistic budget looks like, or when staying put is the smarter move.

This is that guide. No inflated claims about SaaS "owning your content" — that's not how exports work, and we'll show you exactly what does and doesn't move.

What Actually Migrates From Moodle, and What Doesn't

Moodle's backup and restore system is genuinely solid. A course backup saves as an .mbz file, and the Moodle documentation on course restore confirms you can restore that package into a new course, either on the same site or a different Moodle instance, with the option to merge into an existing course or create a fresh one. Site administrators can also schedule automated course backups so nothing is hostage to a single admin's manual habit.

That part is not in dispute. What people get wrong is assuming "it backs up" means "it ports anywhere."

What moves cleanly:

• Course structure, content blocks, and quiz banks (via .mbz)
• User accounts, enrollments, and grade history
• SCORM 1.2 packages, since SCORM is a portable zip format by design
• Completion and gradebook records, if you export before cutover

What does not move cleanly, and this is the part competitors won't tell you:

• SCORM 2004 content. Moodle's own documentation states plainly that SCORM 2004 "is not supported in Moodle" at a native level — some packages appear to work because parts of the API were implemented years ago, but development stopped and tracker bugs against it are closed as "won't fix." If your content library is SCORM 2004, you need a third-party player (Rustici's SCORM Cloud is the standard workaround) or a re-export at the authoring-tool level before migration. What SCORM does and doesn't prove for an audit is covered in LMS compliance requirements.
• Plugin-dependent features. If your gradebook, attendance, or custom activity types depend on a community plugin, that behavior does not travel with the .mbz file. You're rebuilding the logic, not just moving data.
• Custom CSS and theme hacks layered onto a Moodle theme over the years. These get rewritten, not migrated.

Say it plainly: these records export; these relationships with plugins still need rebuilding. That's a different claim than "there are no exports," and it's the honest one.

What Actually Migrates From LearnUpon, and What Doesn't

LearnUpon is a different animal. It's a well-built SaaS platform aimed at mid-sized to large organizations, and its own documentation confirms built-in data tools: you can download all user data in a portal, export course settings, and pull question pools from exams. Your learner records and course metadata are not hostage to the platform.

What doesn't travel: LearnUpon's dynamic rules, its automation workflows, and its branding setup. Those are configured inside LearnUpon's admin interface and have no standard export format, because they're platform-specific logic, not data. You're not losing them so much as recreating them in whatever system comes next, whether that's another SaaS platform or a custom build.

On cost: LearnUpon does not publish pricing on its own site. Every plan requires a sales conversation, and third-party buyer guides consistently report minimum annual contracts in the $10,000-$15,000 range, climbing well past that as learner counts grow. That's not a criticism of the product. Opaque enterprise pricing is normal for platforms built around multi-portal, partner-training use cases. It does mean you can't do a clean cost comparison without actually requesting a quote, so if you're building a business case for leadership, get the real number before you present one.

Why Teams Actually Leave Moodle

Set aside the generic "it's old and clunky" framing. The specific, recurring reasons teams cite:

Plugin fragility. Moodle's extensibility is also its maintenance burden. When core updates, third-party plugins frequently break, and someone on your team becomes the de facto Moodle sysadmin whether they signed up for that or not.

Hosting math that looks free and isn't. MoodleCloud's own plans overview confirms it's a SaaS product with fixed user and storage quotas per tier, paid annually. Self-hosting avoids the subscription but shifts cost to servers, security patching, and the admin time to keep it all running. Either way, "free and open source" undersells what a production Moodle instance actually costs to run well.

Academic bones, commercial expectations. Moodle was built for semester-based, course-and-grade academic workflows. When a company tries to bend it into an onboarding platform, a certification engine, or a partner-training portal, the friction shows up in how much configuration and plugin-stacking it takes to get there.

Why Teams Actually Leave LearnUpon

Per-learner economics stop working at scale. LearnUpon's pricing model charges by active learner. For partner or customer training programs where your "learner" count scales with your customer base, the LMS bill scales right alongside your growth. That's this plan adds this charge at this usage, not some abstract "SaaS taxes everything" claim.

Reporting depth versus reporting flexibility. LearnUpon is strong at the compliance question: who did what, and when. Teams that need to slice that data in non-standard ways for operational or sales-enablement purposes often find themselves exporting to a BI tool anyway, which raises the question of why the LMS layer exists at all for that use case.

Workflows the platform wasn't built for. LearnUpon's model centers on content delivery with discussion boards attached. If your training program depends on structured peer review, live cohort cadences tied to a CRM, or gamified progression logic specific to your industry, you're working around the platform rather than with it. SkillBuild is one version of that end state: a platform a home-services company uses to train its own technicians and prove who is qualified, which is not a job a course catalogue was built for.

How Long Does a Moodle or LearnUpon Migration Actually Take?

This varies more by scope than by source platform. A contained instance — one organization, a few hundred courses, no deeply custom plugin stack — can move in a single quarter. A large, plugin-heavy Moodle instance with years of institutional customization is a different project entirely, and treating it like a weekend job is how migrations blow their timeline.

For a custom LMS build (not just a lift-and-shift), a focused MVP generally lands in the 8-20 week range depending on scope: course delivery, assessments, and a clean admin dashboard is a faster build than a platform that also needs certification tracking, SCORM playback, and a partner-facing portal.

Build vs Buy: What the Math Actually Says

We go deeper on this in build vs buy: the real LMS cost math, and on scope pricing in what a custom LMS actually costs. Here's the short version, and it's the part most "switch to custom" content gets dishonest about: custom is not automatically cheaper. Here is the arithmetic with our actual pricing rather than an industry range. Take a mid-size rebuild at $40,000 plus roughly 20% a year to run it, so about $64,000 across three years. Against a SaaS plan at $8 per learner per month, that breaks even at roughly 220 learners sustained over three years. Below that, SaaS wins on pure cost and you should stay put. This is a model, not a quote for your org — your real figure moves with your feature list and your headcount, so get it scoped properly before you build a board deck around it.

That means: if you're a creator validating your first course, start on a SaaS platform like Teachable or Thinkific. If you're a mid-sized training company and your needs fit inside a well-built existing option, something like LearnDash on WordPress can beat a custom build outright on both cost and time to launch. Custom only pays for itself when the platform does something SaaS genuinely cannot, your training product is the business (not a side feature of it), or you've already hit the ceiling on a specific, named limitation of your current platform, not a vague feeling that you've "outgrown" it.

The honest reasons to build custom: control over the exact learner workflow, true data portability going forward, an exit path that doesn't depend on a vendor's roadmap, and support for a process your current platform cannot be configured to do. "You're being ripped off by your LMS" is not one of them, and that framing falls apart the moment someone runs the numbers.

What a Clean Migration Plan Actually Looks Like

1. Export everything before you touch anything. Full .mbz backups from Moodle, full data exports from LearnUpon. Do this even if you're not sure you're migrating yet.
2. Audit for plugin and automation dependencies. List every Moodle plugin or LearnUpon dynamic rule your current workflow actually depends on. This becomes your rebuild spec, not an afterthought.
3. Decide the content standard. If your SCORM library is 2004-era, decide now whether you're routing it through a SCORM Cloud-style player or re-authoring key courses for a native format.
4. Pilot with one course cohort before full cutover. Run the new system alongside the old one for one training cycle. This catches gradebook and completion-logic mismatches before they affect your whole learner base.
5. Keep the old instance read-only for a defined window. Ninety days is a reasonable default. You will need to reference historical records at least once during that window.

We have run this migration path before, and the plugin-and-automation audit in step two is where most of the surprises live. If you want a second pair of eyes on yours before you commit, that is what the first call is for.

Frequently Asked Questions

Does moving off Moodle mean losing all my course history?

No. Course content, grades, and enrollment history export cleanly through Moodle's .mbz backup format and restore into a new system or a fresh Moodle instance. What you lose is plugin-specific behavior and any custom theming, which has to be rebuilt rather than migrated.

Can I export my data out of LearnUpon if I decide to leave?

Yes. LearnUpon's own documentation confirms built-in tools to download user data, course settings, and exam question pools. What doesn't export is platform-specific configuration like dynamic automation rules and branding setup, since those are logic, not data.

Is a custom LMS always cheaper than Moodle or LearnUpon long-term?

No, and be skeptical of anyone who claims otherwise. On our pricing, a mid-size rebuild breaks even against an $8-per-learner plan at roughly 220 learners sustained over three years. Below that, staying on Moodle or a well-chosen SaaS platform is the financially smarter call, and we will say so.

How long does a Moodle to custom LMS migration take?

A contained instance with a limited plugin footprint can move in roughly a quarter. A large, heavily customized Moodle deployment takes meaningfully longer, since the plugin audit and rebuild work scales with how many years of customization you're unwinding.

What happens to SCORM 2004 content during a Moodle migration?

It needs special handling. Moodle's own documentation confirms native SCORM 2004 support was never completed and development on it has stopped. Content in that format typically routes through a third-party player like SCORM Cloud, or gets re-exported from the original authoring tool in a format your new system plays natively.

Should a small training business even consider a custom LMS?

Usually not yet. If you're still validating demand for your course or program, a SaaS platform gets you to market faster and cheaper. Custom builds earn their cost when a specific workflow, integration, or ownership requirement that SaaS genuinely cannot meet is already blocking your growth, not as a first move.

Want a straight answer on whether your Moodle or LearnUpon setup is actually holding you back? Developios builds custom learning management systems for training companies and agencies who've hit a real ceiling, not a hypothetical one. Our build for a State Farm insurance agency, Agency Elite, put training, client performance and revenue reporting in one platform instead of four, across 45+ screens and several permission levels. We took the same ownership-first approach building GED Masters, a certification-tracking platform for a different kind of learner population entirely. If you want your training platform to actually show up when prospects ask AI tools about it, read how we think about that in Get Cited by ChatGPT and Perplexity.