We are excited to announce a new capability for SAP S/4HANA Cloud Private Edition customers: adoption milestone tracking, powered by SAP EarlyWatch Alert data and available in the Customer Insights Dashboard (CID) on SAP for Me.
If you are already familiar with the onboarding milestones for SAP S/4HANA Cloud Public Edition and SAP Integrated Business Planning (IBP), this is the Private Cloud counterpart you have been waiting for. And it goes even further: in addition to tracking implementation progress, the new milestones include built-in adoption risk monitoring that continuously watches for early signs of stalled implementations or declining system usage.
Why This Matters
Moving to SAP S/4HANA Cloud Private Edition is one of the most significant transformations a business can undertake. The journey from contract signature to a fully operational, value-generating system can span months, sometimes even years, of provisioning, configuration, testing and go-live activities.
Yet for much of that journey, the signals that indicate whether a customer is progressing as expected, or beginning to stall, have been difficult to surface systematically. Data was fragmented across tools, inputs were manual, and adoption risk was often identified too late for meaningful intervention.
The question we set out to answer: How can we generate data-driven insights on adoption journeys, early enough to make a real difference?
What SAP EarlyWatch Alert Brings to the Table
SAP EarlyWatch Alert has been a trusted companion for SAP customers for decades, indicating system health, performance, and configuration. With this new release, SAP EarlyWatch Alert further expands its scope beyond system diagnostics into adoption intelligence. Here is what makes this approach unique:
- Zero configuration. SAP EarlyWatch Alert already collects weekly telemetry data from every connected system: active users, transport activity, transaction usage, and more. No additional setup is required from the customer.
- Fully automated. Milestones are automatically recalculated twice per week across all connected S/4HANA Private Cloud landscapes.
- Proactive risk detection. The dashboard does not just track forward progress. It also continuously monitors signs of stalled adoption and user decline after go-live.
- Integrated experience. Milestone data appears in the Onboarding tab of the Customer Insights Dashboard in SAP for Me, right alongside Public Cloud and IBP milestones.
The SAP EarlyWatch Alert Apps as tools for proactive alerting and diagnostics can be accessed via SAP for Me: https://me.sap.com/servicessupport/diagnostics
The Six Adoption Milestones
Each SAP S/4HANA Cloud Private Edition system landscape is tracked through six milestones that map to the key phases of a new cloud ERP implementation or transformation approach. Milestones are evaluated per system track, which is the logical grouping of a customer's Development (DEV), Test (TEST), and Production (PROD) systems linked by a common SAP Transport Management System route.
M1: Landscape Initialized
Your S/4HANA Cloud Private Edition system is live and connected to SAP. Your implementation journey has now begun.
This milestone is triggered when the first EarlyWatch Alert data is received from any non-production system in the track. It marks the moment the landscape becomes visible to SAP. No thresholds and no configuration are needed. The mere presence of this data confirms that provisioning is complete and the system is connected.
M2: Realize Phase Active
Your team has started configuring the system for your business needs. Build and testing activities are now underway.
Detected through usage of transaction SPRO (the SAP Customizing Implementation Guide) on a DEV or TEST system. SPRO is the central entry point for system configuration, so its usage is a reliable signal that the implementation team has begun tailoring the system to the customer's business processes.
M3: Pre-Cutover Preparation
Access roles and authorization profiles are being set up. Go-live preparation is underway.
Detected through usage of transaction PFCG (Role Maintenance) on a non-production system. Setting up authorization roles and user profiles is a critical pre-go-live activity.
M4: Cutover Initiated
Your team has initiated the cutover; configuration is being transported to your production system. Go-live is imminent.
Triggered when a significant transport wave is detected on the production system: at least 1,000 Workbench and Customizing transport objects imported in a single week. This threshold distinguishes genuine cutover deployments from routine maintenance imports and provides a high-confidence signal that go-live preparation is in its final stage.
M5: Go-Live Detected
A significant jump in active users on your production system confirms go-live. Your system is now in productive use.
SAP EarlyWatch Alert tracks weekly active user counts on the production system. When a significant and sustained spike in users is detected, the system is considered live. The detection automatically adapts to the size of each customer's landscape, so it works equally well for small and large deployments. It also accounts for special cases like system conversions and filters out technical-only activity to avoid false positives.
M6: Steady Usage State
Your system is in stable productive use with an active user base and regular updates. The status is reviewed continuously and may change.
Unlike M1 through M5, which are set once and remain, M6 is a living indicator. It is re-evaluated every week and can change between “Reached” (healthy) and “At Risk” based on two independent checks.
M6-1: Transport Activity Check. Were any transports imported into any system in the track within the last six months? If not, the system may no longer be actively maintained. This check runs independently of go-live status, so it can flag adoption stalls even before a customer has gone live.
M6-2: User Decline Detection. After go-live, the system continuously monitors whether the number of active users on the production system is declining significantly. A sustained drop in usage serves as an early signal for customer success teams to reach out and offer support.
Remark: Some milestones can be calculated based on the availability of connected Private Cloud systems.
Where to Find It
The milestone data is available in the Customer Insights Dashboard (CID) on SAP for Me, in the Onboarding tab: https://me.sap.com/reporting/customerinsightsdashboard/onboarding
If you are already using the Onboarding view for SAP S/4HANA Cloud Public Edition or SAP IBP, you will find the Private Cloud milestones right alongside them. Same dashboard, same experience, no additional setup:
When M6 turns red, it provides a specific, actionable signal: either maintenance activity has stopped or the productive user base is declining. Both are leading indicators of adoption challenges, and both are surfaced early enough for proactive engagement.
Conclusion
Adoption milestone tracking for SAP S/4HANA Cloud Private Edition transforms EarlyWatch Alert data, collected every week from every connected system, into structured, actionable adoption intelligence. By automatically identifying where each customer stands in their cloud journey and flagging early signs of risk, it enables the kind of proactive, data-driven engagement that complex cloud transformations demand.
Read more about how this helps you get the most out of your SAP investment: Proactive by Design: Introducing Adoption Milestone Tracking for S/4HANA Private Cloud – SAP Community
The data is already there. Now, it tells a story.