Skip to main content

The State of Application Modernization

Alisha Marfatia
EvolveWare

As businesses continue to rely heavily on technology to drive growth and innovation, the importance of modernizing outdated applications has become a top priority for CIOs and IT teams. With this in mind, EvolveWare commissioned an independent survey to gain current insights into IT teams' strategies and preparedness for modernization initiatives, revealing some surprising contradictions to common assumptions around modernization priorities and goals. It has also highlighted a curious disconnect between IT leaders' perception and the reality of their overall readiness, their ability to secure legacy talent, and the availability of the much-sought-after technology capabilities.

Jump to infographic below

Key findings include:

Confidence in understanding of applications wanes as projects progress

A comparison of the confidence in knowledge of applications being modernized between those who have not yet begun their modernization projects (41% very confident) to those who have already begun projects (28% very confident) reveals a notable drop. This is likely an indication that organizations only start to realize the level of knowledge needed for these efforts after they execute on the project plans.

Many respondents also base their confidence on having personnel with knowledge of these legacy systems. This is a clear blindspot for IT leaders, as a full 81% of respondents say they currently have — or anticipate — challenges hiring and/or retaining legacy programming talent. This shortage of specialized IT talent will only continue to grow as employees retire and expertise in legacy systems continues to decline.

IT Teams and the rest of the C-Suite may not be aligned on modernization goals

The number one modernization motivation for IT team respondents is boosting employee productivity (40%). This is opposed to commonly cited rationales such as improving customer experience (29%) and migrating to the cloud (22%). However when looking at success measures, increasing business efficiency is in the bottom two chosen, which boosting employee productivity would typically be related to. This discrepancy seems to imply that while IT teams are looking to address challenges they face with maintaining legacy applications, possibly due to lack of documentation and/or lack of qualified personnel, they must also justify these projects in terms that are important to business leadership.

Reasons most often cited by the C-Suite for modernization are directly related to increasing revenue and profits, such as moving to the cloud to improve customer experience and reduce costs. The disconnect indicates that IT teams, who have their own modernization motivations, must find ways to align with the C-Suite who are defining tangible measures of success, prior to executing on these projects.

IT teams lack of awareness and access to modern tools

Most respondents don't believe they have access to the capabilities they want. For example, more than half would like to automate code transformation and business rules extraction (BRE) to a large degree, and 40% want to automate application documentation creation. Similarly, 64% believe freezing code during the modernization process will have significant business and financial consequences, and a full 59% say the ability to modernize without freezing code is on their technology wish list, making it the top most requested modernization capability. Yet while these, and other technologies on their wish lists, are available in the current modernization market, no more than 31% of IT leaders say they have access to them.

The ability to successfully modernize will be a key differentiator for businesses as they navigate the ever-evolving digital landscape. While the process can be complex and challenging, insights into potential blind spots and disconnects can help IT leaders develop more effective strategies and make the most of their available resources and technological advancements.

Alisha Marfatia is a Product Strategist at EvolveWare

The Latest

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

The State of Application Modernization

Alisha Marfatia
EvolveWare

As businesses continue to rely heavily on technology to drive growth and innovation, the importance of modernizing outdated applications has become a top priority for CIOs and IT teams. With this in mind, EvolveWare commissioned an independent survey to gain current insights into IT teams' strategies and preparedness for modernization initiatives, revealing some surprising contradictions to common assumptions around modernization priorities and goals. It has also highlighted a curious disconnect between IT leaders' perception and the reality of their overall readiness, their ability to secure legacy talent, and the availability of the much-sought-after technology capabilities.

Jump to infographic below

Key findings include:

Confidence in understanding of applications wanes as projects progress

A comparison of the confidence in knowledge of applications being modernized between those who have not yet begun their modernization projects (41% very confident) to those who have already begun projects (28% very confident) reveals a notable drop. This is likely an indication that organizations only start to realize the level of knowledge needed for these efforts after they execute on the project plans.

Many respondents also base their confidence on having personnel with knowledge of these legacy systems. This is a clear blindspot for IT leaders, as a full 81% of respondents say they currently have — or anticipate — challenges hiring and/or retaining legacy programming talent. This shortage of specialized IT talent will only continue to grow as employees retire and expertise in legacy systems continues to decline.

IT Teams and the rest of the C-Suite may not be aligned on modernization goals

The number one modernization motivation for IT team respondents is boosting employee productivity (40%). This is opposed to commonly cited rationales such as improving customer experience (29%) and migrating to the cloud (22%). However when looking at success measures, increasing business efficiency is in the bottom two chosen, which boosting employee productivity would typically be related to. This discrepancy seems to imply that while IT teams are looking to address challenges they face with maintaining legacy applications, possibly due to lack of documentation and/or lack of qualified personnel, they must also justify these projects in terms that are important to business leadership.

Reasons most often cited by the C-Suite for modernization are directly related to increasing revenue and profits, such as moving to the cloud to improve customer experience and reduce costs. The disconnect indicates that IT teams, who have their own modernization motivations, must find ways to align with the C-Suite who are defining tangible measures of success, prior to executing on these projects.

IT teams lack of awareness and access to modern tools

Most respondents don't believe they have access to the capabilities they want. For example, more than half would like to automate code transformation and business rules extraction (BRE) to a large degree, and 40% want to automate application documentation creation. Similarly, 64% believe freezing code during the modernization process will have significant business and financial consequences, and a full 59% say the ability to modernize without freezing code is on their technology wish list, making it the top most requested modernization capability. Yet while these, and other technologies on their wish lists, are available in the current modernization market, no more than 31% of IT leaders say they have access to them.

The ability to successfully modernize will be a key differentiator for businesses as they navigate the ever-evolving digital landscape. While the process can be complex and challenging, insights into potential blind spots and disconnects can help IT leaders develop more effective strategies and make the most of their available resources and technological advancements.

Alisha Marfatia is a Product Strategist at EvolveWare

The Latest

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...