A school district stayed with an LMS they hated for three extra years. The migration estimate? $85,000.
Three years of frustrated teachers, confused students, and extra work for IT. Because leaving was more expensive than suffering. That's not a market failure. That's the business model working as intended.
The Scale of the Lock-In Problem
The numbers are ugly.
Inside Higher Ed reports that even smaller schools spend $150,000-$200,000 a year just running their LMS. When they decide to switch, DIY migrations "require at least two years to transition from one system to the next, meaning schools must pay to operate two LMS platforms at the same time." That's $300-400K in dual-platform overhead before you've moved a single course.
Then there's the actual migration work. Budget "$300-$1,500 per course for remediation and accessibility fixes," and a typical school moves about 4,000 courses. Do the math on that and you get $1.2-6 million in course remediation alone.
Suddenly that $85,000 estimate looks like a bargain. The district that stayed three extra years may have actually made the cheaper choice.
How They Keep You
Nobody writes "vendor lock-in" into the contract (though some contracts don't help). The lock-in is practical, not legal.
Proprietary formats. Course content stored in formats that only work inside that platform. Try to export and you get either a raw data dump that requires an engineer to interpret, or a simplified version that strips formatting, rubrics, embedded media, and interactive elements. The content a teacher spent years building effectively becomes the vendor's content.
Export tools that technically exist but don't actually work. Exports that miss metadata. Student records without linked submissions. Grade histories as flat CSV files with no context. Reviewers describe multi-month migration projects that needed custom engineering, not because the new platform couldn't accept the data, but because the old platform couldn't produce it in any usable format.
Integration dependency. Every integration you set up (SIS, gradebook, assessment tools, communication platform) is another thread you'd have to unwind and reconnect somewhere else. The more integrated the platform, the harder it is to leave. Vendors are fully aware of this, which is why they're so eager to help you integrate everything during onboarding.
Institutional knowledge that can't be exported. Over years, teachers build courses, rubrics, feedback templates, workflow customizations. Even if you can export the raw content, the organization (the relationships between materials, the pedagogical logic baked into the course structure) is lost in migration. That's thousands of hours of refinement, gone.
The Part That Doesn't Show Up on a Spreadsheet
Teacher burnout. "Rebuild all your courses in the new system over summer break." That's the ask. On top of everything else. Teachers' recovery time turned into a data migration project.
Continuity gaps. Students using two systems at once during transition. Previous grades, feedback, portfolio work either inaccessible or incomplete in the new platform.
Decision paralysis is the worst effect. When switching costs this much, schools stop looking. They stop going to demos. They stop asking if something better exists. Lock-in doesn't just prevent switching. It prevents thinking about switching.
And it gets worse over time. Each new course, rubric, and year of accumulated student data raises the switching cost further. The longer you stay, the more trapped you are.
What Data Freedom Actually Means
It's not a specific export format. It's a stance.
Export everything, anytime. Assignments, submissions, student records, grades, rubrics, feedback, activity logs. All of it, in standard formats (JSON, CSV, PDF, DOCX), whenever you want. Not "contact support to request an export." Not "available during the cancellation window." Self-service, no restrictions, right now.
Formats other systems can use. A JSON dump with a proprietary undocumented schema is technically an export. It's not practically useful. Standard, documented formats mean your next platform can import the data without a custom engineering project.
No penalty for leaving. Some platforms restrict export access once you cancel, creating a scramble to extract data before the account closes. Your data should be accessible whether you're a current customer or not.
Documented data model. If a technical team can't understand what they're looking at without reverse-engineering the export, portability is performative.
It's Also a Retention Strategy
A platform that makes it easy to leave is saying: "We're good enough that you'll stay by choice." A platform that makes it hard to leave is saying something else entirely.
During your next eval, try these:
- "Can I export all my data right now, during this demo? Show me what the output looks like."
- "What happens to my data if we cancel?"
- "How long did your last customer's migration take?"
- "Do you offer month-to-month, or annual-only?"
The answers tell you whether the vendor is confident in their product or dependent on your inability to leave.
The Opportunity
$85,000 migration costs are an anchor keeping schools tethered to platforms they hate. Any new entrant that makes switching painless (easy import, full export, no lock-in contracts) isn't just offering a better product. They're offering something the incumbents can't: freedom to leave.
And in a market where frustrated customers are publicly, in detail, writing out exactly what they want fixed, that opportunity isn't theoretical. It's sitting in the review section of every app store and software marketplace, waiting for someone to build it.