Beyond ERP Modernization
Building a composable, intelligent enterprise technology foundation.
ERP modernization creates an opportunity to reconsider how work and information move across the enterprise. A new core platform may simplify important processes, but the surrounding landscape still matters: planning tools, commerce systems, reporting, integrations, and custom applications all influence the experience people actually have.
The current platform direction
At Sapphire in May 2026, SAP announced a Business AI Platform bringing together technology, business data, and AI capabilities. The announcement illustrates a vendor direction toward connected context and governance. It should not be interpreted as proof that every announced capability is available, suitable, or included in a particular customer contract.
Source: SAP — Sapphire 2026 Business AI Platform announcement (May 2026).
Map the surrounding decisions
Before changing the ERP core, identify the workflows that depend on it. An illustrative retailer may need consistent product, stock, order, and financial information across stores and digital channels. Replacing a finance component does not by itself resolve an inventory discrepancy exposed to a customer.
Trace the information journey: where a record originates, which systems may change it, how often it is refreshed, and who resolves a conflict. This map helps distinguish a core-platform problem from an integration, ownership, or data-quality problem. Those distinctions should influence the roadmap.
Choose extensions deliberately
A custom extension can protect a distinctive business process, but it also introduces maintenance and support responsibilities. For each extension, document why the standard process is insufficient, what business value the variation creates, and how it will be tested when the surrounding platform changes.
Apply the same discipline to AI capabilities. An assistant can make information easier to access, yet still give an unreliable answer if it reads stale or inconsistent data. Evaluate the information contract and permission model alongside the user interface. A conversational layer should not become a shortcut around process controls.
Plan a migration the business can operate
A migration plan should identify reconciliation points, responsibilities during transition, and criteria for switching to the new workflow. Test the cases that cross systems: returns, cancellations, corrections, late-arriving data, and changes to master records are often more revealing than a standard transaction.
The operating model after launch deserves equal attention. Assign ownership for integrations, monitoring, user support, and controlled changes. Include those costs when comparing options. The most attractive architecture diagram is not necessarily the most supportable solution for the team that must run it every day.