New Saritasa Research Finds Legacy Software Specialists Disappearing as Internal IT Teams Absorb Aging Systems

Saritasa’s survey of 513 IT professionals found that 68% of organizations depend on at least one legacy software system, up from 62% in 2025. Security vulnerabilities were cited by 54% of respondents, up 11 percentage points, and high maintenance and support costs by 52%, up 13 points; dedicated legacy specialist coverage fell from 20% to 12%. Modernization priorities increasingly center on integration, scalability and security, while execution concerns—including operational disruption and data migration—remain barriers.

Analysis

Legacy modernization is a delayed-spend signal, not yet a revenue signal. The key mechanism is that integration and data-access work can precede wholesale system replacement: if firms pursue AI without migrating core systems, demand may accrue first to API, data-engineering and systems-integration providers, while cloud infrastructure vendors benefit only when workloads actually move. Phased projects also create a second-order risk: prolonged parallel-run and migration costs could crowd out new transformation budgets or trigger pauses after operational disruption.

The evidence is weak for near-term positioning. This is a vendor-sponsored survey, not verified bookings, budget growth or project starts; reported pain can rise while procurement remains frozen. Saritasa’s commercial interest is relevant, and the broad respondent mix limits inference about large-enterprise spending. Over the next 1–3 months, look for corroboration in Accenture, IBM and Cognizant commentary on modernization pipeline conversion, project delays and realized revenue—not just AI demand. Over 6–18 months, sustained specialist attrition and security exposure could raise urgency, but execution failures or budget pressure could extend deferrals. The contrarian point: “systems still work” may be economically rational where replacement risk exceeds maintenance cost; survey sentiment does not establish a wave of imminent upgrades.

Key Decisions for Investors

• No trade on this release alone. Treat it as a watch signal for Accenture, IBM and Cognizant, not evidence to add exposure before bookings or guidance corroborate spending.
• Over the next 1–3 months, monitor modernization backlog conversion, project cancellations and revenue commentary from services firms; favor evidence of integration and data-layer work converting into billable projects over generalized AI pipeline claims.
• Watch security incidents, outage disclosures and executive budget approvals as catalysts for faster modernization. A rise in reported pain without stronger bookings or guidance would falsify the near-term demand thesis.
• Avoid assuming hyperscaler upside from modernization intent: confirm workload migration and consumption trends before expressing a cloud-infrastructure view. Survey methodology, respondent company-size mix and actual project-spend data remain key gaps.