News | 02.06.2026

SAP DM Transition is a Data Architecture Decision

Why Cybus Connectware is the Data Layer for Your SAP MII/ SAP ME to SAP Digital Manufacturing

Migrating from SAP MII and SAP ME to SAP Digital Manufacturing (SAP DM) is not a product swap. It is a data architecture decision – and the choice you make about your industrial data layer determines whether the migration scales across plants or collapses into a per-site project.

Cybus Connectware is the data layer that makes that decision work: connecting what SAP DM’s Production Connector cannot, processing data the cloud was never built to handle, preserving the custom logic SAP DM strips out – and turning a plant-by-plant integration project into a templated rollout.

Picture of Lara Ludwigs, Head of Marketing at Cybus

Expert article by

Lara Ludwigs
VP Commercial, Cybus

The SAP MII and SAP ME End-of-Life deadline is hard. The decision is now.

By December 31, 2030, SAP ends mainstream support for SAP ME and SAP MII. Functional development of both stopped already – only security patches remain. The question over the next five years is not whether to migrate, but on what data architecture.

Decide now, and you define your target landscape. Wait, and you inherit one – assembled from whatever Production Connector configurations, BTP workarounds and per-site custom integrations you have left at the end of 2029.

That decision is the data layer. Everything else is downstream of it.

What that means in practice: brownfield equipment onboarded by configuration instead of code. Data filtered and contextualized at the edge before SAP DM ever sees it. Custom logic SAP DM removes, preserved in containerized environments. Plant rollouts turned into templates instead of new projects. The rest of this article explains why SAP DM’s own tooling cannot do this – and what changes when Cybus Connectware sits in the middle.

SAP Digital Manufacturing (DM) is a cloud MES – not an enterprise integration layer

SAP DM is built for the cloud and for transactional MES processes – order execution, confirmations, quality events. Not for the part of the manufacturing stack where your shop floor lives.

For brownfield environments across 10, 50 or 100+ plants, that creates three structural gaps:

  1. No real-time processing for high-frequency shop floor data.
    Sending PLC-level data directly into SAP DM is architecturally wrong: it overloads the system, drives cloud cost and offers no edge-level processing for time-critical decisions on the floor.
  2. SAP DM’s Production Connector is the only SAP-native OT path – and it is insufficient for enterprise scale.
    It replaces SAP Plant Connectivity (SAP PCo), which SAP discontinued together with MII. The successor runs on Windows, requires manual case-by-case configuration and has limited protocol coverage. SAP DM SDKs for common industrial protocols such as S7 or CSV are not generally available; customers report writing their own C# connectors. For a 120-plant rollout planned over eight years, that is not an integration approach – it is an integration risk that compounds with every site. Concrete example: the ProdCon installer refuses to install when a Proficy Historian agent is active on the same host — a single legacy connector blocks the rollout on that line.
  3. The custom logic from ME/MII does not transfer.
    You spent years building business logic into your MES landscape – soft logic, custom transactions, plant-specific process flows. SAP DM removes most of that flexibility by design. Without an OT-adjacent layer, every plant rebuilds in Process Designer, falls back to BTP workarounds or loses functionality outright.

These are not edge cases. They are the standard situation in every brownfield SAP DM migration we see.

“The companies that will get the SAP DM migration right aren’t the ones with the best MES strategy. They’re the ones who decided their data layer first.“

— Lara Ludwigs, VP Commercial Cybus

The architecture that makes the SAP DM migration work: Cybus Connectware as the industrial data layer

SAP DM is not built to handle OT load directly – and SAP’s own answer to that, the Production Connector, is not sufficient for brownfield at scale. The alternative: capture, normalize and contextualize machine and process data in an OT-adjacent data layer. SAP DM consumes only the business-relevant events it actually needs – at the cadence it can handle.

This is the Unified Namespace (UNS) model: one structured source of truth for all factory data, decoupled from any consuming system. The shop floor publishes. SAP DM subscribes. So do quality, energy, analytics and AI systems.

Cybus Connectware is that data layer. Not a migration tool. The infrastructure that makes the SAP MII, SAP ME and SAP PCo migration to SAP DM possible at enterprise scale. For SAP DM environments specifically, Cybus Connectware:

  • Connects what SAP DM’s Production Connector cannot. 100+ industrial connectors including proprietary and legacy protocols. Brownfield equipment that would otherwise require custom C# work is onboarded by configuration, not code.
  • Decouples OT load from SAP DM. High-frequency machine data is filtered, aggregated and contextualized at the edge – SAP DM consumes only the business-relevant events at the cadence it can handle.
  • Preserves the customization SAP DM removes. Soft logic and complex processing run in containerized environments at the edge – JSONata for transformations, bring-your-own-container for custom code – keeping the business logic from ME/MII alive without breaking SAP standards.
  • Scales by template, not by project. One plant becomes a blueprint. Each additional site requires less effort than the last. One multi-site European appliance manufacturer rolls out one brownfield factory per month on this model.
  • Deploys without production halts. CI/CD pipelines, blue/green deployments, and Infrastructure-as-Code mean configuration changes do not require stopping production. For automotive customers, every hour of unplanned downtime costs approximately €1M.
  • Keeps your data sovereign – and on-premises by default. Production data is structured and stored vendor-neutrally, outside SAP. For plants with strict data residency, offline-tolerance or air-gap requirements, this is a hard prerequisite: SAP DM and Event Mesh are cloud-native, and the OT layer cannot follow them there. If SAP’s roadmap shifts again – and over a 15-year horizon, it will – the data layer does not need to be migrated with it.

9 things that change with Cybus Connectware in your SAP DM migration

SAP’s move to DM is only the beginning. 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 AN OT data layer ✅ Migrating to SAP DM with Cybus Connectware
OT Integration Complexity❌ High: SAP DM’s Production Connector, manual per-machine configuration, Windows-bound, limited protocol coverage, no native support for legacy or proprietary protocols✅ Low: 100+ industrial connectors, configuration-driven, deployment on Kubernetes, Docker or hybrid
Real-Time Processing❌ Not possible: SAP DM has no local edge processing; raw shop floor data forced into the cloud✅ Guaranteed: edge-level filtering, aggregation, contextualization – instant decisioning on the floor
Customization Flexibility
❌ Limited: SAP DM removes most ME/MII business logic; rebuild in Process Designer or push to BTP as workaround
✅ Open: containerized edge environments (JSONata, bring-your-own-container) – keep your existing logic without breaking SAP standards
Rollout Model
❌ Per-site engineering project; every plant repeats the integration work		✅ Template-driven; site N+1 requires less effort than site N
Time to Migration (per site)❌ 12–24 months: ue to manual adaptation, custom scripting and debugging cycles✅ 3–6 months: with automated IT/OT integration, pre-built connectors, modular templates
FTEs Required❌ 5–10 FTEs: across IT, OT and SAP teams to manually map, configure and debug✅ 1–3 FTEs: Cybus Connectware automates the integration
Cost of Migration
❌ €500K–€3M+: per program – consultants, extended timelines, continuous troubleshooting		✅ €100K–€500K: up to 75% lower by eliminating manual integration, debugging and custom coding
Risk of System Downtime❌ High: configuration changes require production halts✅ Near-zero: Cybus Connectware runs in parallel; CI/CD and blue/green deployments without downtime
Future Readiness
❌ Locked-in: future SAP roadmap changes may trigger another complex migration		✅ Future-Proof: vendor-neutral OT data layer survives the next MES change and feeds analytics, quality, energy and AI systems from the same source of truth
Sources: Cybus partner data; industry benchmarks from TeamViewer 2024 (95% of businesses lack sufficient connectivity) and industry research on battery manufacturing ramp-up (€1–2bn revenue impact from a 6-month delay).

“We see it in every migration we’re called into: there’s no like-for-like move from SAP ME/MII to SAP DM. There’s only an architectural decision – and most companies are making it too late.“

— Lara Ludwigs, VP Commercial Cybus

Up to €2.3M saved per SAP DM migration program with Cybus Connectware

The architecture decision has a direct financial mirror. Where SAP DM’s Production Connector adds friction – manual configuration, external SAP consultancy, production halts, debugging cycles – Cybus Connectware removes cost.

At line-item level across a typical multi-site migration program:

Cost Factor❌ Without Connectware✅ With ConnectwareSAvings
External SAP Consultants€200K – €800K€50K – €200KUp to €600K saved
IT/OT Engineer Time (FTE)5-10 FTEs, ~€500K/year1-3 FTEs, ~€150K/yearUp to €350K saved
Downtime Costs€1M per hour of disruptionNear-zero with parallel integration€1M+ saved per avoided hour
Rework & Debugging€100K – €500K+ over timeMinimal rework neededUp to €400K saved

Total Savings Potential: €2.3M and more per migration project.

These ranges reflect what Cybus sees in real multi-site programs. Production Connector adds cost per machine, per plant, per update. Cybus Connectware removes cost per template, per rollout, per CI/CD cycle. Over a multi-site program, that compounds.

Four SAP DM migration decisions you and your organization need to make now

  1. Stop sequencing the data architecture decision after the MES decision. They are the same decision. The MES choice without a data layer choice is incomplete.
  2. Treat SAP DM’s Production Connector as one option, not as the default. It is sufficient for a small, homogeneous, cloud-native plant. It is not sufficient for enterprise brownfield at scale.
  3. Decide the data layer once, not per plant. A vendor-neutral, OT-adjacent UNS is the only architecture that survives the next two SAP product transitions after this one.
  4. Pilot the architecture, not the product. One brownfield plant, one template, six weeks. If the model holds, the rest is rollout.

The SAP DM migration is not optional. The data architecture decision is.

Five years sounds long. It is not. SAP DM functional gaps are still being closed. Rollouts to 10, 20, 50 plants take years. 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 layer that makes the SAP DM transition work at enterprise scale – vendor-neutral, on-premises, and built to outlast the next SAP product transition after this one.

Let’s talk about your SAP DM roadmap

Whether you’re scoping the migration or already mid-rollout, we’ll show you where a vendor-neutral data layer changes the timeline, the cost and the risk.


You could also be interested in:

News

The Greenfield Illusion: Why New Factories Still End Up with Old Problems

Learn more
Press release about Cybus being positioned as a major player in the IDC MarketScape Industrial DataOps Platforms 2026

News

IDC MarketScape: Worldwide Industrial DataOps Platforms 2026 Vendor Assessment: Cybus Positioned as a “Major Player”

Learn more

News

Hannover Messe 2026: AI Hype Meets the Missing Data Foundation

Learn more