EN
PT
Cloud migration can unlock significant benefits — reduced infrastructure costs, better scalability, improved resilience, and faster innovation. But a poor migration plan can result in security gaps, unexpected costs, and performance issues that undo those gains. Use this checklist to migrate with confidence.
Before You Migrate
1. Define Your Cloud Strategy
Decide between lift-and-shift (fastest but least efficient), re-platforming (small optimisations for cloud), and re-architecting (rebuild for cloud-native benefits). Most enterprises use a mix across their portfolio.
2. Complete a Full Application Inventory
Catalogue every application, its dependencies, its current performance baseline, and its criticality to the business. You cannot migrate what you haven't mapped.
3. Classify Your Data
Identify which data is sensitive, which is regulated (GDPR, NIS2), and which has residency requirements. This directly determines which cloud regions and services you can use.
4. Assess Licensing
Software licensing in the cloud is different. SQL Server, Windows Server, and Oracle all have cloud-specific licensing rules. Miscalculations here are a common source of budget overruns.
5. Define Your Target Architecture
Draw the target architecture before you start. Where will each workload land? What networking topology will you use? How will identity and access management work across cloud and on-premise?
Security and Compliance
6. Implement Zero-Trust Networking
Do not simply replicate your on-premise perimeter in the cloud. Use Azure Private Endpoints, network security groups, and service-to-service authentication with managed identities.
7. Enable Logging and SIEM from Day One
Connect your cloud environment to a SIEM before any workloads go live. Security incidents are far harder to investigate retrospectively.
8. Test Disaster Recovery
Define your Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for each workload, then actually test them. Many organisations discover their backup strategy is inadequate only during an incident.
Cost Management
9. Set Up Budgets and Alerts
Cloud spending can grow unexpectedly. Configure cost budgets and alert thresholds in Azure Cost Management or AWS Cost Explorer before your first workload goes live.
10. Choose the Right Pricing Model
Use Reserved Instances or Azure Savings Plans for stable workloads. Keep pay-as-you-go for variable workloads. Rightsize virtual machines — many organisations run VMs that are two or three tiers too large.
During and After Migration
11. Migrate in Waves
Start with the least critical, most straightforward workloads. Build confidence, refine your process, then tackle the complex ones.
12. Run Parallel Environments
Keep your on-premise environment running for a minimum of two weeks after each migration wave. A fast rollback path is essential.
13. Update Your Monitoring Stack
Application Performance Monitoring (APM) should be in place before users touch the new environment. Azure Application Insights and Grafana are our recommended stack.
14. Train Your Operations Team
Cloud operations require different skills from traditional sysadmin work. Invest in Azure Administrator and DevOps Engineer certifications for your team.
15. Optimise Continuously
Migration is not the end — it is the beginning. Run quarterly FinOps reviews, apply Advisor recommendations, and retire technical debt that the migration surfaced.
Share this article
Carlos has over 20 years of experience in software architecture and enterprise technology. He leads the technical vision at NT4Solutions and is passionate about cloud-native development and digital transformation.