Before You Replace the Legacy ERP, Learn What It Is Actually Doing
I spend much of my time helping organizations move from established enterprise systems to modern cloud platforms. Increasingly, that work has involved large public-sector transformations where the word legacy can mean many things: PeopleSoft, an older commercial ERP, a mainframe application, a custom database, or an ecosystem of systems and interfaces that has accumulated over decades.
When we begin these transformations, there is a natural tendency to focus on the destination.
But before designing the future state, a transformation team also needs a reliable understanding of what the legacy environment is actually doing today. That idea was reinforced for me at Ascend 2026, when I attended a presentation by Tirumala Rao Chimpiri (Tiru) on PS-CARE, the PeopleSoft Continuity Automation & Resilience Engine, a framework he developed.
What interested me as a transformation consultant was the possibility of using operational history during discovery. It could help us ask better questions about the systems we are preparing to transform.
The Legacy System Is Part of the Transformation
An organization may spend years planning, funding, designing, configuring, converting data, building integrations, testing, preparing for cutover, and stabilizing a new environment.
During those years, the legacy system does not suddenly become unimportant because it has a planned retirement date.
Payroll still has to run. Vendors still have to be paid. Financial periods still have to close. Interfaces still have to complete. Reports still have to be produced.
This is especially apparent in the public sector, where I frequently encounter environments that have evolved over many years and sometimes decades. What we casually call the "legacy system" may actually consist of an ERP, mainframe applications, data warehouses, agency-specific systems, scheduled interfaces, extracts, reports, and custom processes held together by both technology and institutional knowledge.
Higher education is a good example of this challenge. Institutions may depend on years of accumulated PeopleSoft processes supporting payroll, finance, student administration, reporting, and integrations while simultaneously preparing for a new ERP or cloud environment. Understanding which of those processes remain active, how they behave, and what depends on them can become an important part of transformation discovery.
Better visibility is not necessarily an investment in keeping the old platform forever. It can be an investment in making the transition away from it more successful.
For CIOs and ERP leaders, that distinction matters. The question is not whether to preserve legacy technology indefinitely, but whether better evidence about the current environment can reduce transition risk and improve decisions about what should be carried forward, redesigned, consolidated, or retired.
Featured
-
Microsoft, Nvidia Move Enterprise AI Toward Active Cyber Defense
AI security is entering a new stage as organizations look beyond protecting models from prompt injection, unauthorized access, and data exposure.
-
Anthropic, NVIDIA Move AI Agents Deeper into Scientific Workflows
Anthropic has introduced Claude Science, a new AI workbench for scientists that integrates research tools, produces auditable artifacts, and connects to specialized life sciences models and workflows from NVIDIA.
-
Anthropic Launches Lower-Cost Claude Sonnet 5
Anthropic has released Claude Sonnet 5, positioning the model as its most autonomous mid-tier offering to date and a lower-cost alternative to its flagship Opus 4.8 system. The company said the model can plan multi-step tasks, operate tools such as browsers and terminals, and complete agentic work at a level that previously required larger and more expensive models.
-
Cloud Security Alliance Recommends Separate Governance Model for 'Non-Human Identities'
A recent report urges organizations to inventory, govern, and continuously monitor machine and agent identities.