New Research from Precisely and ASUG Reveals SAP Modernization Momentum as AI Adoption Accelerates and Migration Challenges Intensify

Precisely and ASUG reported that 67% of surveyed organizations are fully or partially migrated to SAP S/4HANA, up from 59% in 2025 and 50% in 2024; another 23% expect to migrate within 24 months. AI adoption remains mostly assistive: 46% use AI across automated and human-assisted tasks, while 3% report fully automated AI-driven processes. Best-of-breed automation adoption rose to 33% from 19% in 2025, though legacy customization, integration and data quality remain obstacles; Precisely also announced Automate MCP Server and native OData support.

Analysis

The investable signal is migration urgency, not an AI-adoption inflection. ECC deadlines can pull forward SAP upgrade decisions and extend demand for implementation, data-cleaning, and integration work; however, the survey’s “fully or partially migrated” measure does not establish completed conversions, contract value, or SAP revenue conversion. The gap between broad AI-interface use and scarce fully autonomous workflows argues against pricing near-term agent-led productivity gains into enterprise software economics.

Second-order risk for SAP: best-of-breed automation and Microsoft’s prominent role as an AI interface may leave SAP as the system of record while others capture workflow engagement and incremental automation spend. That could constrain BTP/Joule attach, although the survey does not measure customer spend or displacement. Complexity and hybrid environments also support demand for specialist integration and data-quality providers, but Precisely is not a mapped public equity.

Near term (days): this company-sponsored release is weak evidence for a material estimate revision. Over 1–3 months, watch SAP cloud/backlog disclosures, migration-related guidance, and evidence that customers convert pilots into paid production use. Over 6–18 months, the key question is whether ECC urgency converts to completed S/4HANA deployments and SAP platform monetization—or whether customization and clean-core work delay projects and broaden third-party capture. The contrarian point: migration penetration may look advanced while partial conversions and hybrid estates leave a long, costly tail; conversely, the AI narrative is ahead of demonstrated autonomous use. Falsify the constructive view if SAP reports weaker cloud/backlog momentum or continued project delays; strengthen it if paid production deployments and platform attachment improve.

Key Decisions for Investors

• No immediate trade from this release alone: treat it as a modest demand-supporting datapoint for SAP, not proof of incremental earnings or AI monetization.
• Watch SAP’s next results for cloud backlog/revenue commentary, S/4HANA conversion pace, and BTP/Joule attachment. Consider adding SAP exposure only if those measures confirm migration urgency is converting into paid platform demand; reduce the thesis if guidance or backlog momentum weakens.
• Do not infer a Microsoft-versus-SAP winner from AI-interface usage. Track whether customers standardize automation on Microsoft tools, SAP-native offerings, or third-party platforms; that allocation is the key competitive catalyst.
• Monitor implementation delays, customization scope, and data-readiness spending over the next 6–18 months. A widening gap between announced migrations and completed deployments would undermine the near-term SAP benefit while supporting specialist integration and data-quality providers.