News | 02.06.2026
Migrating from SAP MII and SAP ME to SAP Digital Manufacturing is not a product swap. It is an architecture decision – and the choice you make about your industrial data foundation determines whether the migration scales across plants or collapses into a site-by-site engineering project.
An industrial data foundation is not optional here – it’s a prerequisite. With a secure, standardized and seamlessly integrated shop floor layer, the SAP DM migration becomes plannable and efficient. And a plant-by-plant rollout becomes a repeatable process.
Expert article by
Lara Ludwigs
VP of Commercial, Cybus
By December 31, 2030, SAP ends mainstream support for SAP ME and SAP MII. Functional development of both systems has already stopped – only security patches remain. The question over the next four years is not whether to migrate, but how. Companies that define their target architecture now can approach the SAP DM migration proactively – and build an AI-ready, future-proof data architecture in the process, rather than making reactive decisions under time pressure.
SAP Digital Manufacturing is designed for transactional MES processes: order execution, quality events, confirmations. Not for the layer where your shop floor actually lives. For brownfield environments across 10, 50, or 100+ plants, this creates three structural problems:
These are not edge cases. They are the standard situation in every brownfield SAP DM migration we see.
SAP DM is not designed to handle OT loads directly. Data heterogeneity and sovereignty remain critical challenges for plant operators – regardless of which MES sits above.
The solution: machine and process data is captured, normalized, and contextualized in an OT-adjacent data foundation layer. IT systems like SAP DM access real-time shop floor data via standardized APIs. At the same time, the company retains full control over which data moves to the cloud, reducing cloud costs and minimizing the attack surface.
This architecture follows the Unified Namespace (UNS) model: one structured, central source of truth for all plant data, decoupled from any consuming system. The shop floor publishes. SAP DM, quality systems, energy management and AI applications subscribe.
Cybus Connectware is exactly that data layer. Manufacturers running our Industrial DataOps software are prepared not just for the SAP DM migration – but for the (AI) transformation after that one, too.
SAP’s move to DM is one of many technological transformations ahead of us. Companies need a scalable, flexible and future-ready data strategy to maintain control over production data while ensuring seamless IT/OT integration.
| Metric | ❌ Migrating to SAP DM without a data Foundation | ✅ Migrating to SAP DM with Cybus Connectware |
|---|---|---|
| OT Integration | ❌ High effort: manual per-machine configuration, limited protocol coverage | ✅ Efficient: 100+ industrial connectors, configuration-driven, legacy equipment included |
| Real-Time Processing | ❌ Not possible: raw shop floor data pushed directly to the cloud | ✅ Guaranteed: edge-level filtering, aggregation, and contextualization at low latency |
| Custom Logic | ❌ Lost: ME/MII business logic must be rebuilt in Process Designer or mapped via BTP workarounds | ✅ Preserved: containerized edge environments (JSONata, bring-your-own-container) – existing logic survives without breaking SAP standards |
| Rollout Model | ❌ Site-by-site: every plant starts from zero | ✅ Scalable: first plant becomes a template; each additional site requires less effort than the last |
| Time to Migration (per site) | ❌6–18 months: manual configuration, custom scripting, debugging cycles | ✅ 2–5 months: automated IT/OT integration, pre-built connectors, modular templates |
| FTEs Required | ❌ 5–10 FTEs across IT, OT, and SAP teams | ✅ 1–3 FTEs: Cybus Connectware handles the integration work for you or your SI team |
| Production Downtime | ❌ High risk with every configuration change | ✅ Near-zero: CI/CD pipelines, blue/green deployments, Infrastructure-as-Code |
| Data Sovereignty | ❌ Limited: SAP DM and Event Mesh are cloud-native | ✅ Full: production data structured and stored vendor-neutrally, on-premises |
| Future Readiness | ❌ Vendor lock-in: the next SAP roadmap shift triggers the next migration | ✅ Future-Proof: vendor-neutral OT layer outlasts the next MES change |
The architecture decision has a direct financial mirror. While a typical SAP DM migration requires manual configuration, external SAP consultancy, production halts and debugging cycles, a migration based on a data foundation such as Cybus Connectware reduces costs and effort significantly.
The comparison alone makes the ROI obvious – before any of the additional use cases that holistic data access enables. At line-item level across a typical multi-site migration program:
| Cost Factor | ❌ Without Connectware | ✅ With Connectware | Savings |
|---|---|---|---|
| External SAP Consultants | €200K – €800K | €50K – €200K | Up to €600K |
| IT/OT Engineering (FTE) | 5-10 FTEs, ~€500K/year | 1-3 FTEs, ~€150K/year | Up to €350K |
| Production Downtime | €1M per hour of disruption | Near-zero with parallel integration | €1M+ per avoided hour |
| Rework & Debugging | €100K – €500K+ over time | Minimal | Up to €400K |
Mainstream support for SAP MII and SAP ME ends December 31, 2030. Four years sounds like plenty of time – until you start planning a rollout across 20, 50, or 100 plants. Decide the data layer now and you spend 2026–2030 migrating in templates. Wait and you spend 2029–2030 firefighting a plant-by-plant integration project under deadline pressure, with no fallback in ME/MII.
Cybus Connectware is the data foundation that makes the SAP DM migration work at enterprise scale – vendor-neutral, on-premises, and built to outlast the next SAP product transition after this one.
Whether you’re still scoping or already mid-rollout – we’ll show you exactly where a vendor-neutral data foundation layer shortens your timeline, reduces cost, and takes risk off the table.
You need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Turnstile. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Embedded Content. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information
