Moodle development and integration
Moodle already does courses, enrolment, assessment and the reporting an auditor asks for. The real question is whether your problem is running that administration, or building a learning experience that is itself the product. Those two answers lead to very different projects.
01Capabilities
Where Moodle work actually goes
The work divides cleanly into extending it, connecting it, upgrading it and getting evidence out of it. All four sit inside our LMS development work, and the third is what people arrive with most often.
- Plugins
Course formats, question types and grading rules
Built as plugins, so that upgrading stays possible. Anything that reaches into core or into a theme to do its job is a decision to stop upgrading, whether or not anybody describes it that way at the time.
- Access
Getting people into the right course
Single sign-on, enrolment synchronised from an HR system or a CRM, and results pushed back to whatever reports on them. Most support load is somebody not reaching the course they were enrolled on, which is an integration problem, see platforms development and integration.
- Upgrades
An estate that has drifted a long way from stock
Old versions, a forked core, business logic living in a theme, and plugins whose upstream disappeared years ago. Getting that back onto a supported footing is closer to legacy modernization than to learning-platform work.
- Evidence
Who completed what, and when it expires
Past a certain point the answer is getting the data out of Moodle and into something built for reporting, see data engineering, rather than installing another report plugin. Evidence that exists only as a screenshot somebody takes each quarter is not evidence.
02Fit
Configure the platform, or build the thing?
This argument usually gets settled by whoever is in the room. The actual dividing line is narrower than that: Moodle wins when learning administration is the problem, and a bespoke build wins when the learning experience is the product. Both answers are common, and confusing them is expensive in both directions. Each row is the call we would make, and two of them link to the unicrew service that takes it on.
| Your situation | What we recommend |
|---|---|
| Formal courses, enrolment, assessment, certification and compliance reporting | Use MoodleThe standards work alone, SCORM, LTI and xAPI, is worth more than a bespoke build would deliver in its whole first year. |
| Learning is the product, and how it works is your differentiator | Build insteadSee LMS development and custom software development. Adaptive paths and your own commercial model mean fighting Moodle's assumptions every sprint. |
| Learning has to sit inside your own product, wearing your own interface | Keep the scope narrowMoodle behind its web services can work when the scope stays narrow. A themed Moodle pretending to be your product satisfies nobody, and the theme becomes the thing that blocks upgrades. |
| A handful of internal courses and a small team to run them | A hosted platformSelf-hosting is an operational commitment: servers, upgrades, plugin currency, backups. A hosted platform costs less in total at that scale, even at a worse licence price. |
| An existing Moodle with a forked or hand-patched core | Un-fork firstA modified core is almost always why upgrades stopped. Every month of new work laid on top makes undoing it more expensive, and nothing else is durable until it is undone. |
| You want AI tutoring or content generation bolted onto it | Keep it outsideBuild it as a service beside Moodle with its own evaluation, see AI integration. Then it can change or be removed without touching the platform that holds your compliance records. |
Scope
What we own here is that judgement and everything downstream of it. Whether Moodle fits the problem you actually have. What each extension we write costs you at the next upgrade. unicrew has been building custom software since 2012, with 100+ senior in-house engineers across six countries. We work under an ISO 27001:2022 certified information-security management system. If Moodle fits and the bespoke platform you were planning does not, we build on Moodle.
03Delivery
How we open up an inherited Moodle
Inherited Moodle is the usual case, and it is almost always further from stock than it looks. This is the order we work in.
- Find out how far it has drifted from stockA diff against the stock release, a plugin inventory with upstream maintenance status, and whatever is living in the theme. Until those three exist, any upgrade estimate is a guess, so we produce them before we estimate.
- Move customisation into pluginsBehaviour pulled out of core edits and theme hacks into plugins we can version and test through the same QA and test automation practice as our own builds. This is the step that turns an estate frozen on an old release into one that can be upgraded on a schedule.
- Fix sign-in and enrolment before featuresIdentity and enrolment sync come before any new activity type, because that is where the support tickets and the abandoned courses come from. A learner who cannot reach the right course has no opinion about your question types.
- Get the completion evidence out of the databaseCompletion, expiry and the evidence behind both, extracted into a reporting layer and verified against the source rather than trusted. That is what makes an audit a morning's work instead of a fortnight's.
04Stack
What a Moodle estate runs on
The language it is written in, the two databases it supports, and the system its public site usually sits in. Each has its own page.
05Questions
What people ask before committing to a learning platform
What we get asked before anybody commits to a platform, answered as we would on a call.
Yes, and on an established estate that often works well, because your people know the courses and the learners. Our engineers build extensions as plugins, so Moodle stays upgradable: an architect outside the delivery team reviews how each customisation is structured, and work goes through the same QA practice as our own. Team extension is managed teams; an outcome is web development.
Ask whether learning administration is your problem or the learning experience is your product. If you need enrolment, assessment, grading, certification and an audit trail, Moodle already does all five and the standards support is a real head start. If your differentiator is how the learning itself works, build it, because on Moodle you spend every sprint pushing against decisions made for a different audience.
Yes, through its web services, and it is reasonable when Moodle is the engine and your product is the experience. Be clear about the cost: you take on the API surface, version compatibility, and features users can see in stock Moodle but not in yours. It works best when the scope stays narrow, courses and enrolment and results, and worst when you try to reproduce everything.
Usually yes, and how hard depends almost entirely on whether the core was modified and how many plugins have no maintained upstream. The first job is a diff against stock and a plugin inventory, because those two determine everything else. The effort figure comes once we have seen them. What we do promise is a rehearsed upgrade with a rollback, not a weekend attempt on production.
A scoping call with an engineer. For an existing estate we ask for the version, the plugin list and read access to the code, because a modified core is the single fact that changes every recommendation. What comes back is written: whether to extend, upgrade or move, and what we would fix first in each case. Most engagements start within two to four weeks.
Three shapes, and which fits depends on how settled the scope is. Time and materials is billed hourly and quoted per project, which suits work still moving. Fixed price is outcome based, offered once the first read is done, because a fixed number on a platform nobody has opened is a guess with a contract around it. Team extension is billed monthly per engineer.
Extending Moodle, or wondering whether to build instead?
Tell us what the courses have to do and what has already been customised. You get a straight recommendation, Moodle or a bespoke build, decided by what the courses need.