Legacy application retirement · any ERP, HR, payroll or document system
The system is replaced. The servers are still on. We fix the second part.
Every enterprise application you have ever replaced is still running somewhere: unpatched, unsupported, in scope for every audit, and holding the only copy of records you are required to keep. Nogalis archives it into your own AWS account and lets you shut it down.
We have not archived every system on this page. We have archived enough of them to know the method is the same, and we will tell you on the first call whether yours is one we have seen.
What you get back
A decommissioned server, a smaller attack surface, and every record still answerable.
- ✓The old hosting, licensing, DBA time and DR spend stops.
- ✓The unsupported OS and database leave your pen-test scope for good.
- ✓Retention, audit and legal-hold obligations are met from one read-only archive.
- ✓The last person who knew the old system stops being a single point of failure.








What a retirement is worth
Four things change the day the old system goes dark.
Hosting, database licensing, maintenance contracts that no longer buy patches, backup storage, DR copies, and the DBA hours that keep a system nobody transacts in alive. Most of it is invisible until someone adds it up.
Legacy applications run on the operating systems, Java runtimes and databases that stopped getting security fixes years ago. They are the finding on every penetration test and the box your cyber-insurer asks about. Retiring one removes the finding, not just the workaround.
Payroll, tax, HR, financial, procurement and patient-adjacent records carry retention windows of three to ten years, longer under litigation hold. The archive meets them from one place, with the record in the form it was created, not a flat file someone exported in a hurry.
An auditor, a regulator, or opposing counsel asks for a record. Today the answer depends on whether the one person who remembers the old system is still employed. Afterward, any authorized user finds it in seconds, with the audit trail.
Systems we retire
If it has a database behind it, it can be archived and shut down.
These are the systems we are asked about most. Infor Lawson and Kronos Workforce Central have their own pages because we have retired many of each. The rest are listed because the question comes up, not because we claim a trophy for every one.
ERP and financials mid-market
- Infor Lawson S3, Landmark, GHR
- Infor CloudSuite, SyteLine, LN, M3, and the on-premises generations behind them
- Microsoft Dynamics GP, NAV, AX, and SL
- Sage 100, 300, 500, and X3
- Epicor, including Prophet 21 and Eclipse
- JD Edwards World and EnterpriseOne
- Oracle E-Business Suite and PeopleSoft Financials
- Tyler Munis, Eden, and New World; Infor Public Sector
- Ellucian Banner and Colleague
- Unit4 Agresso, Deltek Costpoint, QAD, IFS, and Ross
HR, payroll and time people records
- UKG Workforce Central (Kronos)
- UKG Pro on-premises and UltiPro
- PeopleSoft HCM
- ADP Enterprise and ADP PayForce
- Ceridian HPL and Dayforce predecessors
- Oracle HRMS
- Infor HR and Lawson Payroll
- API Healthcare, Kronos Scheduler, and other time-and-attendance systems
Document and content management scanned and generated records
- MHC Software (EngageCX, Image Express)
- Hyland OnBase
- ImageNow and Perceptive Content
- Ascend and other HR document systems
- Infor Document Management (IDM)
- Laserfiche, Kofax, FileNet, and Documentum
- Check images, remittance advices, W-2s, 1099s, and the print files that came out of the ERP
Not on the list? That is normal. Describe the system on the discovery call: what it runs on, roughly how much data, and what people still ask it for. If the answer is honest about anything we have not done before, it will be honest about this too.
Why the system does not matter
Every retirement is the same five steps.
- DiscoverWhat runs where, how big the database is, where the attachments live, who still asks the system for what, and which retention rules apply. Then a demo on data like yours, then a quote.
- Extract everythingEvery table, every row, every attachment and generated document. We do not cherry-pick the tables the new system wanted. The ones it did not want are the ones the auditor wants.
- Prove itRow counts, control totals, and sampled comparisons against the production system, run by automation and then checked by a person. You get the report before anything is turned off.
- Deploy into your AWS accountServerless, read-only, encrypted with your keys, behind your single sign-on. Fully managed by Nogalis. Nothing for your team to patch.
- Shut it downYou approve the validation. The servers go dark. The licensing stops. The pen-test finding disappears. The records are still there.
What makes a system archivable
A relational database we can read: SQL Server, Oracle, DB2, Informix, Progress, MySQL, PostgreSQL. A file store for attachments, images, or print output. And people who can show us the three or four screens they still open.
That describes nearly every enterprise application built in the last thirty years. It also describes the ones whose vendor is gone, whose partner stopped answering, and whose last upgrade is older than some of your staff.
The exceptions are rare and specific — proprietary file formats with no database, or systems whose data lives only inside a vendor cloud you no longer have a contract with — and we name them on the first call rather than the last.
“Nobody gets promoted for keeping the old server alive. People get fired when it is breached, or when the record on it cannot be produced.”
How we frame every retirement decision
Questions we hear every time
Straight answers
Have you archived my specific system before?
What do you actually need from the old system?
Will people be able to use it, or is it a SQL dump with a search box?
Where does the data live, and who can see it?
How long does it take, and when can we shut the servers down?
What does it cost?
Name the system. We will tell you if we can retire it.
Thirty minutes with a Nogalis engineer. Bring the name of the application, what it runs on, and what people still ask it for. You leave with a straight answer and, if the answer is yes, a demo on data like yours. Pricing follows the demo.
