Unit4 Student to Microsoft Fabric: Student Records and Retention Reporting Dashboards for UK Universities
Unit4 Student Management data reaches OneLake through a read-only replica, SFTP export or API and feeds Power BI reporting dashboards.
Unit4 Student to Microsoft Fabric is the step UK universities take when the student record is trusted, but the reporting built around it is slow, manual and hard to defend. Student numbers, continuation and completion measures and in-year returns all draw on the same records. Fabric gives that data one governed home, so planning, registry and faculty teams work from the same reporting dashboards.
This guide is for registrars, directors of planning and student systems, data and BI managers and the IT leaders who support them. It explains the pressure on reporting, how Unit4 Student Management makes data available, the realistic routes into Fabric, and what to build first.
Why University Student Reporting Is Under Pressure
The Office for Students notes that the original Data Futures programme concluded in 2024 and that an in-year student data collection programme launched in 2025. Whatever the detail of each return, the direction is clear: student data is expected to be accurate sooner, and institutions are expected to explain it.
Alongside regulatory measures such as continuation, completion and progression sit the questions leadership asks every term about retention, engagement and recruitment. Many institutions answer these from several places, and the planning team joins them by hand. The cost is late numbers and versions that disagree.
What Unit4 Student Management Holds, and Where Reporting Stops
Unit4 Student Management is a cloud student information solution. Unit4's service description says it is delivered as software as a service on Microsoft Azure, with a separate database for each customer and, for UK customers, London and Cardiff as the primary and disaster recovery locations. The same document describes user-created and ad-hoc reports inside the product, and does not describe a dedicated analytics platform.
That is sensible for running student administration and limiting for institution-wide analysis. Combining student records with engagement, finance or recruitment data is hard to do repeatably inside one product. Fabric does not replace Unit4 Student. It adds a governed copy that analysts can use freely. The service description we reviewed is from 2020, so confirm each point against your current agreement.
Why Unit4 Student to Microsoft Fabric Works for Reporting Dashboards
Many universities already run Microsoft 365, Azure and Power BI, so identity, licensing and security are familiar. Fabric brings OneLake storage, pipelines, notebooks, a warehouse and Power BI into one environment billed on a single capacity, which keeps the platform manageable for a lean data team.
Capacity can be placed in a UK Azure region, which supports data residency requirements, although the final position belongs in your data protection impact assessment. If you also run other student systems, see how we approach SITS:Vision to Microsoft Fabric. Our Power BI consulting team builds the dashboards on top.
Unit4 Student to Microsoft Fabric: Replica, SFTP and API Routes
Unit4's service description lists three ways to reach customer data. Which are included depends on your agreement, so confirm with Unit4 before designing anything.
| Route | When it fits | Check first |
|---|---|---|
| Read-only database replica | You want tables or views refreshed frequently for reporting | Optional and extra cost, which tables or views, database type, connection method |
| SFTP data export | Scheduled file extracts are enough for the questions you ask | Which data the export covers, schedule, file format, history |
| API or web services | You need specific objects or event-driven updates | Coverage, rate limits, effort to build and maintain |
| Existing extracts or a data warehouse | Reporting already depends on them | Missing fields and history, ownership, reconciliation |
Unit4 describes the read-only replica as an optional, extra-cost copy of selected tables or views, refreshed at least every 15 minutes. It also describes SFTP with separate import and export credentials, and API and web services for integrations. Fabric pipelines can copy from SFTP and REST sources into a lakehouse, and a replica can be read through a pipeline and gateway where needed. Whichever route you choose, the goal is a trusted copy on an agreed schedule, with the live student record left alone.
Our Microsoft Fabric migration approach and migration checklist show how the chosen route fits a wider plan.
- Unit4 Student to Microsoft Fabric gives student, course and cohort data one governed home for reporting dashboards.
- Unit4 lists a read-only replica, SFTP export and APIs as access routes, and which you have depends on your agreement.
- Confirm what your contract includes before designing, because the replica is optional and extra cost.
- Build a reconciliation view and keep history from the first release, so every submitted number can be explained.
- Start with one question, such as continuation for one faculty, and agree the definition first.
Building a Student Reporting Model That Reconciles
Design the model around the questions you must defend: who is enrolled, on which course and mode, at what point in the year, and what happened to them. Keep a raw copy of the extracted tables, a cleaned layer where students, courses and cohorts carry one agreed definition each, and a measures layer that Power BI reads.
Build a reconciliation view from the start. It compares internal counts with what was submitted, so differences are found and explained before a deadline rather than after. Keep history, because continuation and progression questions compare cohorts over time, and a snapshot of today does not answer them.
UK GDPR, Student Data and Reporting Governance
Student data is personal data, and some of it is special category data. Bring it into Fabric with a clear lawful basis, a data protection impact assessment and a retention rule, and keep personal identifiers out of datasets that do not need them. Unit4's service description treats the customer as data controller, so your institution owns these decisions.
Row-level security lets a head of school see their own students while the planning office sees the whole institution. Our guide to OneLake security, DLP and governance covers the controls in more detail. Our data governance consulting work and the Power BI Governance Platform keep them in place, and our guide to moving system data into Fabric explains the wider case.
Unit4 Student to Microsoft Fabric: What to Build First
Start small. A continuation and retention view for one faculty, agreed with the planning office and reconciled to what was submitted, proves the approach. Then add engagement, attendance, finance and recruitment data, and extend to other faculties.
A short discovery confirms which Unit4 access routes your agreement includes and what to build first. Numlytics designs and builds Microsoft Fabric data platforms and Power BI reporting for universities. Speak with a certified consultant to turn your student data into reporting you can defend.