# Modernization without disruption: Rethinking the rip-and-replace mindset

DevFeed: [Modernization without disruption: Rethinking the rip-and-replace mindset](<https://devfeed.tech/articles/modernization-without-disruption-rethinking-the-rip-and-replace-mindset-63215.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4229004/modernization-without-disruption-rethinking-the-rip-and-replace-mindset.html>)

Author: Chris Carreiro

Published: 2026-10-01T11:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>), [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>), [finops](<https://devfeed.tech/topics/finops.md>)

Tags: [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [digital-transformation](<https://devfeed.tech/tags/digital-transformation.md>), [digital-transformation-it-leadership-it-management](<https://devfeed.tech/tags/digital-transformation-it-leadership-it-management.md>), [investment](<https://devfeed.tech/tags/investment.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [it-management](<https://devfeed.tech/tags/it-management.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [migration](<https://devfeed.tech/tags/migration.md>), [modernization](<https://devfeed.tech/tags/modernization.md>), [operational-risk](<https://devfeed.tech/tags/operational-risk.md>), [security](<https://devfeed.tech/tags/security.md>)

## AI overview

The article argues that modernization should prioritize changes based on business value, operational risk, future needs and available engineering capacity rather than replacing technology solely because it is old. It discusses weighing infrastructure changes against competing demands such as AI, and considering security and access changes when existing systems remain viable.

## Source excerpt

I've seen organizations reach a point in a modernization program where the technology itself is no longer the biggest risk. A decision was made for a full rip-and-replace. The new environment is ready. The migration plan has been tested. The business case has been approved. But the team responsible for delivering it is also responsible for keeping the existing estate running. A change freeze is approaching; business units are nervous about the cutover and what started as a technology upgrade has become an exercise in managing operational risk. That is the uncomfortable reality behind many large-scale modernization programs. We often make assumptions that legacy infrastructure is the problem and replacement is the solution, but in practice, rip-and-replace can create as much disruption as it removes. So rather than asking -- what do we need to modernize, CIOs should be asking a more practical question -- what needs to change right now? Do we really need to change everything? The reality is, there is only so much an organization can take on at once. AI is demanding investment and attention, workplace technology is changing, security expectations continue to rise and the existing estate still must keep running reliably in the background. All those priorities are competing for the same budgets, infrastructure and crucially, the same people. Modernization shouldn't mean replacing technology simply because it is getting older. It should mean focusing time and investment where change will make the biggest difference. Modernization needs triage, not a starting gun With legacy technology, age is usually the trigger for change. A platform reaches a certain point in its lifecycle, an OEM support deadline approaches or a newer alternative becomes available, and replacement can start to feel like the obvious next step. But the age of an asset doesn't necessarily tell us whether it is still doing its job, or whether replacing it is the right decision. A better approach is to assess