UK higher education
Move to your new ERP while preserving searchable finance, HR, payroll and historical records — without keeping Unit4, Agresso, Oracle, PeopleSoft or SAP running indefinitely.
Universities modernise the ERP and then keep the previous platform running, because occasional historical access is still required. The question that actually blocks retirement is not where to put old data.
How do we preserve usable historical access well enough to switch the old application off?
Don't keep an ageing ERP alive simply because Finance, HR or audit teams occasionally need historical records.
The replacement platform is not the point. Institutions move to a newer Unit4 release, to Oracle Fusion, to Workday, to SAP or to another cloud ERP — and the outgoing environment holds the same history in every case. SyntraETL is the migration, archive and decommissioning layer, whichever target you have chosen.
A working inventory of the record classes that usually have to survive the ERP, grouped the way an institution's own finance and HR teams think about them.
Module
Module
Module
Module
Module
Module
Exact scope depends on the modules used, institutional retention policies and the replacement-system strategy.
Unit4 is the most common UK university finance estate, but rarely the only thing being kept alive for history.
Typical areas: finance, procurement, assets, HR and payroll, with the attachments held against them.
Explore Oracle EBS Retirement →Typical areas: HCM and Financials, and the effective-dated employee and finance records that a target system will not accept.
Explore PeopleSoft Retirement →Typical areas: finance, procurement, HR, assets and document-level historical transactions.
Explore SAP ECC Retirement →Standalone HR and payroll platforms replaced ahead of, or behind, the finance system. Historical employee and payroll records are preserved with the pay periods, elements and deductions they were calculated under.
Payroll and HR archival →Departmental and faculty systems and historical reporting databases that grew around the ERP. These are consolidated into the same archive rather than retired one at a time into nothing.
Assess your estate →Most institutions run a warehouse or reporting database alongside the ERP. Keeping it alive to serve history defeats the purpose of retiring the ERP, so it belongs in the same inventory.
Syntra Legacy Exit →Historical journals, invoices, payments, supplier history, balances, assets and cost centres — the basis of every prior-year comparative and audit request.
Grants, projects, historical expenditure, funding-related transactions and the supporting evidence behind them. Funder audit routinely reaches back beyond the life of the system that recorded the spend.
Previous employees, assignment history, organisational history, compensation history and absence where applicable — including leavers, returners and fixed-term research staff.
Historical payroll results, deductions, payment history and employee payroll records, queried long after the pay period closed.
Suppliers, requisitions, purchase orders, receipts, invoices and the approval trail that authorised them.
Attachments, invoices, reports, supporting evidence and audit history, archived against the record they belong to rather than as a separate document dump.
SyntraETL preserves and provides access to research and project finance records held in the source system. It is not a grant-management application and does not replace one.
Most migration scope arguments are really this question, asked one object at a time. Settling it early shrinks the migration and removes the reason the old platform survives.
| Typical data moved to the new ERP | Typical data retained in the historical archive |
|---|---|
| Active suppliers | Closed suppliers |
| Open invoices | Historical invoices |
| Open purchase orders | Completed purchase orders |
| Active employees | Former employee history |
| Current balances | Detailed historical transactions |
| Active projects | Closed projects and grants |
| Opening balances | Historical journals |
| Current reference data | Historical attachments and audit history |
This is illustrative. The final migration and archive split is agreed during discovery with the institution and the implementation partner.
Your SI implements the new ERP. SyntraETL handles the migration, historical preservation and retirement layer.
SyntraETL is not an ERP implementation partner and does not compete with one. The data workstream runs inside the programme your SI or your own team leads.
The cost is rarely visible as one line. It is a vendor renewal, an infrastructure allocation, a share of application support and the specialist skills retained for a platform nobody wants to work on.
Illustrative business case only. Actual costs and savings depend on licences, infrastructure, support contracts, data volumes and retention requirements.
Retirement is signed off by information governance as much as by IT. The archive is designed so the obligations currently justifying the legacy platform are met by the archive instead.
SyntraETL supports institutions in implementing their approved retention, access and disposal policies. It does not provide legal advice, does not set retention periods, and does not by itself make an institution compliant.
No information asset owner signs off a shutdown on the basis that the archive looks right. Each extract is reconciled back to source and the evidence is retained as part of the decommissioning pack.
| Validation | Source | Archive | Status |
|---|---|---|---|
| Suppliers | 73,214 | 73,214 | ✓ |
| Invoices | 3,842,119 | 3,842,119 | ✓ |
| Journals | 8,426,873 | 8,426,873 | ✓ |
| Attachments | 312,446 | 312,446 | ✓ |
Illustrative example. The figures show how reconciliation evidence is presented; they are not drawn from a specific engagement.
Source, transformed, rejected and archived counts at every cycle.
Control totals on financial data, so a matching row count cannot mask a broken amount.
An invoice still resolves to its supplier, purchase order, approvals and attachments.
Documents reconciled separately — the most common place an archive is quietly incomplete.
Every discrepancy categorised and explained rather than netted off.
Finance, HR and information governance accept the evidence before anything is switched off.
Technology
Reduce technical debt and the support burden of an estate that keeps growing because nothing is ever retired.
Finance
Remove the cost of maintaining an ERP that has become a historical lookup tool.
Programme
Reduce migration scope and remove the legacy dependency that keeps a closed programme open.
People
Preserve access to historical workforce and payroll information for verification, pensions and ER cases.
Applications
Retire ageing ERP infrastructure and the environments, copies and interfaces around it.
Governance
Support controlled retention, search, legal hold and evidenced disposal.
SyntraETL has not yet published a UK higher-education engagement. The engagements below are the same architecture delivered elsewhere, and are shown on that basis.
A local council moved PeopleSoft HCM to Oracle Fusion with effective-dated employment history preserved and reconciled.
Read the case study →Finance, procurement and master data migrated out of SAP ECC with source-to-target reconciliation at every cycle.
Read the case study →A government body migrated Oracle EBS financials to Oracle Fusion with a controlled, repeatable and reconciled migration process.
Read the case study →These are published SyntraETL engagements outside the UK, shown because the architecture is the same one applied here. They are not UK public-sector references and are not presented as such.
Tell us which ERP, finance, HR, payroll and departmental systems are still being maintained for historical access. We will come back with a scoped Legacy Exit Discovery proposal.
A Legacy Estate Assessment establishes which applications your institution is keeping alive purely for historical access, what has to be retained and for how long, what those systems cost today, and what retiring them would return.