Assess
- Inventory servers, applications, databases, file shares and their owners.
- Map dependencies — which systems talk to which, and what breaks if one moves.
- Measure performance so target sizing is based on real use, not guesses.
- Check licensing — some software licences do not transfer to cloud as-is.
- Decide per workload: rehost, replatform, modernise, replace with SaaS or retire.
South African considerations
- Data residency. Microsoft, Google and AWS operate South African cloud regions. Confirm each service you need is available in-region, and whether regulation, contracts or POPIA considerations make local hosting important.
- Connectivity. Size and make resilient the links between offices and the cloud — a cloud-first business depends on its internet connection.
- Power resilience. Cloud reduces dependence on local server rooms, but offices and network equipment still need a plan for power interruptions.
- Currency. Cloud services are often priced in US dollars; budget for exchange-rate movement.
Design the landing zone
- Identity and access with least privilege and MFA.
- Network design, including secure connectivity to offices.
- Security baseline, logging and alerting — see cloud security.
- Backup and disaster recovery designed around recovery objectives.
- Cost controls: budgets, alerts and tagging from day one.
Migrate in waves
- Start with lower-risk workloads to prove the approach.
- Define tests, go-live criteria and a tested rollback plan per wave.
- Communicate cutover windows to the business.
- Keep the source available until the migrated workload is proven.
After migration
- Right-size based on real utilisation — see cloud cost optimisation.
- Hand over to operations with documentation and monitoring.
- Decommission old infrastructure safely.
- Review cost, security and performance regularly.