SAP Cloud & Managed Platform Services

Our standard method has three phases. In the discovery phase, the target hardware is determined from SAP's official sizing report and EarlyWatch data — memory is the basis for HANA, the SAPS rating for ECC. In the pilot phase, the quality assurance (QAS) system is migrated with SUM/DMO tools and regression testing is carried out with your business units. The final cutover is a controlled 8-24 hour operation in a weekend maintenance window; a rollback plan is ready at every step. For a mid-sized ECC environment, the end-to-end timeline is typically 4-8 weeks.

For migrations combined with an S/4HANA conversion (lift-and-convert), the timeline extends depending on the project; still, combining the infrastructure move and the conversion in a single window is more economical than going through two separate outages.

HANA is an in-memory database: all hot data is held in RAM, and SAP requires production systems to run on hardware that meets specific certification requirements (memory-to-core ratio, NUMA topology, storage KPIs). Ordinary virtualization environments cannot guarantee these KPIs; when log write latency exceeds 1 ms, HANA performance visibly degrades. DataKobi's SAP pool is built on high-memory servers and NVMe storage set aside to these requirements; a synchronous copy in a second data center via HANA System Replication is optional.