Howard County Public Schools in Maryland moved to Canvas by Instructure in 2013. More than a decade later, the district runs it across 78 schools for roughly 5,000 teachers and just under 60,000 students.
Getting to that point meant replacing a system every teacher in the district already knew how to use. That's the decision in front of you, and it's the reason LMS migration gets postponed year after year in districts that know they've outgrown their platform.
This guide walks through what migration actually involves: what transfers and what doesn't, what to look for in a new system, how long each phase takes, and the mistakes that cause the most pain. If you're further along and already scoping a timeline, the K-12 LMS migration checklist covers the go-live window in more detail.
What is LMS migration?
LMS migration is the process of moving from one learning management system to another. In practice that means transferring four things: course content and files, user accounts and rostering data, third-party integrations, and system configuration.
What it doesn't automatically mean is that everything comes across intact. Course shells, files, and assignment structures usually transfer well. Historical grades, student submissions, and discussion threads are harder, and in most cases come through via your student information system.
Districts typically start looking because their current system can't keep up, whether that's because of an integration it doesn't support, a teacher experience that drives people to work around it, or the need for a more connected education ecosystem.
What should K-12 districts look for in an LMS?
Five criteria show up in a platform that a district will use for a decade. Use them to evaluate a new system and to audit the one you have.
1. Supports learning everywhere
Look for an LMS that enhances teaching across in-person and remote settings. Your system should give educators the flexibility to deliver high-quality instruction no matter where learning happens.
2. Scales with growth and change
As your district's needs change, the system has to change with it. That means real support for the interoperability standards districts already run on: LTI 1.3 for tool integration, and OneRoster or a direct SIS sync for rostering. Ask a vendor which specific standards they certify against, not just if they integrate with certain tools.
3. Delivers actionable insights
Your LMS should help you understand what's working and what needs adjustment. Administrators, instructional leaders, and teachers need clear data on student engagement and learning progress to guide better decisions. Also consider an LMS that thinks beyond instruction and allows for seamless assessment experiences.
4. Simplifies assessment and feedback
Assessment is a critical part of student learning. A strong LMS enables easy formative and summative assessments, rubrics, auto-grading, and timely feedback, which all save teachers time and can support student growth. Consider an LMS that integrates seamless with an assessment management system (AMS).
5. Fosters a supportive community
Great technology is backed by a great community. An LMS with active user groups, professional learning opportunities, and a vendor that feels like a part of your team helps educators feel confident and connected.
If your current system falls short on two or more of these, migration is worth scoping.
What are the phases of an LMS migration?
Per one migration partner, plan on four to six months from decision to go-live, including teacher training. Put concretely: an August launch should be in ramp-up mode by February.
Phase | Typical duration | Who owns it | Key deliverable |
|---|---|---|---|
Pre-migration | 4 to 6 months before go-live | District leadership, IT, and curriculum | Content audit and platform decision |
Migration | 2 to 4 weeks running both systems | IT and LMS partner | Course transfer, integration testing, and pilot |
Post-migration | First 90 days | Instructional coaches and PD team | Training delivered and adoption tracked |
Districts consistently underestimate the content audit. A system that's been running for eight years accumulates thousands of course shells, most of them dead. Deciding what to retire is slower than moving what's left.
Most districts migrate over the summer, for the obvious reason: no active grading period to disrupt, and teachers have time for training before students return. That makes summer capacity scarce on the vendor side, so districts that decide in March might get a smoother June than districts that decide in May.
How to make LMS migration easier for K‑12 schools
The data moves more easily than the people do. Districts that get this right run migration as a professional learning project with a technical component underneath it, and they staff it that way: curriculum and instructional leadership own adoption, IT owns the transfer, and both answer to the same timeline. District risk running two systems in parallel a year after go-live if they just hand the whole thing to IT and schedule training for the week before launch.
Five mistakes that cost districts the most:
- Migrating everything. Moving unused course shells wholesale means teachers open the new system and find the same clutter they had before. Audit first.
- Skipping the accessibility review. Content that was non-compliant in the old system is still non-compliant in the new one, and migration is the cheapest moment to fix it.
- Underestimating training. Only 15% of educators rated the training they got on their district's LMS as "very effective," according to an EdWeek Research Center survey of more than 1,000 district leaders, principals, and teachers. In a companion survey the same summer, more than half said their ed-tech professional development was mostly one-time events with little or no follow-up coaching. Migration is the moment to break that pattern, because you're retraining everyone anyway.
- Testing integrations last. SIS rostering, single sign-on, and third-party tools break in ways that only surface under real load. Test them in the pilot, not the week before launch.
- Piloting without collecting feedback. A pilot should be more than a scaled up demo. Get the ins and outs of what a pilot should actually produce here.
Five steps for a smooth LMS migration
Now that we've explored what to avoid, let's take a closer look at what you can to do to be successful. Again, moving to a new LMS is a lot like house hunting and moving. Your wish list and process may vary and ultimately, you're in charge of what success looks like.
1. Set a clear vision
Identify district goals and how your new LMS will help achieve them. Survey staff and students to gather insights into what’s working and what’s not with your current system.
2. Build a cross-functional team
Form a committee that includes teachers, administrators, instructional coaches, IT staff, and other stakeholders. Their diverse perspectives will help ensure the chosen system meets everyone's needs.
3. Develop a migration plan
Establish a clear timeline, define roles and responsibilities, and communicate regularly. Flexibility is key—be ready to adjust your plan as needed to keep LMS migration on track.
4. Promote buy-in and excitement
A district-wide communications campaign does more for adoption than any feature in the platform. Virginia Beach City Public Schools, which serves around 65,000 students, ran an all-day summer workshop called Camp Canvas in June and August of 2022. More than 1,400 educators attended across the two sessions. Demos, info sessions, and hands-on training work better when they're an event people opt into rather than a mandate they sit through.
5. Prioritize partnership
We can't emphasize this enough: a trusted LMS partner offers more than software—they provide long-term support, migration services, training, and opportunities to collaborate with other districts. Join user groups and take advantage of online communities to continue learning.
Before you start
The short version: set your goals and success metrics, audit your existing content, choose a platform with input from across the district, build a timeline and a communications plan, test your integrations in a pilot, train everyone who touches the system, and track adoption after launch.
For the detailed version, including what has to be finished at each point in the go-live window, use the K-12 LMS migration checklist.
What if you're ready to start your LMS migration?
Whether you're actively talking to vendors or just mapping out what a change would involve, the work in front of you is mostly the same: audit what you have, decide what's worth keeping, and plan for the training long before you plan for the launch.
If you want to see what migration would look like for your district, request a demo or start with the K-12 LMS Buyer's Guide.
Frequently asked questions
What data can be migrated to a new LMS? Course content, files, assignment structures, and user accounts transfer reliably. Historical grades, student submissions, and discussion threads often migrate over via SIS. Confirm what your state's records retention rules require before you decide what to leave behind.
When should a district migrate? Summer, in almost every case. It avoids disrupting an active grading period and gives teachers time to train before students return.
Do teachers have to rebuild their courses from scratch? No. Course content and structure transfer during migration. Teachers should expect to spend time reorganizing and cleaning up rather than rebuilding, which is one more reason the pre-migration content audit matters.
How does SIS rostering work after migration? Through a direct SIS integration or a rostering standard such as OneRoster, often by way of Clever or ClassLink.
Can you migrate from Schoology, Blackboard, Google Classroom, or Moodle to Canvas? Yes. Check out stories by other districts who have done it.
