upnoow

Moodle migration · LMS migration

Moodle migration services: change platform without losing your learning history.

Moving from another LMS to Moodle, from an old Moodle to a current one, or from one server to another is delicate work. We plan it, test it on a copy and cut over with a rollback plan, keeping courses, users, enrolments and grades.

Customized Moodle platform shown on a laptop and a phone

10+ years

of experience

50+

projects delivered

Ongoing

support

Custom

development

Three kinds of migration

The word migration covers very different jobs, and each one has its own risks. It helps to identify which one you have before asking for a quote.

From another LMS to Moodle: content, users, enrolments and, when possible, grades are mapped and imported. Some features do not have a direct equivalent and have to be rebuilt.
From an old Moodle to a current one: a version jump that may cross several releases and require intermediate steps and plugin replacements.
From one host to another: same Moodle, new server. It sounds simple, and it is where a wrong path or a missing extension can stop the site.

How we run a migration

We begin with an inventory: how many courses, users and files, which plugins, which customizations, which integrations. That tells us what can move as it is, what needs an alternative and what should be left behind.

Inventory of content, users, plugins and integrations.
Migration to a test copy and review with your team.
Fix of what did not transfer correctly.
Scheduled cutover with a verified backup and a rollback plan.
Post-migration monitoring and adjustment.
Custom plugin development and customizations on Moodle

Custom development

Migration that keeps your history

A migration is judged by what remains afterwards. These are the pieces we take care of most.

  • Courses, users, enrolments and grades carried over with care
  • Replacement or rebuilding of plugins that no longer exist
  • Checks and backups before and after the move

Migrating to build a better platform

Many organizations use a migration to fix long-standing problems: duplicated courses, unused plugins, inconsistent roles and slow pages. We take advantage of the move to clean up, with your approval, so that the new platform starts in better shape than the old one.

If you are also moving to a different kind of platform, such as a broader educational platform with portals and payments, we plan it together with the migration.

What can go wrong, and how we reduce the risk

The most common problems are plugins without a version for the target release, content that depends on custom code, and integrations that stop working after the move. We detect them in the inventory and in the test migration, long before the final date. The rule is simple: nothing reaches your real users until it has been checked.

What goes into the inventory before a migration

A migration estimate is only as good as the inventory behind it. Before moving anything, we list what your platform really contains, because the real size of a platform often differs from what people remember. The inventory covers the number of courses and how many of them are active, the volume of files and the largest ones, the number of users and their authentication method, the plugins in use and which of them are still maintained, the customizations in the theme or in the code, and the integrations with other systems.

With that list we can say what will transfer without effort, what needs a replacement, what is not worth moving and what could take longer than expected. It also gives you a chance to decide, before the work starts, which old courses and inactive accounts can stay behind.

An illustrative project: from another LMS to Moodle

This is a hypothetical example, written to show the shape of a project, and not a client case. A training company has run its courses on a proprietary LMS for years and wants to move to Moodle to stop paying per-user fees and to control its own data. It has around two hundred courses, a few thousand learners and a catalog of certificates that learners may need to download again later.

The project starts by mapping what exists in the old platform to what Moodle offers. Courses are exported and imported in groups, starting with a pilot of five. Learner accounts and enrolments are loaded with a script that we test on a copy. Completion records and certificates are migrated so that nobody loses proof of a course already finished. Features that have no equivalent, such as a specific type of quiz, are rebuilt with a Moodle activity or a small plugin. Both platforms run in parallel for a short period, and the old one is switched off only after the company confirms that everything it needs is in the new one.

Moving between hosts without surprises

Changing the server of a Moodle that already works sounds simple and is a frequent source of unplanned downtime. The new server must meet the requirements of your Moodle version: the PHP version and extensions, the database version, memory and time limits, and the correct path configuration for the web server. A missing extension or a wrong path can leave the site unreachable.

Check of the target server against the Moodle requirements.
Full copy of files, database and the data folder.
Test of the platform on the new server with real data.
Change of the address at a quiet time.
Old server kept intact until everything is verified.

Data protection during a migration

A migration moves personal data from one place to another, and that deserves attention. We limit who has access to the data during the work, move it over secure connections and avoid leaving copies in places where they should not be. When you ask us to, we remove the temporary copies at the end and confirm it in writing.

If your organization works under rules about where data may be stored, tell us at the start. The location of the new server is a decision to take with those rules in mind and not an afterthought.

After the migration: what we check in the first weeks

The first days after a cutover are when small problems appear: a course that restored with a missing resource, a user who cannot log in, a scheduled task that has not run. We monitor the platform closely during this period, handle the reports that come from your team and fix what needs fixing. After a few weeks, we hand over a short report with what was migrated, what was changed and what to keep an eye on.

Many clients continue with a support or managed hosting plan after the migration, so that the new platform starts its life with updates and backups already in place.

Common mistakes in migrations

Migrations fail for reasons that are almost always avoidable:

Not doing an inventory, and discovering plugins or customizations only at the end.
Migrating directly on production, with no test copy.
Underestimating how much old content is really worth keeping.
Switching without a verified backup and a way to go back.
Forgetting to tell users about the change of address or the downtime.
Not checking certificates and completion records, which people rely on later.

Migration timelines and what affects them

How long a migration takes depends mostly on the size and the complexity of the platform. A small site with few plugins can move in a couple of weeks. A large platform with many courses, customizations and integrations takes longer, and the test and review stages are the part that should not be rushed. We give you a calendar after the inventory, with the dates when your team has to review, so that you can plan around them.

We recommend avoiding migrations during peak periods, such as exams or the start of a term. When the date is fixed by something else, we plan the work backwards from it and adjust the scope to make it achievable.

Migrating content that people depend on

Some content has long-term value to learners and must survive the move intact: certificates, completion records, grades and the courses that are still in use. We identify these items in the inventory and verify them one by one after the migration, so that a learner who needs a certificate from three years ago can still download it. Content that is no longer used can be archived and kept available outside the main platform, which keeps the new one light and fast.

Related Moodle services

Managed Moodle: we take care of the server

Server, backups, SSL, security updates and support included. These are some of our monthly plans.

Popular L

US$66 /month

~400 students · ~40 concurrent

Corporativo XL

US$268 /month

~1.500 students · ~150 concurrent

Corporativo Max

US$668 /month

~3.000 students · ~300 concurrent

Elite M

US$944 /month

~5.000 students · ~500 concurrent

See all plans

Frequently asked questions about Moodle migration

Where we work

Ready to take the digital leap?

Tell us your idea and we will show you how to make it happen. No commitment.