TechnologyOne to Microsoft Fabric: Finance, Student and Council Reporting Dashboards
TechnologyOne data reaches OneLake through REST API, file export or ETL and feeds Power BI reporting dashboards for finance, student and council teams.
TechnologyOne to Microsoft Fabric is the step universities, councils and other public bodies take when a SaaS enterprise platform runs the organisation, but leaders still wait for exports and spreadsheets to see the whole picture. Finance, student and asset data sit in one vendor's platform, while planning, risk and performance questions need that data combined with everything else. Fabric gives it one governed home, so reporting dashboards are built once and trusted everywhere.
This guide is for finance directors, planning and data leaders, student systems teams and the IT leaders who support them. It explains why SaaS reporting still needs a data platform, how data can leave TechnologyOne, and what to build first.
Why SaaS Reporting Still Needs a Data Platform
A SaaS platform removes servers and upgrades from your list, and it usually includes its own dashboards. What it does not do is combine its data with the rest of your estate. Student, finance and workforce numbers live in one product, while engagement, timetabling, CRM and planning data live elsewhere, so cross-cutting questions end up in spreadsheets.
That produces late numbers and competing versions. Reporting dashboards are only dependable when definitions are agreed once and applied to every source.
What TechnologyOne Holds: Finance, Student and Council Data
TechnologyOne provides a SaaS enterprise platform used across education and the public sector. Its Student Management offering covers the lifecycle from enquiry to graduation, with a Reporting and Analytics module that provides integrated dashboards, and the vendor also supplies finance and other business modules. A subject area for council or local government reporting follows the same pattern, with its own entities and owners.
Plan each module as a separate subject area that shares common dimensions such as calendar, organisation unit and cost centre. Because TechnologyOne is delivered as a service, access to the data depends on what the vendor exposes. Check your agreement and the current documentation rather than assuming a database connection is available.
Why TechnologyOne to Microsoft Fabric Works for Reporting Dashboards
Fabric brings OneLake storage, pipelines, notebooks, a warehouse and Power BI together on one capacity, with security that follows Microsoft 365 identities. Once TechnologyOne data is in OneLake it can be joined with HR, CRM, learning, survey and planning data, modelled once and served through a governed semantic model.
That is the difference between dashboards inside one product and a reporting estate that covers the organisation. If you are also reviewing student systems, see how we approach SITS:Vision to Microsoft Fabric and Unit4 Student to Microsoft Fabric. Our Power BI consulting team builds the dashboards.
TechnologyOne to Microsoft Fabric: REST API, Export and ETL Routes
Public service listings describe TechnologyOne Student+ as offering REST and SOAP web services, with API documentation and a test sandbox, business ETL tools, and exports in formats such as CSV and XML. Which of these your organisation can use depends on your modules and agreement, so confirm with the vendor first.
| Route | When it fits | Check first |
|---|---|---|
| REST API | You need configurable data sets on a schedule | Which data sets are exposed, authentication, volume limits, who maintains it |
| SOAP web services | You need predefined business processes or updates | Coverage, effort to build and maintain, read versus update |
| Scheduled file export | Daily or weekly extracts answer the questions you ask | Which data the export covers, format, history, delivery location |
| Existing extracts or a data warehouse | Reporting already depends on them | Missing fields and history, ownership, reconciliation |
Fabric pipelines and Dataflows Gen2 can pull from REST sources and from files, landing data in a lakehouse on a schedule. Because this is SaaS, there is usually no database to mirror unless the vendor provides one, so plan for incremental loads that identify changed records. Our Microsoft Fabric migration approach and migration checklist show how the chosen route fits a wider plan.
- TechnologyOne to Microsoft Fabric gives finance, student and council data one governed home for reporting dashboards.
- Because it is SaaS, access depends on what the vendor exposes, such as REST, SOAP, exports or ETL tools.
- Confirm which routes your agreement includes before designing, and avoid assuming a database connection.
- Plan incremental loads and a reconciliation view so every number ties back to the source.
- Start with one subject area and one dashboard that the data owner signs off.
Building One Reporting Model Across Finance, Student and Council
The value comes from shared definitions. Calendar, organisation unit, cost centre, supplier and person definitions can be agreed once and reused by finance, student and council reporting. Each module lands in a raw layer, is cleaned in a shaped layer where each entity has one definition, and feeds a measures layer that Power BI reads.
Keep history from the first release, because trend and cohort questions compare periods, and a snapshot of today cannot answer them. Build a reconciliation view that ties dashboard totals to the figures finance and registry already report, so differences are found and explained early.
Security, Data Protection and Reporting Governance
These systems hold personal, financial and student data, some of it 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. Row-level security lets each department see its own data while central teams see the whole organisation.
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 definitions consistent, and our CRM and ERP to Fabric guide explains the wider case.
TechnologyOne to Microsoft Fabric: What to Build First
Choose the subject area leaders ask about most, such as a finance performance pack, a student retention view or an asset and works dashboard. Confirm the access route, land the data in a lakehouse, build one semantic model and one reporting dashboard, and agree the definitions with the data owner. Then add the next module.
A short discovery confirms which TechnologyOne modules you run, which access routes your agreement includes and the first dashboard to build. Numlytics designs and builds Microsoft Fabric data platforms and Power BI reporting. Speak with a certified consultant to turn your TechnologyOne data into reporting you can rely on.