Modernisation · iMiddleware
Legacy system modernisation services for ministries and universities
The system nobody wants to touch is usually the one everything depends on. It holds a decade of records, it is wired into payroll, registration or reporting, and the people who wrote it have moved on. Meanwhile the requirements keep arriving: online services, dashboards, national reporting, AI. Replacing it wholesale means a switchover date, a freeze on operations and a risk profile no committee wants to sign.
Intrazero approaches modernisation the other way round. iMiddleware sits between the systems you already run and the platforms you want to add, brokering data and identity so both keep working while the estate changes underneath. The clearest example is Egypt's national LMS programme, where 500+ governmental university faculties were federated into one national layer through iMiddleware rather than being migrated onto a single new system first.
Why rip-and-replace fails in public institutions
A full replacement asks an institution to do two hard things at once: build the new system and stop running the old one. Public bodies rarely have that luxury. Admissions still open in September, invoices still fall due, inspectors still ask for last year's records. When the cutover slips — and it usually does — the organisation is paying to operate two systems with none of the benefit.
Incremental modernisation removes the cutover as a single point of failure. Each capability moves when it is ready and proven, the legacy system stays authoritative until it is not needed, and the programme can be paused or resequenced without stranding the institution mid-migration.
- No single switchover date that the whole programme depends on
- Operations continue on the legacy system while new services go live
- Value delivered in stages instead of at the end of a multi-year build
- Rollback stays possible because the old system is still running
- Budget and scope can be resequenced between phases
iMiddleware: brokering between the old system and the new one
iMiddleware is Intrazero's integration platform. It sits between systems and brokers what passes between them — records, identities, events and reference data — so a new application can read and write against a legacy database, an older reporting system or a departmental application without either side being rewritten to suit the other.
That layer is where the difficult work of modernisation actually happens: reconciling field definitions between institutions that never agreed on one, translating an old system's export format into something a modern platform can consume, and keeping both copies of a record consistent while ownership of that record moves from one system to the other.
- Connects new platforms to existing databases and departmental systems
- Maps and reconciles differing data models between institutions
- Keeps legacy and new systems consistent during the transition period
- Federates many local systems into one national or group-level view
- Lets each institution keep its own system while joining a shared layer
Proven at national scale: 500+ faculties on one federated layer
Egypt's national LMS programme is the working proof. More than 500 governmental university faculties were brought onto a national learning layer built on iStudent, connected through iMiddleware. Faculties did not have to abandon what they were already running or migrate in lockstep; the middleware federated them.
That is the pattern most large modernisation programmes need. The centre gets consistent data and a single view; the institutions keep local systems, local processes and local control. Neither side has to wait for the other to finish.
- 500+ governmental university faculties federated via iMiddleware
- Institutions joined without abandoning existing local systems
- One national view for the centre, local autonomy for each faculty
- Delivered inside a live national education programme, not a pilot
- Part of delivery spanning 24+ ministries and 200+ projects
Modernise around the systems you intend to keep
Not every legacy system deserves replacing. Some are stable, well understood and simply isolated — the problem is not the system, it is that nothing else can reach it. In those cases modernisation means giving it interfaces, not a funeral.
Intrazero's platforms are built to sit alongside an existing estate rather than demand exclusivity. iTest integrates with Moodle, Blackboard, Canvas and Google Classroom; iTutor — an AI tutoring platform rather than an LMS — adds SCORM to that list; iStudent covers the student lifecycle from admissions to alumni; iAssets and MedWaste do the same on the healthcare side, from hospital maintenance to medical waste chain of custody. Each can be introduced against a legacy core through iMiddleware.
- iTest integrates with Moodle, Blackboard, Canvas and Google Classroom
- iTutor, an AI tutoring platform, adds SCORM to the same integrations
- iStudent covers the student lifecycle from admissions to alumni
- iAssets and MedWaste modernise healthcare operations without replacing core systems
- Legacy systems gain interfaces instead of being decommissioned prematurely
Deployment, data control and how a programme is procured
Modernisation programmes are usually constrained by where data may live before they are constrained by technology. iTest runs cloud, on-premise or hybrid; iStudent and iAssets run cloud or on-premise; iTutor and MedWaste are cloud only. Where a regulator or ministry requires the data to stay inside national infrastructure, a platform that supports it is deployed there and iMiddleware brokers across the boundary.
Commercially, the work is scoped in phases with defined deliverables rather than as one indivisible programme, which is what makes it approvable by a procurement committee that cannot underwrite a multi-year switchover. Intrazero has been delivering since 2016, with 24+ ministries across 5+ countries, from Cairo, Dubai, Riyadh, Muscat and Hamburg.
- On-premise, cloud or hybrid deployment depending on the platform
- Data can remain inside national or institutional infrastructure
- Scoped in phases with deliverables per phase, not one monolithic contract
- Discovery maps the existing estate before any commitment to replace
- Offices in Cairo, Dubai, Riyadh, Muscat and Hamburg
FAQ
What are legacy system modernisation services?
They are the work of extending, connecting and gradually replacing systems that an organisation still depends on but can no longer develop. Intrazero delivers this through iMiddleware, an integration platform that brokers between existing systems and new ones, so modernisation happens in stages instead of a single rip-and-replace switchover.
Do we have to replace our existing system?
No. The point of the approach is that the legacy system keeps running and stays authoritative until it is genuinely no longer needed. iMiddleware connects it to new platforms so both operate together, and capabilities move across only when they are ready and proven.
What does iMiddleware actually do?
iMiddleware is Intrazero's integration platform. It brokers between systems — mapping data models, translating formats, and keeping records consistent between a legacy system and a new one during the transition. On Egypt's national LMS programme it federated 500+ governmental university faculties into a single national layer.
Can you integrate with Moodle, Blackboard or Canvas?
Yes. iTest integrates with Moodle, Blackboard, Canvas and Google Classroom, and iTutor adds SCORM to the same set. Where a system is not on that list, iMiddleware is the layer used to connect it, which is how bespoke and in-house legacy systems are brought in.
How is a modernisation programme scoped and procured?
It starts with discovery: mapping the existing estate, its data and its dependencies before anything is committed to replacement. The programme is then scoped in phases with deliverables per phase, so a procurement committee approves defined stages rather than underwriting one multi-year switchover with a single cutover date.
Can the modernised system run on our own infrastructure?
Yes, depending on the platform. iTest supports cloud, on-premise or hybrid deployment; iStudent and iAssets support cloud or on-premise; iTutor and MedWaste are cloud only. Where data must remain inside national or institutional infrastructure, a platform that supports it is deployed there and integration is brokered across the boundary.
Modernise without stopping operations
Tell Intrazero which systems you cannot switch off and the team will map a phased modernisation around them — starting with what iMiddleware can connect today.
Tell Intrazero which systems you cannot switch off and the team will map a phased modernisation around them — starting with what iMiddleware can connect today.
Initiate Technical Scoping
Complete the form below and our enterprise architecture team will respond within one business day.