Moving from on-premise infrastructure to the cloud is the single most impactful technology transformation most Australian businesses will undertake this decade. Done well, it delivers dramatic cost savings, improved security, and business agility. Done poorly, it results in budget blowouts, extended downtime, and frustrated stakeholders. This checklist ensures you get it right.
According to the Australian Bureau of Statistics, over 60% of Australian businesses now use cloud computing services, up from 42% just four years ago. Yet McKinsey research indicates that cloud migrations typically take 2-3 times longer and cost 1.5 times more than initially planned. The difference between success and failure is preparation.
Key Takeaway
The most successful cloud migrations follow a structured methodology with clearly defined phases. Rushing the assessment and planning stages is the single biggest predictor of migration failure.
Pre-Migration Assessment Checklist
1. Complete Infrastructure Audit
Before migrating anything, you need a comprehensive understanding of what you have. Use Azure Migrate Discovery and Assessment or similar tools to catalogue:
- All servers — physical and virtual, including specifications, utilisation, and dependencies
- Applications — every application in use, its architecture, and interdependencies
- Databases — type, size, version, and licensing (SQL Server, Oracle, MySQL, PostgreSQL)
- Network architecture — subnets, firewalls, load balancers, DNS configuration, and bandwidth requirements
- Storage — volumes, usage patterns, IOPS requirements, and data classification
- Users and access — Active Directory structure, group policies, and remote access configurations
This audit typically reveals 20-30% more infrastructure than organisations expect, including shadow IT systems and forgotten development environments.
2. Application Classification
Categorise each application using the 6 Rs framework:
| Strategy | Description | Best For |
|---|---|---|
| Rehost (Lift-and-Shift) | Move to Azure VMs with minimal changes | Legacy apps, quick migration needs |
| Replatform | Minor optimisations during migration | Database migrations to Azure SQL |
| Rearchitect | Rebuild using cloud-native services | Apps needing scalability and modernisation |
| Repurchase | Replace with SaaS alternative | CRM, ERP, email systems |
| Retire | Decommission entirely | Unused or redundant applications |
| Retain | Keep on-premise for now | Highly specialised or regulated systems |
Key Takeaway
Most organisations find that 40-60% of workloads are suitable for lift-and-shift, 20-30% benefit from replatforming, and 10-20% should be rearchitected. Typically, 5-15% of applications can be retired outright, delivering immediate cost savings.
3. Total Cost of Ownership Analysis
Build a detailed TCO comparison that accounts for:
- Current on-premise costs: Hardware, power, cooling, rack space, maintenance contracts, staffing
- Azure costs: Compute, storage, networking, licensing, and support tiers
- Migration costs: Project management, technical resources, testing, potential downtime
- Ongoing operational costs: Monitoring, management, security, backup, and compliance
- Risk costs: Disaster recovery improvements, security enhancements, compliance benefits
Use the Azure Pricing Calculator and Azure TCO Calculator for detailed estimates. Factor in Azure Hybrid Benefit if you have existing Windows Server or SQL Server licences — this can reduce compute costs by up to 40%.
4. Compliance and Security Requirements
Before migration, document your compliance obligations:
- Data sovereignty: Identify data that must remain in Australian data centres (Azure Australia East/Southeast)
- Essential 8 alignment: Ensure your cloud architecture supports all eight mitigation strategies at your target maturity level
- Industry regulations: APRA CPS 234 for financial services, Privacy Act for personal information, HIPAA-equivalent standards for health data
- Backup and retention: Define retention periods and backup requirements for each data classification
Migration Planning Checklist
5. Design the Azure Landing Zone
Your Azure Landing Zone is the foundation for everything that follows. A well-designed landing zone includes:
- Subscription architecture: Separate subscriptions for production, development, and management
- Resource group strategy: Logical grouping aligned with applications or business units
- Network topology: Hub-and-spoke or Virtual WAN design with appropriate segmentation
- Identity integration: Entra ID Connect for hybrid identity, Conditional Access policies
- Security baseline: Azure Policy assignments, Microsoft Defender for Cloud, and network security groups
- Cost management: Budgets, alerts, and tagging standards for chargeback
6. Establish Connectivity
Reliable connectivity between on-premise and Azure is critical during and after migration:
- Azure ExpressRoute for dedicated, private connectivity (recommended for production workloads)
- Site-to-Site VPN as a backup or for smaller environments
- DNS configuration for hybrid name resolution
- Bandwidth assessment — ensure sufficient bandwidth for data transfer during migration windows
7. Build the Migration Wave Plan
Divide your migration into waves, starting with low-risk workloads:
- Wave 1 (Pilot): Non-critical development or test environments — validate processes and tooling
- Wave 2 (Early adopters): Low-risk production workloads with minimal dependencies
- Wave 3 (Core): Primary business applications and databases
- Wave 4 (Complex): Highly interconnected systems, legacy applications, and databases requiring schema changes
- Wave 5 (Cleanup): Remaining workloads and decommissioning of on-premise infrastructure
Migration Execution Checklist
8. Pre-Migration Testing
- Perform test migrations for each workload type using Azure Migrate
- Validate application functionality in the target environment
- Test disaster recovery procedures before going live
- Confirm network connectivity, latency, and throughput meet requirements
- Verify backup and monitoring configurations
9. Migration Execution Steps
For each migration wave:
- Notify stakeholders and schedule maintenance windows
- Create a detailed runbook with step-by-step procedures and rollback plans
- Execute the migration using Azure Migrate Server Migration or Azure Site Recovery
- Perform post-migration validation: application functionality, performance, and data integrity
- Update DNS records and decommission source systems only after validation
- Document any deviations from the plan for future waves
10. Database Migration Considerations
Database migrations require special attention:
- Use Azure Database Migration Service for SQL Server migrations to Azure SQL
- Plan for minimal downtime using online migration mode where possible
- Test application compatibility with the target database version
- Validate performance under production-equivalent load
- Ensure encryption at rest and in transit for all database connections
Key Takeaway
According to Microsoft, organisations using Azure Migrate with a structured wave approach complete migrations 45% faster than those using ad-hoc methods. The tool provides automated discovery, assessment, and migration capabilities that significantly reduce manual effort.
Post-Migration Optimisation Checklist
11. Cost Optimisation
- Right-size VMs based on actual utilisation data (most VMs are over-provisioned by 30-50%)
- Implement Azure Reserved Instances for predictable workloads (up to 72% savings)
- Enable auto-shutdown for development and test environments
- Configure storage tiering to move infrequently accessed data to cool or archive storage
- Set up Azure Cost Management alerts and budgets
12. Security Hardening
- Enable Microsoft Defender for Cloud across all subscriptions
- Deploy Microsoft Sentinel for SIEM and automated threat response
- Enforce Essential 8 controls including MFA, application control, and patch management
- Configure Azure Policy to prevent configuration drift
- Implement network segmentation using NSGs and Azure Firewall
13. Operational Readiness
- Configure comprehensive monitoring and alerting through Azure Monitor
- Establish backup and disaster recovery procedures with regular testing
- Document operational runbooks for common management tasks
- Train IT staff on Azure management and troubleshooting
- Review and optimise Conditional Access and identity policies
Common Migration Mistakes and How to Avoid Them
- Skipping the assessment phase — Every dollar spent on assessment saves five dollars during execution
- Migrating everything at once — Wave-based approaches reduce risk and allow learning between phases
- Ignoring network bandwidth — Large data transfers can take days; plan for Azure Data Box for datasets over 10TB
- Forgetting about licensing — Understand Azure Hybrid Benefit and bring-your-own-licence options before purchasing new licences
- Not planning rollback procedures — Every migration wave needs a documented rollback plan
Get Expert Help with Your Cloud Migration
Precision IT has guided hundreds of Australian businesses through successful cloud migrations. As a Microsoft Solutions Partner, we have the expertise and tools to ensure your migration is completed on time, on budget, and without disruption to your operations.
Our cloud migration service includes comprehensive assessment, planning, execution, and post-migration optimisation — all backed by our 24/7 Australian support team and fixed-price project delivery.
Download our detailed migration planning template or book a free migration assessment to get started. We will analyse your current infrastructure and provide a tailored migration roadmap with clear timelines and cost projections.