The hidden cost of legacy data integration in higher education…and how university IT leaders can work out their own.
In almost every university and college, enrolment and registration are the annual stress test for the systems working behind the scenes. For a few intense weeks each year, the integrations that move data between your student records system, your VLE, your finance, HR and CRM platforms are pushed harder than at any other time. Most of the time nobody thinks about them. They simply work. Until they don’t. Or until the person who understands them hands in their notice.
For the IT leaders responsible for keeping all of this running – CIOs, CTOs and heads of IT – the real risk usually isn’t a dramatic, visible failure. It’s a cost that has never been fully added up, because it never arrives on a single invoice. And it matters more than ever: in the Office for Students’ most recent financial sustainability report, more than a third of providers (35.8%) reported a deficit for 2024-25, with the regulator warning that finances remain under continued pressure (Office for Students, May 2026). When budgets are that tight, anything running inefficiently in the background deserves a second look. So it’s worth taking a clear-eyed look at what legacy integrations quietly cost higher-education institutions, and where those costs might be hiding in your institution.
A legacy integration is, by its nature, invisible when it’s healthy. There’s no dashboard flashing red, no line in the budget headed “integration risk.” The cost is real, but it’s spread thinly across people, risk, staff time and missed opportunity. Which is exactly why it’s so easy to leave unexamined, year after year.
At sector level, though, it adds up fast. A March 2026 Jisc briefing estimated that technical legacy could be costing UK universities between £2bn and £4.7bn a year (Jisc, Tackling technical legacy in UK higher education, 2026) through duplicated systems, the maintenance of outdated technology, and lost staff productivity. And Jisc is clear that the money is only part of it. Many of these costs are hidden – the kind you’d never think to add up. And the biggest risk of all is the innovation that never happens.
The person who is also a single point of failure. In many institutions, how the systems connect lives in one person’s head. They know which script runs at 2am, which spreadsheet feeds which system, why that one integration has to be nudged by hand every enrolment. It works, right up until they’re on leave, off sick, or they’ve moved on. That’s not a criticism of them; it’s a concentration of risk that would keep any head of IT awake if they had to answer to the senior team when something broke.
The expertise that’s hard to replace. Across IT more widely, deep knowledge of older, custom-built integrations tends to concentrate in a few long-serving specialists – and these roles can be hard to recruit into. That makes succession a strategic question, not just an HR one: if you looked around the room today and asked “who really knows what connects these systems together, and what happens when they leave?”, would you be comfortable with the answer?
The integrations no one is watching. Many legacy connections run unmonitored and unmaintained, and they rarely fail cleanly. More often, a system update or a small change at one end breaks something quietly, or the integration keeps running while passing on data that’s subtly wrong. When that happens, the cost isn’t just the fix. It’s the reputational damage of data going wrong in front of students or staff, and the process chaos that follows when your systems are no longer telling each other the same story.
The hours spent moving data by hand. Where integration is manual – spreadsheets exported and re-imported, records keyed twice, direct database connections held together with care – skilled people spend a surprising share of their week simply shifting data from one place to another. It’s the “lost staff productivity” Jisc points to, and it’s slow, error-prone, and scales badly at exactly the moments, like clearing and enrolment, when you can least afford it to.
The student experience – and the support load behind it. When systems don’t share data reliably, students feel it: an enrolment that hasn’t reached the VLE, a fee record that’s out of date, the same question asked three times because no system has the full picture. Each one is a frustrated student and a support ticket for your team. And across a cohort it chips away at the joined-up experience you’re working to deliver, at a time when satisfaction and retention matter.
The modernisation you can’t start. Perhaps the most expensive hidden cost is the one that never happens, and it’s the risk Jisc rates highest. The catch is that the way many institutions integrate today – hand-keyed spreadsheets, direct database connections – simply doesn’t carry across to modern, cloud-based platforms, which expect clean, API-based integration. The more you depend on those older methods, the more a move to a new VLE or student system means first rebuilding how everything connects. So the current setup doesn’t just cost you today: it can stand between you and the platforms and AI-enabled services you want to move to next.
The salary you’re paying to move data. Keeping scarce, specialised data-integration expertise on staff is expensive in its own right. That’s a real, recurring payroll cost attached to a task that, done well, should largely run itself.
The work that isn’t getting done instead. And behind the salary sits the opportunity cost. Every hour a capable person spends moving data from server to server, database to database or file to file is an hour they’re not spending on the frontline work that actually improves things for students and staff.
You don’t need us to tell you where these sit. A few honest questions will get you most of the way:
Who is your single point of failure, and what happens the week they leave? Which integrations would break without anyone noticing until it’s too late? How many skilled hours each month go into moving data by hand? Where does the experience feel disjointed to a student or a colleague? And, crucially, what modernisation is currently blocked, or quietly harder, because of how your integrations work today?
The answers tend to be uncomfortable, and clarifying. Most institutions have simply never laid them side by side.
The alternative isn’t a bigger version of the same thing. It’s treating integration as a managed, monitored, maintained service. Resilient by design, not dependent on any one person, and built to give you a clear runway to modernise rather than a barrier to it. That’s the model we’ve built Amos Connect around, and it’s how we help universities and colleges turn integration from a hidden cost into a foundation they can build on, freeing up people, budget, and keeping the path to modernising clear.
None of this calls for ripping everything out tomorrow. The first step is simpler: seeing the cost clearly, and deciding whether it’s one worth carrying for another year.
If you’d like to see what that looks like for your own institution, the Amos team is always glad to help – mapping where your costs and risks sit today, and setting out practical options at whatever pace suits you.
Feel free to contact Derek to book a no-obligation chat and to take the first step towards a more cost-effective, simpler, and more reliable way forward for your organisation.
