Compute
Private Cloud
A resource pool with its own quotas, network and users.
Cloud Migration
Move your servers to the cloud with a planned, rehearsed migration
Migration runs as a project: inventory and dependencies are mapped, systems are grouped by how much downtime they tolerate, and each group is rehearsed on a copy first. What happens on migration night, and how to roll back if the plan fails, is written down in advance.
Service scope
Inventory and dependency report
Resource needs, connections and downtime tolerance of every system are collected in a written report.
Sizing and cost forecast
Current usage is measured to work out the CPU, memory and storage needed in the cloud, so the items that drive the monthly cost are visible up front.
Written migration plan
Order, time windows, owners and communication steps sit in one written plan.
Rehearsal migration
Critical systems move on a copy first and are validated, so the real move uses proven steps.
Rollback plan
For every group, how to return to the old system if the plan fails is written in advance.
Validation and handover
Every migrated system is checked against a list, with backup and monitoring in place from day one.
How to get started
- 1
Inventory and dependency map
Servers, applications, databases and the connections between them are mapped and documented.
- 2
Grouping and plan
Systems are grouped by downtime tolerance; order, windows and owners are agreed with the business units.
- 3
Pilot migration
A non-critical system and copies of critical systems move first, are validated with the application team, and downtime is measured.
- 4
Planned migration
Groups move in the agreed windows and every system is checked against a list; if the plan fails, the written rollback step is applied.
- 5
Handover and monitoring
Migrated systems are handed over with monitoring, backup and firewall rules, and the old environment is shut down with your approval.
Who does what
| Included in the service | On your side |
|---|---|
| Inventory, dependency map and sizing | Approval from application owners and business units |
| Migration plan and rollback steps | Setting the downtime windows |
| Rehearsal migration and downtime measurement | Application-level testing (business workflows) |
| Planned migration and technical validation | Licence and third-party software details |
| Monitoring and backup setup | Approval to shut down the old environment |
Related products
Compute
Virtual Servers
Linux and Windows virtual servers, ready in minutes.
Data Protection
Backup
Centralised backup against outages and cyberattacks.
Data Protection
Business Continuity
Disaster recovery that replicates on-site servers.
Frequently asked questions
- Can we lose data during the migration?
- The old system stays running and is not shut down until validation is complete. If the plan fails, the written rollback step is applied and the system keeps running where it was.
- How much downtime should we expect?
- Downtime differs from system to system and is measured in the rehearsal migration. The measured figure is given to the business unit in writing before the move.
- Do we have to reconfigure our applications?
- Usually not: virtual servers move as they are. Any IP address, licence or external connection changes are listed during inventory and go into the plan.
- Can physical servers be migrated too?
- Yes. Physical servers are converted to virtual servers first, then moved with the same plan and rehearsal steps.
- How do we know the monthly cost after the move?
- Sizing is based on measured usage, so the items that drive the monthly cost are visible before the move. Usage is tracked in the first months and oversized servers are scaled down.
- How is the migration priced?
- Migration is priced as a project by the number and complexity of systems; the price is given in writing once the inventory is done.
About the related products
Private Cloud
- How are my resources separated from other customers?
- Your resource quotas, network and users are reserved for your organisation. Your organisation's network traffic passes through its own gateway.
- How does it differ from Virtual Servers?
- A private cloud gives your organisation a resource pool with CPU, memory and storage limits, its own gateway and its own user management. With Virtual Servers you take servers one at a time; with Private Cloud you create the servers inside the pool yourself.
Virtual Servers
- How are virtual servers priced?
- Each server is billed on the number of vCPUs, the amount of memory and the disk size you choose.
Business Continuity
- What workloads can I protect with Business Continuity?
- Workloads running in virtual machines in your on-site environment. Which servers are protected is chosen server by server in the quote.
Take the next step
Tell us which systems you want to move; a written plan and price proposal follows the call.