The sequence is familiar to any CFO who has sat through the renewal meeting. The core instance your organization has customized over a decade is declared end-of-life. Modern machine learning capability, real-time inventory tracking, and automated workflow orchestration are not available as modules against the existing install, they require the successor platform. The stated cost is a $10 million minimum, against a three-year rollout, while your engineering teams port millions of lines of custom database logic.
The base rates do not support the allocation. More than 70% of large ERP migrations exceed budget or stall entirely, and operational performance degrades across the migration window. The expenditure purchases replacement database infrastructure; it does not purchase optimization, which arrives years later if the program completes at all.
There is a second allocation path. The transactional core stays in place, and an event-driven orchestration layer is constructed above it.
Replacing an entire ERP to obtain real-time analytics is a capital substitution error: it acquires new infrastructure to solve an access problem.
Capital allocation matrix
| Metric | Core ERP replacement | Orchestration overlay |
|---|---|---|
| Capital expenditure | $10M+ baseline software allocation | Fraction of core infrastructure cost |
| Deployment timeline | 24 to 36 months minimum | 60 to 120 day operational window |
| Operational risk | Code breakage and database downtime | Non-invasive; sits above existing systems |
| Data strategy | Forced batch cycles and schema rewrites | Event-driven semantic translation |
The allocation argument
While technical teams work through field-mapping exercises, the sourcing market continues to move. A three-year wait for algorithmic forecasting, multi-tier visibility, and edge automation is a competitive position, not a neutral one. The alternative unlocks the latent utility of the databases already owned, extracting their real-time event logs and routing them to orchestration models that operate against current margin.
Verified system outcome
A high-volume B2B manufacturer deployed an event-driven semantic overlay above its legacy transactional systems rather than allocating capital to a core upgrade. Within a 60-day operational window, the deployment consolidated workflows across five fragmented warehouse and procurement locations. Measured results: 40% acceleration in quote-to-cash processing, a 30% reduction in picking errors, and a 35% reduction in localized safety stock overages, against an estimated 18-month migration that was not undertaken.
The decision is a capital allocation question, not a technology preference. One path funds infrastructure replacement on a three-year horizon. The other funds visibility and control layers inside a quarter.