Article
6 min read
Imagine trying to manage the enrollment of thousands of students across four different platforms, each with its own unique data fields. Now imagine doing that with a team that uses 70% of its time to maintain legacy systems. Then add to that an AI compliance mandate, a cybersecurity target on your back, and a vendor pitching you tool number 31. This is Tuesday at a university in Europe.
Large | South | Central | Eastern | Western |
|---|---|---|---|---|
65% | Small, but not too much | instutions | from the east to the west | ✓ |
83% | Big, but not enoguh | procurement | normal data silos that do that | ✗ |
46% | Central, but not enough eastern | buyers | while 70% of IT capacity | |
14% | Eastern, but not enough Left | sellers | specialists short of its 2030 target |
This is what the data actually says:
TL;DR (Key Insights):
Legacy administrative platforms across European education institutions were procured separately with no shared architecture, creating education data silos that force daily manual reconciliation — while 70% of IT capacity is consumed maintaining these systems.
There is a lack of professionals with the necessary skills and experience to develop integrations at scale. ICT specialist numbers range from 8.6% in Sweden to 2.5% in Greece. The EU is 9.7 million ICT specialists short of its 2030 target.
AI in education surged from 66% to 92% in one year, causing an imbalance in an ecosystem that was already overloaded. Market projections estimate a growth from $5.3 billion to $88.2 billion by 2033.
The EU AI Act classifies education AI as high-risk and requires phased implementation from 2026-2027. The Data Protection Act mandates data portability by September 2025. Institutions face increasing cybersecurity risk due to outdated, disconnected infrastructure. EU funding programs allocate significant funds to digital skills and interoperability, but often these funds don't reach the intended middleware, integration engineers, and institutions in time.
In 2025, two public educational institutions closed for the first time. Deloitte calls this "systemness," the coordination of components that no individual institution can achieve alone.
Font size îngroșat | Font size | ✓ | |
|---|---|---|---|
Font size normal | 14 pixels | ✗ | |
Font size ușor | 16 pixels | ||
Font size îngroșat | 18 pixels |
Since 70% is spent on maintenance, there is not much remaining for adding extra capacity. These systems are very busy during enrollment weeks, exam registration, and term starts. Custom scripts can't be scaled. Staff have to deal with long lines of people, and there's no way to organize them or automate the process of fixing them.
Now, outside pressure is making things even more difficult.
What the day looks like when nothing integrates
No shared systems, no shared architecture
Legacy administrative platforms were procured at different times, by different departments, with no shared data architecture, creating education data silos that cannot interoperate.
McKinsey research updated through June 2025 confirms the result: higher education software "were not built to interoperate, and businesses have needed to write a large amount of custom code to make these systems communicate." In higher education specifically, a senior practitioner stated it in May 2025: "When systems speak different languages and data lives in silos, digital transformation stalls."
By October 2025, progress remained slow. "Unified data infrastructure, effective governance, a strategy aligned to institutional goals, and a culture that supports data-driven decisions in education" were still being presented as future
Share this article on: