18 Sep Moving from Moodle to Moodle Workplace: what changes, what it costs, and what the upgrade path actually involves
Ask what Moodle Workplace costs, and you will usually get an answer about licensing. It is a fair answer to the question asked, and it describes the smaller half of what you are buying.
And while it’s the licence that appears on an invoice, the larger part of the process is the design work that happens once the code is in place, because Workplace does not simply add features to Moodle. It asks you to describe your organisation to the system: who reports to whom, which roles exist, what has to be completed by when, and what should happen automatically when someone’s circumstances change. Answer those questions well, and the administrative load on your L&D team falls permanently. Answer them badly, and you have a more complicated Moodle.
This is what the upgrade path involves, in the order it happens.
The code upgrade is the straightforward part
Most people imagine something more dramatic than it is. Moving a standard Moodle site to Workplace is a base upgrade: maintenance mode on, a full database backup taken, and the standard Moodle code directory overwritten with the Moodle Workplace distribution package.
That is it, technically. Your courses, users, and completion history live in the database and stay where they are.
Workplace is built directly on the Moodle LMS core, which is the part most administrators are relieved to hear. The interface your team already knows does not change out from under them, and the architecture underneath is the one your platform has been running on for years. You are keeping the foundation and adding a layer to it, not replacing what works.
However, there is a fundamental constraint worth stating clearly upfront. Moodle Workplace is licensed software available only through Moodle Certified Partners and Service Providers, so this is not an upgrade you can perform yourself with a simple download.
The plugin audit is where the first real decisions appear
If you have been running standard Moodle for any length of time, you have almost certainly built some additional capabilities out of plugins. Reporting is the usual one. Compliance tracking is the other.
Workplace has native frameworks for both, and they are more robust than the plugin arrangements most sites have assembled over the years. That is the good news. The less comfortable news is that those plugins need auditing before you go live, and several will be disabled or replaced rather than carried across.
This is the part of the upgrade buyers worry about most, so it is worth being specific. You are not losing the capability. You are moving it onto a supported framework and, in most cases, retiring a workaround that somebody built under pressure three years ago and hasn’t been touched since. But it does mean someone has to work through your plugin list and decide what Workplace now does natively, what still needs a plugin, and what can simply go. Doing that before the upgrade is considerably cheaper than discovering it afterwards.
Five things you then have to design
In standard Moodle, users sit in flat lists or site categories. Workplace expects a hierarchy, and you have to build it.
Your organisational structure
In standard Moodle, users sit in flat lists or site categories. Workplace expects a hierarchy, and you have to build it.
That means designing position frameworks, covering the roles that exist in your organisation, and department frameworks, covering its functional divisions. It then means assigning managers, which is the step people underestimate. Manager assignment is not simply an org chart exercise. It determines who can see whose progress and who can approve training requests, so getting it wrong creates either a permissions problem or a governance one.
Done properly, it also changes who has to ask you for things. Managers gain oversight of their own teams and can pull their own reports without holding system administrator permissions, which is usually the point at which the central L&D inbox stops being a bottleneck.
Multi-tenancy, if it applies to you
If you run subsidiaries, franchise branches, or deliver training to external partners and clients, you’ll need to configure tenants: separate environments inside a single installation, each with its own theme, logo, login URL, and interface.
You also need to delegate administration. A tenant administrator gets local control over their own users without visibility of global system settings, which is the mechanism that makes it safe to give a client organisation genuine self-service rather than routing every request through your team.
Not every organisation needs this. If you do, it is usually the single strongest reason you’ve decided to be on Workplace at all.
Programs and certifications
Workplace changes how courses relate to one another. Programs let you sequence them, so course B is not available until course A is complete. Certifications handle the compliance side, with expiry intervals, valid periods, and automated recertification windows, so somebody who certified twelve months ago is re-enrolled without anyone having to remember.
If your current arrangement involves a spreadsheet tracking who is due what and when, this is the section that replaces it.
Dynamic rules
This is where most of the efficiency gain sits, and where a significant amount of the configuration time goes.
Dynamic rules are conditional statements the platform acts on autonomously. If a user’s department changes to Sales, enrol them in the sales onboarding program. If someone misses a compliance deadline, notify the learner and email their manager. If a certification is completed, issue the certificate and record it against their profile.
Written well, these remove a substantial amount of manual administration permanently. Written thoughtlessly, they generate notifications nobody reads. The work here is not simply building the rules. It is deciding which manual tasks are worth automating and which are better left to a person who can exercise judgement.
Reports and dashboards
Workplace includes a drag-and-drop report builder, which needs configuring rather than simply switching on. In practice, that means constructing the queries your L&D and HR teams actually need, then scheduling them so progress and compliance reports arrive in team leaders’ inboxes without anyone running them manually each month.
How the migration runs
At Accipio, the sequence we follow is the same one we use for any migration. Discovery, planning, a dry run, then go live.
Discovery is the stage worth explaining, because it does three jobs rather than one and most organisations arrive expecting only the second.
The first is establishing where you actually are. What version you are running, what has been customised, which plugins are load-bearing and which are vestigial, how your data is structured, and what condition your integrations are in. This is factual work and it is usually quicker than people expect, but it has to happen before anything else is credible.
The second is the one everybody anticipates: what is not working. The reports that take two days to assemble. The compliance chasing that falls to one person. The client who wants their own branded environment and cannot have one. These are the reasons you started looking, and they matter.
The third is the one that actually shapes the build, and it is about direction rather than difficulty. Where do you want this platform to be in two years? Are you planning to open the catalogue to external customers, or bring three subsidiaries onto one system, or move from tracking completions to evidencing competence? Are you expecting user numbers to double? Is there a regulatory change coming that your current setup will not survive?
That third conversation is what determines how the employee role frameworks, the tenant structure, and the dynamic rules get designed. Configure Workplace around today’s problems and you will have solved them, and you will be reconfiguring in eighteen months. Configure it around where the organisation is heading and the same work lasts considerably longer.
Discovery also settles one strategic question: whether to migrate and advance, moving the site as it stands and improving it afterwards, or to take a big bang approach and go live on a redesigned platform. Neither is automatically right. Organisations with a hard deadline or a governance requirement usually prefer the first. Organisations treating the upgrade as a chance to fix things they have tolerated for years usually prefer the second.
Planning then scopes the work end to end and agrees timeframes. The dry run builds your new platform on a staging site, with your data in it, so you can test the rules and structures against real cases before anything goes near your live environment and revise them while revision is still cheap. Go live repeats the tested process.
What it costs
Three separate things, and they are worth keeping separate.
The migration itself is free. That is genuinely the case for the great majority of upgrades we perform, and it is a standing position rather than a promotion. The honest exception is a site carrying heavily bespoke development that has to be rebuilt rather than moved, which occasionally attracts a charge. If that applies to you, you will find out at discovery rather than at invoice.
The licence is not free. Moodle Workplace is a subscription sitting on top of the managed service, priced by user band. Our pricing is published in full, so you can find your band and work out your own number without needing a conversation first.
The configuration is not free either, and it is the part that genuinely varies. An organisation with a simple hierarchy and no multi-tenancy is a different piece of work from a professional body running six tenanted client environments with automated recertification across all of them. We scope it at discovery and quote against our implementation packages rather than pretending a single figure covers both cases.
Choosing who does it
Most technology decisions come with a long list of suppliers. This one does not.
Moodle Workplace can only be implemented and supported by a Moodle Premium Certified Partner, the highest tier of Moodle HQ’s partner programme. That is an access restriction built into the programme rather than a commercial preference, and it is assessed at country level. In the UK there are four Premium Certified Partners. Accipio is one of them.
A shortlist of four is a manageable evaluation, and it is worth doing properly rather than assuming the tier alone settles it. The questions that actually separate one Premium Partner from another are these.
A shortlist of four is a manageable evaluation, and it is worth doing properly rather than assuming the tier alone settles it. The questions that actually separate one Premium Partner from another are these.
Who does the configuration work, and have they done this upgrade before? The five design decisions above are where the value of Workplace is either realised or wasted. Ask to speak to the person who would run your discovery, not the person who would sell you the project.
What happens to your code? Some partners configure what the platform offers. We modify open source at source level, which means when Workplace does not do something your organisation needs, the answer is not automatically no.
What does the ongoing relationship include? Our fully managed service covers hosting, support, maintenance, and free upgrades as new versions are released, alongside quarterly enhancement workshops. A platform that is two major versions behind is a platform whose upgrade has been quietly deferred, and that is a question worth asking of anyone you shortlist.
How quickly do you get a real answer? We aim to give a meaningful response to a support ticket within ten minutes, and most tickets are resolved within twenty-four hours. Ask for numbers rather than adjectives, from all four.
What can you see before you commit? Our pricing is published across every user band. Migration is free. You can work out most of your own answer before you speak to anyone, which is deliberate.
We are also a Platinum Totara Alliance Partner, ISO 27001 and ISO 9001 certified, and hold Cyber Essentials Plus. Those matter more in some procurement processes than others, and you will know which yours is.
Where to start
The useful first conversation is not about Workplace features. It is about what your L&D team does manually every month that it should not have to, and what you want the platform to be doing in two years that it cannot do now. Those two lists together are the actual brief, and they are also the honest test of whether the upgrade is worth it for you.
Some organisations have that conversation and conclude standard Moodle serves them perfectly well. That is a legitimate answer, and it is considerably better reached before an upgrade than after one.
If you want to talk it through in more detail, bring us your LMS challenges and we’ll walk you through what a move would actually mean for you.