SAPinsider Las Vegas: SAP Cloud ERP Impact for Data Centers

Running SAP Cloud ERP in customer data centers or colocation facilities is no longer a legacy compromise; it is a deliberate operating model that mirrors the functionality and update cadence of hyperscaler deployments while keeping infrastructure under local control. According to James Loiacono, HPE Worldwide SAP Private Cloud Sales Lead in his presentation “Keeping SAP Cloud ERP On-Site: Reducing Risk Without Sacrificing Innovation” at SAPinsider Las Vegas, a big decision is ahead.

Understanding Differences, Similarities for SAP Cloud ERP

In the customer data center model, SAP delivers the same cloud ERP software stack, lifecycle management, and innovation roadmap, while partners provide infrastructure as a service that lives on premises or in a colocation facility. From an operational standpoint, internal teams still manage business configurations, integrations, and extensions, but the underlying hardware capacity, patching and resilience can be consumed as operating expense, similar to public cloud.

“Everything is the same except where you host the infrastructure,” Loiacono said.

For technology executives, this shifts daily work from hardware procurement cycles to contract and service-level governance. Leaders will spend more time modeling total cost of ownership (TCO) across on-site, colocation, and hyperscaler options, and less time dealing with infrastructure upgrades. Loiacono emphasized how the four main SAP Cloud ERP deployment options deliver identical application capabilities. The difference, he said, is who hosts and operates the infrastructure and where adjacent data sets reside.

As a result, data strategy becomes a priority. When critical non-SAP systems remain in a data center, moving only SAP to a hyperscaler can add latency, integration complexity, and duplication for analytics and AI scenarios. Keeping SAP Cloud ERP co-located with those systems lets architects design simpler data aggregation patterns for AI inference, including Joule agentic AI, while preserving data residency and sovereignty policies  many industries require.

“If the data is on-site, cloud ERP doesn’t do anything other than cost time and expense,” Loiacono said.

How On-Site Cloud ERP Changes Day-to-Day Responsibilities

In day-to-day operations, security and compliance leaders gain more direct control over physical location, network segmentation, and regulatory evidence because sensitive data remains within a controlled facility, even as the ERP stack adopts a cloud operating model. However, this also means internal teams must align security baselines, SOC processes and disaster recovery drills to avoid gaps.

“You can’t predict what’s happening, but if it’s happening in your data center, you have the ultimate control,” Loiacono said.

Loiacono also cautioned against viewing SAP in isolation from surrounding applications and data flows. If adjacent data dependencies remain on-site, lifting only SAP into a single hyperscaler can increase risk, cost, and time to value by forcing large-scale data migrations worth hundreds of millions of dollars before any business benefit is realized.

In that context, cloud agility is less about a destination and more about preserving options across hybrid and multicloud architectures so SAP and non-SAP landscapes can evolve at different speeds.

Four Key Priorities for Colocation Evaluation

SAPinsider research and customer interviews have found that while many organizations report 25 to 30% savings in monthly operational support costs and significantly faster performance on hyperscalers, those benefits depend on holistic workload placement and disciplined cost management.

When evaluating on-site or colocation options for SAP Cloud ERP, technology leaders should prioritize four categories:

1. Data Dependencies: Where the largest and most sensitive data sets reside today, and what it would cost and risk to move them.
2. Risk and Compliance: How different hosting models affect data residency, auditability, and sector-specific regulations.
3. Time to Value: Whether infrastructure modernization, for example moving to a managed private cloud in a data center, can be decoupled from major ERP reimplementation to avoid long freezes on business change.
4. Innovation Access: How quickly SAP continuous innovation, including Joule AI agents and industry content, can be consumed without being constrained by customizations or fragmented landscapes.

Keeping SAP Cloud ERP close to core data sources in a managed on-site or colocation environment can simplify integration patterns, but it raises expectations on architects to standardize APIs, metadata and security policies across the estate.

Loiacono also stressed cloud ERP decisions must align with long-term enterprise architecture, not just the current budgeting cycle. The ability to pivot between on-site, colocation, and hyperscaler deployments over time without disrupting the ERP core will be central to how often teams execute major infrastructure projects versus focusing on process innovation and AI-driven optimization.

What This Means for SAPinsiders

Cloud location becomes a strategic control point. Technology leaders should treat hosting choices as levers for risk, data residency, and agility, not as binary cloud-or-not decisions, to better align SAP strategy with enterprise architecture.

Data-centric architectures drive ERP value. Enterprise architects who co-locate SAP and non-SAP data can streamline AI, analytics, and compliance, signaling opportunities for vendors and GSIs to deliver integrated data platforms and governance accelerators.

Hybrid agility reshapes transformation roadmaps. Transformation leaders must design roadmaps that decouple infrastructure modernization from functional change, encouraging SAP vendors and partners to support portable, cloud-agnostic architectures and flexible commercial models.