MSP Cloud Migration Guide: Moving to the Cloud Without the Chaos
Cloud migration is one of the most common projects Australian MSPs undertake. Done well, it transforms a business's IT capabilities. Done poorly, it creates chaos, data loss, and ongoing problems.
Here is a practical guide to cloud migration — from assessment to optimisation.
Why Migrate to the Cloud?
The business case for cloud migration typically includes:
- Reduced infrastructure costs — no more on-premises server maintenance
- Improved resilience — cloud platforms offer built-in redundancy and disaster recovery
- Remote access — work from anywhere, a critical requirement since 2020
- Scalability — add or remove capacity as needed
- Security — major cloud providers invest more in security than most businesses can
- Updates — automatic updates and patches reduce management burden
Common Cloud Migration Targets
| Migration | What Moves | Typical Complexity |
|---|---|---|
| Email to Microsoft 365 | Exchange to Exchange Online | Low-Medium |
| Files to SharePoint/OneDrive | On-premises file shares | Medium |
| Applications to Azure | Line-of-business apps | High |
| Desktops to Windows 365/Azure Virtual Desktop | Physical desktops | Medium-High |
| Hybrid | Combination of above | High |
The Migration Framework
Phase 1: Assessment (Weeks 1-4)
Before moving anything, understand what you have:
Infrastructure Audit: - Server inventory (hardware, OS, applications) - Network topology and bandwidth - Storage capacity and utilisation - Software licences and compatibility
Application Assessment: - Which applications are cloud-ready? - Which need modification? - Which cannot move (legacy, regulatory, performance)?
Data Assessment: - Total data volume - Data sensitivity and classification - Data growth rate - Backup and retention requirements
Dependency Mapping: - Application dependencies - Network dependencies - Authentication dependencies (Active Directory) - Integration dependencies (third-party connections)
Our Essential 8 Implementation Checklist covers security assessment as part of migration planning.
Phase 2: Planning (Weeks 2-6)
Based on the assessment, develop a migration plan:
Migration Strategy per Workload:
| Strategy | Description | When to Use |
|---|---|---|
| Rehost (lift and shift) | Move as-is to cloud | Quick wins, legacy apps |
| Replatform | Minor optimisation during move | Moderate complexity |
| Refactor | Re-architect for cloud | Strategic workloads |
| Retain | Keep on-premises | Legacy, regulatory, performance |
| Retire | Decommission | Obsolete systems |
Migration Timeline:
- Wave 1: Email and collaboration (Microsoft 365)
- Wave 2: File storage (SharePoint/OneDrive)
- Wave 3: Line-of-business applications
- Wave 4: Desktops and virtualisation
- Wave 5: Legacy systems (or retain)
Risk Register:
Document all identified risks, their likelihood, impact, and mitigation strategies.
Phase 3: Preparation (Weeks 4-8)
Before migration begins:
Environment Setup: - Provision cloud tenants and subscriptions - Configure networking (VPN, ExpressRoute, or direct connect) - Set up identity (Azure AD, hybrid identity) - Configure security (Conditional Access, MFA, Defender)
Testing: - Test migration of representative workloads - Validate performance and connectivity - Test backup and restore procedures - User acceptance testing with pilot group
Communication: - Notify users of migration timeline - Provide training materials - Establish support channels for migration issues - Document known issues and workarounds
Phase 4: Migration Execution (Weeks 6-16)
Execute the migration in waves:
Pre-Migration: - Final backup of source systems - Verify cloud environment readiness - Confirm rollback procedures
Migration: - Execute migration per the plan - Monitor for errors and issues - Validate data integrity post-migration - Communicate progress to stakeholders
Post-Migration: - Verify all data migrated successfully - Test application functionality - Monitor performance and stability - Address user-reported issues
Phase 5: Optimisation (Ongoing)
Migration is not the end — it is the beginning:
Cost Optimisation: - Right-size cloud resources - Implement auto-scaling - Review reserved instance opportunities - Monitor and optimise storage tiers
Security Hardening: - Implement Zero Trust principles - Configure Conditional Access policies - Enable advanced threat protection - Regular security reviews
Performance Monitoring: - Monitor application performance - Optimise network connectivity - Address bottlenecks - User satisfaction tracking
Common Migration Challenges
1. Underestimating Complexity
The problem: Assuming cloud migration is simple because the cloud provider makes it look easy.
The solution: Engage an MSP with specific migration experience. The complexity is not in the technology — it is in the planning, testing, and change management.
2. Inadequate Testing
The problem: Skipping testing to save time, then discovering problems after cutover.
The solution: Test every workload before migration. Test the rollback. Test the user experience. Testing takes time but saves exponentially more time in post-migration fixes.
3. Poor User Training
The problem: Migrating to new tools without training users on how to use them.
The solution: Provide training before, during, and after migration. Create quick-reference guides. Establish a support channel for migration-related questions.
4. Data Loss
The problem: Data lost or corrupted during migration.
The solution: Maintain backups throughout the migration process. Verify data integrity after each migration wave. Test restore procedures before decommissioning source systems.
5. Unexpected Costs
The problem: Cloud costs exceeding budget due to underestimation or misconfiguration.
The solution: Start with accurate sizing. Implement cost monitoring from day one. Set up alerts for unexpected spending. Review costs monthly.
6. Business Disruption
The problem: Migration causing downtime that impacts business operations.
The solution: Migrate during low-impact periods. Use phased migration to limit blast radius. Communicate clearly with users about expected disruptions.
Microsoft 365 Migration: The Most Common Project
For most Australian MSPs, Microsoft 365 migration is the most frequent cloud project:
Pre-Migration Checklist
- [ ] Azure AD Connect configured (hybrid identity)
- [ ] DNS records prepared (MX, CNAME, TXT)
- [ ] User licences assigned
- [ ] Mailbox size assessment completed
- [ ] Distribution groups and shared mailboxes documented
- [ ] Public folders assessed and migrated
- [ ] OneDrive/SharePoint permissions mapped
- [ ] Teams structure designed and documented
Migration Steps
- Configure Azure AD Connect — sync on-premises identities to Azure AD
- Set up Microsoft 365 tenant — configure tenant settings, security, and compliance
- Migrate mailboxes — use migration batches or third-party tools
- Migrate files — migrate file shares to SharePoint/OneDrive
- Configure Teams — create teams and channels per the design
- Decommission Exchange — remove on-premises Exchange after verification
The MSP's Role in Cloud Migration
A good MSP brings:
- Experience — lessons learned from previous migrations
- Tools — migration tools and utilities
- Project management — structured approach to planning and execution
- Risk management — identifying and mitigating risks proactively
- Change management — helping users adapt to new tools
Our How to Choose an MSP guide covers how to evaluate MSP capabilities for migration projects.
Post-Migration: The Forgotten Phase
Many migrations fail not during the move, but in the aftermath:
Month 1-3: Stabilisation - Address issues as they arise - Monitor performance and stability - Gather user feedback - Optimise configurations
Month 3-6: Optimisation - Review costs and right-size - Implement advanced security features - Train users on advanced capabilities - Document the new environment
Month 6-12: Maturity - Review and update documentation - Plan for next phase of cloud adoption - Assess additional cloud services - Build internal cloud capability
The Bottom Line
Cloud migration is a journey, not an event. The MSPs that deliver successful migrations are the ones that plan thoroughly, test rigorously, communicate clearly, and support users through the transition.
The cloud is not inherently better — it is different. The value comes from how you use it, not just that you are using it.
Use our MSP Cost Calculator to estimate migration costs, or our MSP Health Score to evaluate your MSP's cloud capabilities.
Was this helpful?