Planning SAP
cloud hosting.
A workload-specific decision involving more than CPU, memory and storage.
Begin with a documented SAP landscape and responsibility matrix. Infrastructure, operating system, database, Basis, functional support, network, backup and recovery ownership must be clear before migration.
Document the complete landscape
Inventory production, quality, development and any supporting systems. Capture SAP versions, databases, operating systems, interfaces, batch windows, data growth, user locations and current performance. An isolated server specification rarely explains the whole workload.
Define ownership before architecture
Hosting providers, SAP partners and internal teams may each manage different layers. Create a responsibility matrix for monitoring, patching, Basis work, database administration, certificates, connectivity, backups and incident escalation. Ambiguous ownership creates delays during the moments when clarity matters most.
Design around business recovery needs
Agree acceptable downtime and acceptable data loss. These targets shape redundancy, backup frequency, replication and recovery cost. Review network paths from user locations and any integrations that depend on fixed addressing, VPNs or third parties.
Migration checklist
- Landscape diagram and component versions
- Measured utilization and growth history
- Interfaces, batch jobs and external dependencies
- Security, network and user-location requirements
- Downtime window, validation and rollback sequence
- Monitoring, backup, recovery and support ownership