{"id":52913,"date":"2026-06-02T18:08:00","date_gmt":"2026-06-02T16:08:00","guid":{"rendered":"https:\/\/www.cybus.io\/?p=52913"},"modified":"2026-06-03T18:52:50","modified_gmt":"2026-06-03T16:52:50","slug":"sap-dm-migration-data-layer","status":"publish","type":"post","link":"https:\/\/www.cybus.io\/en\/sap-dm-migration-data-layer\/","title":{"rendered":"SAP DM Transition is a Data Architecture Decision"},"content":{"rendered":"\n
\n

Why Cybus Connectware is the Data Layer for Your SAP MII\/ SAP ME to SAP Digital Manufacturing<\/h2>\n\n\n\n

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

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 \u2013 and turning a plant-by-plant integration project into a templated rollout.<\/strong><\/p>\n<\/div><\/div><\/div><\/div>\n\n\n\n

\n
\n\n\n\n
\n
\n
\"Picture<\/figure>\n<\/div><\/div>\n\n\n\n
\n

Expert article by <\/p>\n\n\n\n

Lara Ludwigs
VP Commercial, Cybus<\/em><\/p>\n<\/div>\n<\/div>\n\n\n\n

\n<\/div><\/div><\/div><\/div>\n\n\n\n
\n

The SAP MII and SAP ME End-of-Life deadline is hard. The decision is now.<\/strong><\/strong><\/h2>\n\n\n\n

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

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

That decision is the data layer. Everything else is downstream of it.<\/strong><\/p>\n\n\n\n

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 \u2013 and what changes when Cybus Connectware sits in the middle.<\/p>\n\n\n\n

\n\n\n\n

SAP Digital Manufacturing (DM) is a cloud MES \u2013 not an enterprise integration layer<\/strong><\/h2>\n\n\n\n

SAP DM is built for the cloud and for transactional MES processes \u2013 order execution, confirmations, quality events. Not for the part of the manufacturing stack where your shop floor lives.<\/p>\n\n\n\n

For brownfield environments across 10, 50 or 100+ plants, that creates three structural gaps:<\/p>\n\n\n\n

    \n
  1. No real-time processing for high-frequency shop floor data.
    <\/strong>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.
    <\/li>\n\n\n\n
  2. SAP DM’s Production Connector is the only SAP-native OT path \u2013 and it is insufficient for enterprise scale.
    <\/strong>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 \u2013 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 \u2014 a single legacy connector blocks the rollout on that line.
    <\/li>\n\n\n\n
  3. The custom logic from ME\/MII does not transfer.
    <\/strong>You spent years building business logic into your MES landscape \u2013 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.<\/li>\n<\/ol>\n\n\n\n

    These are not edge cases. They are the standard situation in every brownfield SAP DM migration we see.<\/strong><\/p>\n<\/div><\/div><\/div><\/div>\n\n\n\n

    \n

    “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.<\/strong>“<\/h3>\n\n\n\n

    \u2014 Lara Ludwigs, VP Commercial Cybus<\/em><\/h4>\n<\/div><\/div><\/div><\/div>\n\n\n\n
    \n

    The architecture that makes the SAP DM migration work: Cybus Connectware as the industrial data layer<\/strong><\/h2>\n\n\n\n

    SAP DM is not built to handle OT load directly \u2013 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 \u2013 at the cadence it can handle.<\/p>\n\n\n\n

    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.
    <\/p>\n\n\n\n

    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:<\/strong><\/strong><\/p>\n\n\n\n

      \n
    • Connects what SAP DM’s Production Connector cannot. <\/strong>100+ industrial connectors including proprietary and legacy protocols. Brownfield equipment that would otherwise require custom C# work is onboarded by configuration, not code.<\/li>\n\n\n\n
    • Decouples OT load from SAP DM. <\/strong>High-frequency machine data is filtered, aggregated and contextualized at the edge \u2013 SAP DM consumes only the business-relevant events at the cadence it can handle.<\/li>\n\n\n\n
    • Preserves the customization SAP DM removes. <\/strong>Soft logic and complex processing run in containerized environments at the edge \u2013 JSONata for transformations, bring-your-own-container for custom code \u2013 keeping the business logic from ME\/MII alive without breaking SAP standards.<\/li>\n\n\n\n
    • Scales by template, not by project. <\/strong>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.<\/li>\n\n\n\n
    • Deploys without production halts. <\/strong>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 \u20ac1M.<\/li>\n\n\n\n
    • Keeps your data sovereign \u2013 and on-premises by default. <\/strong>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 \u2013 and over a 15-year horizon, it will \u2013 the data layer does not need to be migrated with it.<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n

      9 things that change with Cybus Connectware in your SAP DM migration<\/strong><\/h2>\n\n\n\n

      SAP\u2019s 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.<\/p>\n\n\n\n

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

      “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 \u2013 and most companies are making it too late.<\/strong>“<\/h3>\n\n\n\n

      \u2014 Lara Ludwigs, VP Commercial Cybus<\/em><\/h4>\n<\/div><\/div><\/div><\/div>\n\n\n\n
      \n

      Up to \u20ac2.3M saved per SAP DM migration program with Cybus Connectware<\/strong><\/h2>\n\n\n\n

      The architecture decision has a direct financial mirror. Where SAP DM’s Production Connector adds friction \u2013 manual configuration, external SAP consultancy, production halts, debugging cycles \u2013 Cybus Connectware removes cost.<\/p>\n\n\n\n

      At line-item level across a typical multi-site migration program:<\/p>\n\n\n\n

      Cost Factor<\/strong><\/th>\u274c Without Connectware<\/strong><\/th>\u2705<\/strong> With Connectware<\/strong><\/th>SAvings<\/th><\/tr><\/thead>
      External SAP Consultants<\/td>\u20ac200K \u2013 \u20ac800K<\/td>\u20ac50K \u2013 \u20ac200K<\/td>Up to \u20ac600K saved<\/strong><\/td><\/tr>
      IT\/OT Engineer Time (FTE)<\/td>5-10 FTEs, ~\u20ac500K\/year<\/td>1-3 FTEs, ~\u20ac150K\/year<\/td>Up to \u20ac350K saved<\/strong><\/td><\/tr>
      Downtime Costs<\/td>\u20ac1M per hour of disruption<\/td>Near-zero with parallel integration<\/td>\u20ac1M+ saved per avoided hour<\/strong><\/td><\/tr>
      Rework & Debugging<\/td>\u20ac100K \u2013 \u20ac500K+ over time<\/td>Minimal rework needed<\/td>Up to \u20ac400K saved<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      Total Savings Potential: \u20ac2.3M and more <\/strong>per migration project.
      <\/h4>\n\n\n\n

      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.<\/p>\n\n\n\n

      \n\n\n\n

      Four SAP DM migration decisions you and your organization need to make now<\/strong><\/strong><\/h2>\n\n\n\n
        \n
      1. Stop sequencing the data architecture decision after the MES decision. <\/strong>They are the same decision. The MES choice without a data layer choice is incomplete.
        <\/li>\n\n\n\n
      2. Treat SAP DM’s Production Connector as one option, not as the default. <\/strong>It is sufficient for a small, homogeneous, cloud-native plant. It is not sufficient for enterprise brownfield at scale.
        <\/li>\n\n\n\n
      3. Decide the data layer once, not per plant. <\/strong>A vendor-neutral, OT-adjacent UNS is the only architecture that survives the next two SAP product transitions after this one.
        <\/li>\n\n\n\n
      4. Pilot the architecture, not the product. <\/strong>One brownfield plant, one template, six weeks. If the model holds, the rest is rollout.
        <\/li>\n<\/ol>\n\n\n\n
        \n\n\n\n

        The SAP DM migration is not optional. The data architecture decision is.<\/strong><\/h2>\n\n\n\n

        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\u20132030 migrating in templates. Wait, and you spend 2029\u20132030 firefighting a plant-by-plant integration project under deadline pressure \u2013 with no fallback in ME\/MII.<\/p>\n\n\n\n

        Cybus Connectware is the data layer that makes the SAP DM transition work at enterprise scale \u2013 vendor-neutral, on-premises, and built to outlast the next SAP product transition after this one.<\/strong><\/p>\n<\/div><\/div><\/div><\/div>\n\n\n\n

        \n
        \n

        Let’s talk about your SAP DM roadmap<\/h2>\n\n\n\n

        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.<\/p>\n<\/div><\/div><\/div><\/div>\n\n\n

        <\/p>\n

        <\/div>\n