When you need it
You want to leave your data centre or change cloud, but nobody has a complete list of servers, databases and the connections between them. Without that, every estimate is a guess, and the first cut-over becomes the place where hidden dependencies show up.
What sets the quote
- One source estate (VMware vSphere, Hyper-V, physical servers or another cloud) and one target cloud: AWS, Microsoft Azure or Google Cloud.
- Sized by servers, applications and databases, taken from a discovery tool or an export from vCenter, Hyper-V or your CMDB.
- One week: up to 50 servers, 15 applications and 5 databases.
- Two weeks: up to 200 servers, 40 applications and 20 databases, plus a cost comparison of two target clouds.
- Larger estates are quoted after the first inventory export.
What changes
- You know what you run, what depends on what, and what should not move at all.
- Each application has a migration approach and a place in a wave plan.
- You can take a realistic cost and time estimate to management before committing.
What you get
- Inventory of servers, applications and databases with their dependencies
- Migration approach per application (rehost, replatform, refactor, retain or retire), with the reason
- Requirements for the target landing zone, including network, identity and the hybrid link
- Wave plan with move order, cut-over windows and rollback points
- Monthly run-cost estimate in the target cloud, with the assumptions behind it
- Risk list, including licensing questions to settle before the move
- A 90-minute readout with your team
Tools we use on each cloud
| Step | AWS | Azure | Google Cloud |
|---|---|---|---|
| Discovery and sizing | Migration Evaluator, or an export from vCenter or your CMDB | Azure Migrate discovery and assessment | Migration Center |
| Servers | AWS Application Migration Service | Azure Migrate | Migrate to Virtual Machines |
| Databases | AWS Database Migration Service | Azure Database Migration Service | Database Migration Service |
| Hybrid link | Site-to-Site VPN or Direct Connect | VPN Gateway or ExpressRoute | Cloud VPN or Cloud Interconnect |
The check is the first step before migration and resilience, which carries out the move.
Not included
- Carrying out the migration (quoted separately as migration and resilience)
- Licence negotiations or licence audits
- Changes to application code
- A guaranteed run cost; the estimate depends on your usage after the move
What we need from you
- Read-only access to vCenter or Hyper-V, or approval to run the target cloud's discovery tool, or an export from your CMDB.
- A network diagram and your firewall rules, or the people who know them.
- 30–60 minutes with the owner of each important application.
- Your current infrastructure costs, if you want a cost comparison.
How it works
Free 30-minute call, then a written fixed quote based on the size of the estate.
Collect the inventory and, where possible, a week of performance data.
Interview application owners and map dependencies.
Report, wave plan and a 90-minute readout.
At a glance
- Duration
- 1–2 weeks
- Price
- Fixed quote after a free 30-minute call
- Delivered by
- Our lead architect
Related services
Cloud foundation check
In 1–2 weeks, we review your AWS, Azure or Google Cloud foundation against the CIS benchmark and tie every finding to evidence, the affected resources and a fix.
Zero Trust network review
A one-week review of how traffic enters, leaves and crosses your AWS, Azure or Google Cloud networks, with evidence for every finding, a target Zero Trust design and a prioritised roadmap.
Cloud cost quick wins
Lower your AWS, Azure or Google Cloud bill in one to two weeks by changing how the platform is built, from NAT and data transfer paths to commitments, with the quick wins delivered as code.