Quick answer: Do not migrate every workload the same way. Assess each application and choose rehost, replatform, refactor, repurchase, retain or retire.
Saudi cloud migration also involves data location, compliance, security, connectivity, economics and day-two operations. Start with portfolio assessment before buying capacity.
Readiness
Inventory applications, data, dependencies and service requirements.
- Application inventory
- Data classification
- Dependencies
- RTO/RPO
- Peak load
6Rs
Choose a strategy for each workload.
- Rehost
- Replatform
- Refactor
- Repurchase
- Retain
- Retire
Data residency
Define location and regulatory constraints before selecting services.
- Residency
- PDPL
- NCA controls
- Vendor assessment
- Data classification
Security and networking
IAM, encryption, logging and connectivity must be designed early.
- IAM
- Encryption
- Private connectivity
- Logging
- Backup
FinOps
Cloud does not automatically reduce cost; active governance is required.
- Rightsizing
- Budgets
- Savings plans
- Tagging
- Cost alerts
Frequently asked questions
Is rehost fastest?
Often yes, but it captures fewer cloud-native benefits.
Should everything move?
No; some workloads should be retained, replaced or retired.
When should FinOps begin?
During architecture, not after the first bill.
Next step
Migrate in waves with a low-risk pilot and a tested rollback plan.
