NHS & healthcare
Retire the application. Preserve the records. Reduce the cost.
Preserve historical ERP, HR, payroll, workforce and operational records while retiring costly legacy applications.
Rarely because the application is still needed. Almost always because a specific obligation or a specific group of users still depends on what is inside it.
Prior-year ledgers, closed periods, supplier history and capital records needed for comparatives and audit.
Internal and external audit asking for transaction-level evidence from years already closed.
Historical pay, deductions, pension contributions and year-end records queried long after a pay period closes.
Assignment and employment history for current staff, leavers and returners, including bank and agency workers.
Statutory response deadlines that assume the record can be found, not that a system can be rebuilt.
DSARs requiring retrieval of an individual's records across finance, HR, payroll and workforce systems.
Records subject to litigation, inquiry or investigation that cannot be disposed of on the normal schedule.
Scanned invoices, contracts and correspondence stored inside the application rather than alongside it.
Retention periods measured in years or decades that the organisation must be able to evidence it is meeting.
A sequence, not a product install. Each stage produces something the next stage and the eventual retirement decision depend on.
Extracts structured and unstructured data — including the attachments and documents that usually get left behind.
Explore DataMove →Retains historical information securely, under retention rules and with reconciliation evidence attached.
Explore DataVault →Provides role-controlled access without maintaining the legacy application.
Explore DataLens →An NHS body cannot switch off a system on the strength of an assurance that the archive looks complete. Every extract is reconciled back to source and the evidence is retained as part of the decommissioning pack.
Illustrative figures shown to explain how reconciliation evidence is presented. They are not drawn from a specific customer engagement.
The archive is designed so that the obligations currently justifying the legacy application are met by the archive instead.
SyntraETL provides the technical capability to implement your retention and information-governance decisions. It does not provide legal advice, and it does not make retention or disposal decisions on the organisation's behalf.
Engagements start with the administrative estate — finance, procurement, HR, payroll and workforce systems — where the retention rules are well understood and the licence and hosting savings are immediate.
Financials, procurement, HR, payroll and the attachments held against them.
Finance, procurement and HR records from SAP ECC and earlier releases.
Effective-dated HCM and financials history including leavers.
Finance, procurement and HR records from Agresso-era deployments.
Timecards, schedules, accruals and workforce history.
Pay runs, elements, deductions, payslips and year-end records.
Assignment history, absence and employment records.
Bespoke departmental databases built around the main platforms.
SyntraETL is not a replacement EPR or clinical system, and this service does not position itself as one. Clinical application data can be assessed as a separate engagement with its own clinical safety and information-governance review; it is not in scope of an administrative Legacy Exit.
The financial case is usually straightforward once the annual cost of keeping the application alive is added up honestly — licence or support renewal, hosting, database and storage, backup and DR, patching and security remediation, and the DBA and application-support time nobody bills to it.
Illustrative example. Actual savings depend on the system, contract terms, infrastructure, support model, retention requirements and implementation scope. Estimated three-year saving in this example: approximately £405,000.
Illustrative example — actual savings depend on system, contracts, infrastructure and retention requirements.
Published SyntraETL engagements on the same architecture. Every figure below comes from the referenced case study rather than from a marketing claim.
A multi-hospital health system archived 18 data areas of timekeeping history into DataVault with reconciliation evidence, then ran a ten-stage decommissioning.
Read the case study →Historical records retained in a searchable archive so the source environment could be reduced.
Read the case study →Clinical and administrative records preserved in a compliant archive after the source application was retired.
Read the case study →An NHS Legacy Exit Assessment establishes which applications are being kept 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.