SAP ends mainstream maintenance for Manufacturing Execution (ME) and Manufacturing Integration & Intelligence (MII) on December 31, 2027. Extended Maintenance - a paid continuation with a reduced scope of support - runs through approximately 2030. That window has become a comfortable reason to defer the decision. The financial case for acting now is stronger than that framing suggests - and the costs below explain why.
The cost breakdown: what "staying on SAP ME" actually charges you
| Cost category | Type | What drives it |
|---|---|---|
| Extended Maintenance fee | Visible | ~2% of license value/year on top of standard 22% |
| Security incident exposure | Visible / Latent | Avg. $5.56M per breach in industrial sector (IBM 2024) |
| Production downtime from security event | Latent | Avg. $125,000/hour (ABB, 3,200 plants surveyed) |
| Custom maintenance overhead | Hidden | IT capacity consumed by legacy support instead of innovation |
| Talent premium | Hidden | Contracting specialist market, rising rates YoY |
| Implementation premium (if rushed) | Hidden | Higher partner rates, compressed timelines, risk of rework |
| Innovation opportunity cost | Strategic | Capabilities unavailable on SAP ME: AI analytics, IIoT, cloud |
Each row is a separate line of cost. None appear on a single invoice. The sections below put numbers on each one.
SAP ME Extended Maintenance costs: what the 22%+2% fee structure means in practice
SAP's standard Enterprise Support runs at 22% of net license value annually. Extended Maintenance, available from 2028, adds approximately 2% on top - bringing the effective rate to around 24% per year. (Source: SAP Licensing Experts)
Take a manufacturer with €10M in SAP ME license value. Extended Maintenance adds €200,000 per year to maintain a platform SAP has already decided to retire. Over the full 2028-2030 window, that is €600,000 in fees with no new features, no roadmap development, and security patches only for what SAP internally classifies as critical.
What Extended Maintenance covers is continued operation on a frozen platform. Active development stopped. Native IIoT integration is off the roadmap. AI-assisted production analytics require a different platform entirely. SAP ME's Extended Maintenance fee is, in practical terms, a charge for standing still.
SAP ME without security patches: the breach cost exposure after 2027
After December 2027, SAP stops issuing routine security patches for ME. Critical vulnerabilities may still get addressed under Extended Maintenance, but the definition of "critical" belongs to SAP.
An unpatched MES sitting between the ERP and the production floor is a documented attack surface. The IBM Cost of a Data Breach Report 2024 puts the average total cost of a breach in the industrial sector at $5.56 million - 13% above the global average of $4.88M and an 18% increase over 2023. Industrial organizations also take longer than average to detect and contain breaches: 199 days to identify, 73 days to contain. Source: IBM
That breach figure understates the exposure once production is involved. ABB's survey of over 3,200 global plant maintenance leaders found 67% of manufacturers experience unplanned downtime at least once a month, at an average cost of $125,000 per hour. The Siemens True Cost of Downtime 2024 report puts total unplanned downtime losses for the Fortune Global 500 at $1.4 trillion annually - 11% of their revenues.
A ransomware event on a legacy, unpatched MES stops production. The security question after 2027 is whether your organization will have vendor-backed remediation when a vulnerability appears - or whether it will be handling that alone.
How SAP ME's customization architecture consumes IT capacity
SAP ME's customization architecture shifts development capacity from building new capabilities to keeping existing ones operational. Every custom integration, every modified workflow, every bespoke report added to fill a gap in standard functionality becomes a maintenance liability. The older the platform, the heavier that load.
After 2027 there is no vendor roadmap pulling that customization forward. Custom code written for SAP ME will need to be rewritten, replaced, or retired before any migration can proceed - it travels nowhere automatically.
The capacity SAP ME's maintenance overhead consumes is capacity unavailable for integration projects, analytics initiatives, or the Industry 4.0 work the operations side is asking for. None of it shows up on a maintenance invoice - it accumulates as a backlog with no natural end date.
SAP ME specialist availability is shrinking - and contractor rates reflect it
The SAP ME specialist market is already contracting. December 2027 signals to every experienced SAP ME developer that their platform-specific knowledge has a hard expiration date. Nobody entering the field is learning it. The people who know it well are moving toward SAP Digital Manufacturing, cloud MES platforms, and modern integration stacks - client demand has shifted, and experienced engineers follow the work.
SAP ME's aging support window tightens the available pool of people organizations need to keep the system running. When a specialist is unavailable - for a critical bug, a compliance change, an urgent integration fix - that gap lands directly on production. The broader SAP migration market gives a sense of the direction: consulting fees for SAP legacy migrations rose 20% between 2023 and 2026, making them the single largest source of unexpected cost overruns in migration projects industry-wide. (Source: MSH, 2026) SAP ME is a narrower and more specialized market - the same supply-side pressure applies with less capacity to absorb it.
The talent premium compounds as long as SAP ME remains in production, with no market mechanism to reverse it.
What DELMIA Apriso offers that SAP ME's architecture cannot
Manufacturers treating the 2027 deadline as a trigger for action are using this window to deploy capabilities SAP ME cannot natively provide.
DELMIA Apriso operates at ISA-95 Level 3 - the same production execution layer as SAP ME - with native IIoT device integration, real-time analytics, AI-assisted quality control, and cloud or hybrid deployment. Every quarter SAP invests development resources in Digital Manufacturing rather than ME, the functional gap between the two platforms widens.
The less obvious advantage is the implementation window itself. MES migrations for multi-site manufacturers typically run 12 to 18 months from kickoff to go-live. Integration complexity, data migration, process standardization, and operator training set the pace - none of those phases accelerate by throwing more budget at them. A decision made in 2028 lands production on the new platform in late 2029 at the earliest, with Extended Maintenance fees running the entire time.
SAP ME migration timeline: why a 2030 deadline requires a 2027 decision
The "we have until 2030" position misses what the timeline actually requires.
Working backward from December 2030:
- A 12-18 month MES implementation requires a project start no later than mid-2028 to reach a 2030 go-live.
- Vendor selection, business case approval, budget allocation, and project scoping add 3 to 6 months before that.
- The effective decision deadline lands at late 2027 - precisely when mainstream maintenance ends and Extended Maintenance fees begin.
An organization that decides in 2029 is running a forced migration under time pressure, paying Extended Maintenance fees throughout, competing for implementation capacity against every other manufacturer that also waited, and paying premium rates for the privilege. The additional cost is the rushed delivery premium, the compressed timeline risk, and the security exposure carried through the entire project duration.
| Decision point | Realistic go-live | Extended Maintenance exposure | Implementation conditions |
|---|---|---|---|
| 2025-2026 | 2026-2027 | None or minimal | Capacity available, no deadline pressure |
| 2027 | 2028-2029 | 1-2 years of fees | Moderate demand on implementation partners |
| 2028-2029 | 2029-2031 | 2-3 years of fees | High demand, compressed timelines, premium rates |
| 2030 | 2031+ | Full Extended Maintenance window | Forced migration after end of support |
DELMIA Apriso as SAP ME replacement: ISA-95 Level 3 coverage and what changes
DELMIA Apriso covers the same ISA-95 Level 3 functional scope as SAP ME: production execution, quality management, shop floor logistics, plant maintenance, and equipment integration. On top of that foundation it adds native IIoT connectivity, real-time production analytics, global multi-plant process standardization, and a vendor roadmap with active development funding behind it.
Real-world scale deployments confirm the difference. L'Oréal rolled out Apriso across 30+ plants alongside its global SAP ERP implementation, achieving full production traceability and raising the first-time-right production metric from 93.5% to 94.4%. SAP ME's architecture was not built for that kind of multi-site coordination at scale.
Migrating from SAP ME to Apriso is a redesign of manufacturing execution, with the opportunity to retire accumulated custom code, standardize processes across sites, and build an integration layer connecting production data to enterprise systems in real time. The organizations that do this well start with enough runway to make deliberate decisions. Those that start late carry their legacy constraints into the new platform.
The cost of waiting: SAP ME migration now versus forced migration in 2029
The instinct is to frame this as migration cost versus current cost. Both numbers matter, but the comparison stops too early.
The accurate comparison is what a controlled migration costs when started now, against what a forced migration costs starting in 2028 or 2029 - Extended Maintenance fees accumulating throughout, partner rates at their peak, and the security exposure of an unpatched system carried across the entire project duration. SAP ME running past 2027 generates costs across multiple categories in parallel. The Extended Maintenance fee is the one that appears on an invoice. The others are harder to see until they hit.
December 31, 2027. After that date, SAP stops issuing routine security patches and feature updates for SAP ME and SAP MII. Extended Maintenance is available through approximately 2030 at an additional ~2% of net license value per year, on top of standard Enterprise Support costs.
Standard Enterprise Support runs at 22% of net license value annually. Extended Maintenance adds approximately 2% on top of that, bringing the effective rate to ~24% per year. For an organization with €10M in SAP ME license value, that is €200,000 per year - €600,000 over the full 2028-2030 window - with no new features or active development included.
Multi-site MES migrations typically require 12 to 18 months from project kickoff to go-live, plus 3 to 6 months for vendor selection, scoping, and budget approval before that. Working backward from the 2030 end of Extended Maintenance, the practical decision deadline is late 2027. Organizations that commit in 2028 or later are working under time pressure, against peak demand for implementation capacity.
To discuss your migration timeline, contact our team.