How to migrate your Moodle to a new provider without losing data
Migrating providers is one of the tasks that generates the most anxiety for anyone who manages an institutional Moodle — and rightly so: a mistake in the process can mean losing entire courses, grade histories, or even teacher and student access from one hour to the next. The good news is that, with planning and a bit of discipline, the migration can be smooth and practically unnoticeable to those using the platform day to day.
1. Take a complete inventory before anything else
Before moving a single line of data, list everything that needs to be migrated: the database, the moodledata folder (uploaded files, images, documents, generated certificates), custom plugins, custom themes, email/SMTP settings and integrations with other systems (if any). An incomplete inventory is the most common cause of the famous "I forgot to migrate that" — discovered precisely after the old site has already been shut down, with no easy way back.
2. Choose a low-usage window
Migrations should happen outside class hours and, whenever possible, outside exam or assignment-submission periods. Weekends or late nights tend to be the ideal moment — this minimizes the impact if something takes longer than expected, and leaves room to fix any surprises without anyone noticing during business hours.
3. Generate a full backup (and keep a separate copy)
Even migrating with the utmost care, always keep a complete backup of the original environment stored in a separate location — outside both the old and new providers. This is your "plan B" if something goes wrong during the process, and it only has real value if it can be accessed independently of either provider involved in the migration.
4. Migrate the database and moodledata together, at the same time
A common mistake is migrating the database at one point and the moodledata folder at another, with a time gap between the two processes. If a student uploads a file during that gap, the database record will point to a file that simply doesn't exist in the new environment — a hard error to trace later. Treat both as a single unit, migrated at exactly the same moment, with the site in maintenance mode during the transition.
5. Test in a parallel environment before switching DNS
Whenever possible, bring the migrated Moodle up at a temporary address — before pointing the final domain to it — and run a full check: teacher login, student login, assignment submission, grade posting, certificate generation, automatic email sending. Only switch the DNS after absolutely everything has been validated and is working as expected.
6. Communicate the change in advance
Even in a technically perfect migration, it's important to warn teachers and students about possible temporary instability during the cutover, with an expected date and time. This avoids unnecessary support tickets and frustration from people who simply didn't know that scheduled maintenance was happening at that moment.
7. Monitor closely for the first 48 hours
After the cutover, closely track the first two days: overall performance, automatic emails being sent correctly, uploads working without errors, external integrations (if any) responding normally. This initial period is when any residual migration issue tends to surface — the sooner it's identified, the faster it gets resolved.
8. Document the entire process as it happens
Write down every step taken, every setting adjusted, every decision made during the migration. Besides helping diagnose problems later, this documentation becomes valuable material for the next migration — because, sooner or later, it will probably happen again.
9. Always have a defined rollback plan
Before starting, clearly define: if something goes seriously wrong, what's the criterion for going back to the old environment? Up to what point in time is that still possible? Having this answer defined before the migration begins prevents rushed decisions under pressure, in the middle of an unexpected problem.
You don't have to do this alone
A well-executed migration depends on accumulated hands-on experience, not just following a generic checklist. Providers specialized in Moodle hosting have already been through dozens of migrations and know how to anticipate problems before they happen — often handling the entire technical process so your team only needs to worry about notifying users of the change.
Ready to give your Moodle more stability?
LMSHost offers Moodle hosting with high availability, daily backups and specialized support — the right size and the right price for your institution. We're in pre-launch with 50% off for 6 months for anyone who signs up now.
