The Challenge
A globally recognised university faced significant challenges with their existing Learning Management System (LMS). Despite a robust curriculum and a comprehensive suite of resources, student engagement metrics were worryingly low. The institution was experiencing a plateau in student interaction, with only 65% of enrolled students actively participating in digital coursework and forums. This stagnation not only affected the learning experience but also risked diminishing the university's reputation for fostering an innovative education environment.
Students and faculty members highlighted key issues with the LMS: a non-intuitive user interface, lack of mobile accessibility, slow system performance during peak usage times, and insufficient analytics tools to track student progress and engagement. These limitations were critical pain points that prevented the university from fully leveraging its digital learning offerings and adapting to the modern educational needs of its diverse student body.
The Solution
Adyantrix was commissioned to undertake a comprehensive overhaul of the university's LMS. Our team began by conducting a detailed analysis of user needs through surveys and interviews with students and faculty. This insight guided the development of a strategy focused on three core areas: user experience enhancements, performance optimisation, and advanced analytics integration.
First, we redesigned the user interface to be more intuitive and visually appealing, ensuring easy navigation for both tech-savvy and less experienced users. Mobile-responsive designs were also implemented to accommodate the growing number of users accessing content from their smartphones and tablets.
Second, improved backend infrastructure and DevOps practices were introduced, significantly enhancing system performance and reliability. By migrating to a cloud-based architecture and implementing load balancing techniques, Adyantrix ensured the LMS could handle increased traffic and user loads without compromising on speed or availability.
Lastly, we enhanced the system's analytics capabilities by integrating sophisticated data analytics tools. These tools provided real-time insights into student engagement patterns, enabling educators to personalise learning paths, identify at-risk students promptly, and innovate curriculum delivery methods.
Key Results
The impact of the LMS overhaul was profound. Student engagement metrics soared by 45%, with an impressive 94% of students now actively participating in digital learning activities. The new platform's usability attracted positive feedback from students and faculty alike, who praised the system's seamless performance and intuitive interface.
The refined analytics tools empowered educators with actionable insights, leading to improved teaching strategies and heightened student outcomes. The university also noted improved retention rates as a direct consequence of the enhanced learning environment.
With the LMS's new mobile-friendly features, the university expanded its reach, facilitating international enrolment increases of 20%. Additionally, the system's robustness during peak periods bolstered the institution's reputation as a leader in educational technology.
In summary, Adyantrix's intervention not only transformed the existing LMS but set the benchmark for future-ready educational platforms, demonstrating that an investment in technology can drive academic excellence and student satisfaction across the board.
Technical Approach
The legacy LMS was built on a heavily customised installation of Moodle 3.5, hosted on ageing on-premises servers that had been provisioned for a much smaller student population. Years of ad hoc plugin additions had created a brittle codebase with poor separation of concerns, making performance tuning and front-end redesign extremely difficult without undertaking a deeper architectural overhaul.
The Adyantrix team adopted the following technical approach:
- Moodle 4.2 migration on AWS: Rather than rebuilding from scratch, the team elected to upgrade to the current Moodle LTS release, which introduced a substantially improved default UI framework, and re-implement customisations selectively — retaining only those plugins with genuine user value and replacing deprecated ones with maintained alternatives.
- Cloud infrastructure on AWS: The platform was migrated to an auto-scaling group of EC2 instances behind an Application Load Balancer, with an RDS Aurora cluster replacing the single-node on-premises database. This configuration allowed the platform to scale horizontally during peak periods — examination weeks, semester starts — without manual infrastructure intervention.
- Redis for session management and caching: The legacy installation stored PHP session data on local disk, meaning that load balancing across multiple application servers was not feasible. Migrating session state to a Redis ElastiCache cluster was the critical enabler for horizontal scaling.
- Xerte and H5P integration for interactive content: The analytics data revealed that the course materials with the lowest engagement were static PDF uploads. The team worked with the university's instructional designers to migrate high-priority units to H5P interactive formats — branching scenarios, drag-and-drop exercises, embedded video with comprehension checks — which showed dramatically higher completion rates in pilot testing.
- Learning Record Store (LRS) integration using the xAPI (Tin Can) standard: A dedicated LRS (Learning Locker) was deployed alongside the LMS to capture granular learner interaction data — time on task, content completion at the section level, quiz attempt patterns — that Moodle's native reporting did not expose. This data was the foundation of the at-risk identification analytics.
Implementation Highlights
The migration was structured to avoid disrupting an academic year in progress. The team worked within a narrow pre-semester window and employed a parallel-running strategy to validate the new platform before cutting over:
Discovery and audit (weeks 1–4): A full audit of the existing Moodle installation catalogued 147 active plugins, of which 61 were found to have no maintained equivalent for Moodle 4.2 and had zero recorded usage in the previous 12 months. Removing these immediately reduced the codebase complexity by approximately 40% and eliminated a significant surface area for security vulnerabilities.
Infrastructure build and data migration (weeks 5–10): The AWS environment was provisioned using Terraform infrastructure-as-code, ensuring reproducible and auditable deployments. The course and user database was migrated in full to the new environment and validated against checksums. All media assets — video files, document uploads, SCORM packages — were migrated to S3 object storage and served via CloudFront CDN, reducing page load times for media-heavy course pages from an average of 8.2 seconds to under 1.4 seconds.
UI redesign and accessibility remediation (weeks 6–12, overlapping): The front-end redesign followed WCAG 2.1 AA guidelines throughout, a requirement driven by the university's commitment to inclusive education. Automated accessibility testing using axe-core was integrated into the CI pipeline, ensuring that new theme customisations could not introduce accessibility regressions.
Staff training and content migration support (weeks 11–16): Faculty engagement was essential to adoption success. The team delivered structured training sessions for academic staff on the new UI and interactive content tools, and provided a dedicated support channel during the first four weeks of live operation.
Measurable Outcomes
The post-launch assessment at the one-year mark produced the following quantified findings:
- 45% increase in student engagement, measured as the proportion of enrolled students completing at least 70% of available course activities — rising from 65% to 94% of the active student population.
- 20% increase in international enrolment in the 12 months following launch, attributed in part to the improved mobile experience enabling students in time-zone-distant markets to participate more flexibly.
- System availability improved from 97.2% to 99.7% over the academic year, eliminating the mid-session outages that had repeatedly affected examinations under the legacy infrastructure.
- Average page load time reduced from 4.8 seconds to 0.9 seconds for the most-visited course pages, directly improving the session duration and reducing bounce rates on course content pages by 34%.
- At-risk early identification: The xAPI analytics flagged 312 students as at-risk of disengagement within the first six weeks of the autumn semester. Of those contacted by personal tutors, 71% re-engaged with their course activities within two weeks — an outcome that would not have been achievable without the granular engagement data.
- Faculty satisfaction scores with the LMS rose from 3.1 to 4.6 out of 5 in the annual IT satisfaction survey, reflecting the improvement in tool reliability and the reduction in support tickets generated by LMS-related issues.
Lessons Learned
This project generated several insights directly applicable to future higher education technology transformations:
- Student and faculty consultation at the outset is not optional. The discovery phase surveys revealed that the most-requested improvements — faster load times and mobile access — were not the features the IT team had prioritised for development. Grounding the development priorities in actual user pain points ensured that engineering effort went where it would have the most adoption impact.
- Analytics are only valuable if educators act on them. The at-risk identification capability had existed in a basic form in the legacy system but was rarely used, because the reports required manual interpretation and there was no defined process for acting on them. Building an at-risk alert workflow — automated email to the personal tutor with a contextual summary of the student's engagement profile — converted a passive data asset into an active intervention tool.
- Removing unused plugins is as important as adding new features. The 61 removed plugins had collectively introduced 23 known unpatched CVEs into the legacy system. The security posture improvement from removal was measurable and immediate.
Why This Approach Worked
The overhaul succeeded because it treated the LMS not as a content repository but as a learning environment in which every design decision had a downstream effect on student behaviour. The choice of cloud infrastructure was not primarily a technical decision — it was a decision to make the platform reliably fast and always available, because a platform that students experience as slow or unreliable is a platform they will avoid.
Similarly, the investment in xAPI analytics was motivated not by a desire to generate more data, but by a recognition that the university already had committed pastoral care processes and at-risk intervention programmes — they simply lacked the timely, granular data to activate those processes effectively. By providing that data, Adyantrix enabled the university's own staff to do their jobs better, which is the most sustainable outcome a technology intervention can achieve.
Speak with our Custom Software Development team at Adyantrix to find out how we can support your next project.
Work with Adyantrix
If you are looking to tackle a similar challenge, Adyantrix has the expertise to help across the full project lifecycle. Our custom software development practice covers tailored applications built to your exact workflows. Our web application development practice covers scalable web applications and portals. Our DevOps & cloud solutions practice covers automated pipelines and cloud platform engineering. Our data analytics practice covers BI reporting and self-serve analytics platforms. Get in touch to discuss your requirements — no commitment required.
