Bridgestone EMEA moved its central SAP S/4HANA landscape from its own Microsoft Azure environment to SAP Cloud ERP Private as part of the RISE with SAP model. The scope covered the sandbox, development, test and production environments supporting core operations across EMEA and connected to a wide ecosystem of SAP and non-SAP applications.
The objective was simplifying the operating model, improving predictability and security, and creating the cloud foundation needed for future SAP innovation, including Business Data Cloud, Joule and other AI-enabled capabilities. The program was delivered jointly by Bridgestone, SAP and oXya.

The challenge

The production go-live date of 15 June 2026 was fixed and non-negotiable.

The SAP system itself was only one part of the challenge. Bridgestone’s S/4HANA platform is connected to many satellite applications, integration services, network components, schedulers, file shares and security mechanisms. Some SAP and non-SAP solutions would remain outside the RISE environment, so every critical dependency had to continue working after the move.

The primary success criterion was business continuity. The migration was intended to be almost invisible to end users: the same login, the same business processes and a normal start on Monday morning. Internally, the ambition was simple: make the go-live as smooth as possible.

A controlled migration approach

Bridgestone, SAP and oXya followed a progressive migration path. Each environment was used to learn, correct and de-risk the next step, culminating in a full production dry run and a detailed production cutover.

• Sandbox migration
• Development environment migration
• Test environment migration
• Production dry run
• Production cutover, go-live and structured hypercare

The technical cutover was managed through a detailed runbook, clear decision points and a fully prepared rollback plan, which was ultimately not required. A firm deadline and strong governance helped the teams resolve issues quickly and maintain momentum.

Testing covered the core SAP platform and its connections, but the project also showed the limits of point-to-point connectivity testing. Some issues only appeared in production-scale functional flows, particularly around network and firewall rules, satellite systems, legacy operating-system scripts, file shares, certificates, integration queues and HANA database parameters. These became important lessons to share for future cloud migrations.

Why operational continuity mattered

oXya had managed Bridgestone’s SAP environment since 2019 and therefore brought detailed knowledge of the existing landscape into the migration. That continuity was valuable before, during and after cutover, especially when issues crossed the boundaries between SAP, infrastructure, integrations and satellite applications.

Responsibilities were shared across the three parties. oXya carried end-to-end responsibility for the technical preparation and operational continuity of the SAP landscape. Key activities included:

• Target architecture and migration readiness
• Detailed migration preparation and execution support
• Integration and satellite-system validation
• Cutover planning for the fixed downtime window
• Technical testing, performance validation and production dry run
• Hypercare, incident resolution and transition into steady-state operations

The result

The production migration was completed within the agreed go-live window. The central EMEA SAP landscape moved to SAP Cloud ERP Private while the required connections with systems on Microsoft Azure and other platforms remained in place.

For end users, the platform change was designed to be almost invisible. Business teams could continue working with the same processes and experience, while Bridgestone gained a cloud foundation aligned with SAP’s future innovation roadmap.