The Vendor Lock-In Nobody Budgets For: Exit Costs in School EdTech Contracts

Every school EdTech budget has a line for buying. Almost none has a line for leaving. That omission is where the largest hidden costs of school technology sit. A platform that is easy to adopt can be very expensive to exit, and by the time a school discovers this, the contract has usually renewed.

I wrote about the pedagogical version of this problem in The LMS Trap. This piece is about the contractual and technical side: the exit costs that never appear in a procurement spreadsheet.

Where exit costs hide

• Data portability. Can you export student records, grades, assessments and learning history in a usable, documented format? Or only in a vendor-specific file, or a PDF?
• Content ownership. Lessons, question banks and resources that teachers built inside the platform may be hard to extract, or may not be yours at all under the terms of use.
• Integrations. Every link to your student information system, single sign-on and finance tools is built around the vendor. Replacing the vendor means rebuilding each one.
• Retraining. Teachers and students have built habits around the interface. Moving costs time and goodwill.
• Data retention and deletion. What happens to student data after the contract ends, and who confirms it has been deleted?
• Renewal escalators. Price rises written into multi-year terms, or auto-renewal clauses with short notice windows.
• Bundling. Features packaged so that dropping one module means losing the discount on the rest.

Why schools miss it

1. Procurement focuses on the first year. Demos, pilots and introductory pricing are all about getting in.
2. The people who sign are not the people who migrate. By the time an exit is needed, the original decision-makers may have moved on.
3. Exit terms feel negative to raise. Asking about leaving a vendor you have just chosen seems awkward in a sales conversation.
4. Nobody maps dependencies. The school cannot tell how many processes rely on the platform until it tries to remove it.

The outcome is a school that does not stay with a vendor because the vendor is the best, but because leaving is too hard.

The equity dimension

Lock-in hits smaller and lower-resourced institutions hardest. A large group can negotiate custom terms and fund a migration team. A small school usually accepts standard terms and has one person handling every system. When prices rise or support falls, the small school has the least leverage and the fewest alternatives.

There is also a student-data dimension. Records that cannot be exported cannot follow a child to a new school or be returned to a family. That makes the student, not the institution, the one who is locked in.

A pre-signing exit checklist

School leaders and their IT teams can ask these questions before any contract is signed.

1. Can we export everything? Ask for a sample export of real data in an open, documented format and check that it can be opened elsewhere.
2. Who owns the content? Confirm in writing that teacher-created material remains the school’s property and can be taken out.
3. What are the termination terms? Look at notice windows, auto-renewal clauses and any fee for early exit.
4. What happens to our data afterwards? Require a defined deletion timeline and written confirmation.
5. How is price protected? Seek caps on annual increases and clarity on what triggers re-pricing.
6. Which standards does the product support? Prefer vendors that support common interoperability standards for rostering, content and sign-in, so replacing one part does not mean replacing everything.
7. What does migration cost? Ask what help the vendor will provide if you leave, and at what price.
8. Can we test the exit? During a pilot, run a trial export and a trial import into another system.
9. Is the data residency compliant? For GCC schools in particular, check where data is stored and what local rules apply, as I discussed in Cybersecurity Compliance for GCC Businesses.

Record the answers in a vendor file that survives staff turnover. The vendor relationship from the other side is covered in What International School IT Leaders Wish Vendors Knew.

The question for your next procurement meeting

If we wanted to leave this vendor in two years, what would it cost, how long would it take, and who would do the work? If nobody can answer, the price on the quote is not the real price.

Related Reading

• The LMS Trap
• IT Budgeting for International Schools
• Build vs Buy Software
• Why Your LMS Implementation Failed