skie.io
SAPHANA migrationManaged private cloudConsumer goods

A full SAP estate to HANA, with migration time cut in half.

How a global footwear brand moved ECC, BW, GRC and BusinessObjects from Oracle Database on premises to SAP HANA in SAP's managed private cloud, bringing the critical ERP migration down from 160 hours to 77.

160 to 77 hrsTotal migration time
52%Less migration time
60-70%Faster key reportsvs. the old BW
4Systems movedECC, BW, GRC, BO
Global footwear brandFootwear design, manufacture and retail · US headquartered · Delivered by the skie.io SAP migration team

A US-headquartered global footwear company that designs, manufactures and distributes shoes sold worldwide, running SAP ECC (AFS), BW, BusinessObjects, GRC and Portal.

The SAP landscape sat on Oracle Database in a third-party data center, and end-to-end application performance was holding the business back as data volumes grew.

The business trigger

Performance to gain, and a tight downtime window to do it in.

The company wanted HANA performance across its SAP estate and a cloud foundation under it. The constraint was the ERP: a large database that had to move within a downtime window the business could accept, with encrypted transfer between the on-premises and cloud data centers.

Reports slowed by data volume

Large data volumes were slowing report generation across the platform.

A complex BusinessObjects estate

Many user instances and objects in user folders, all of which had to arrive intact.

A large ERP database

ECC had to move within a tight downtime window.

Secure transfer

Data had to move encrypted between the on-premises and cloud data centers.

The skie.io approach

A migration tuned through repeated, measured test runs.

The team applied its migration methodology and SAP Migration Factory tooling, running the migration repeatedly and measuring each pass until the production window fit.

1

Parallel migration

Best-practice parallelization with table splitting and database tuning at source and target.

2

Infrastructure tuning

Network monitoring and server resource tuning at both ends.

3

Security

Encrypted data transfer between the on-premises and cloud data centers.

4

Cloud readiness

Architecture review with sizing and scale-up recommendations for the target.

5

Code and BI

Custom code remediated and optimized for HANA; BusinessObjects 4.2 built in the cloud with all content migrated and a structured test roadmap.

Results

Faster reporting, one BI platform, a shorter cutover.

Days and weeks of optimizing the migration path brought the ERP migration from 160 hours to 77, coordinated across three teams in two data centers.

Business impact

  • Big gains in report generation across the platform; key reports 60-70% faster than the old BW
  • A single unified BI platform
  • Lower cost of supporting the SAP environment

Operational impact

  • Migration time halved: 160 hours to 77
  • Delivered on time and to a high standard
  • Three teams in two data centers coordinated through one cutover plan

Technology impact

  • ECC, BW, GRC and BusinessObjects on SAP HANA in the cloud
  • BW on Oracle converted to BW on HANA
  • A HANA cloud foundation in place for digital transformation
160 to 77 hrsTotal migration time
52%Less migration time
60-70%Faster key reportsvs. the old BW
4Systems movedECC, BW, GRC, BO

"After days and weeks of optimizing the migration path, you successfully dropped the migration time from 160 hours to 77 hours. The optimization took the collaborative and combined effort of 3 teams in 2 data centers to get it done. We couldn't have done it without each of you."

SAP Cloud Project Director · client organization

Why it matters for your estate

The whole SAP estate, moved as one program.

ECC, BW, GRC and BusinessObjects moved together, from Oracle Database on premises into SAP's managed private cloud, the path that today corresponds to RISE with SAP. The repeated, measured test runs are how a large database fits a small window.

Rehearsed cutover

Every pass measured and tuned; the production run was the one the team had already done.

Oracle Database to HANA

The database change was part of the move, not a separate project.

BI arrives intact

A structured test roadmap for the large BusinessObjects estate, refined through user feedback.

What comes next

A HANA foundation for what comes next.

With the estate on HANA in the cloud and reporting running at the speed the business needed, the company has the platform in place for its digital transformation.

Facing a VMware renewal or the SAP ECC deadline?

Two clocks are running. Make one decision, not two.

See the four S/4HANA paths, the 30-day assessment, and how skie.io moves SAP and everything around it, lands it optimized, and operates it from day one.