Compute
Private Cloud
Your own quota, your own gateway and your own identity provider.
Cloud Migration
Move your servers to the Nesnet cloud with a migration that is planned, rehearsed and ready to roll back
Migration runs as a project: the inventory and dependencies are mapped first, systems are grouped by how much downtime they tolerate, and every group is rehearsed on a copy. What happens on cutover night — and how to roll back if the plan fails — is written down in advance.
Why now
Warranties end, the calendar is tight
Hardware goes out of warranty within months, and every week spent deciding between refreshing and moving narrows the options.
Nobody is sure what depends on what
Servers added over the years, forgotten scheduled jobs and hard-coded IP addresses can turn cutover night into a chain of surprises.
The downtime window is tiny
Finance can’t stop at month end and e-commerce can’t stop during a campaign; the move has to fit into a few hours.
The last migration went badly
An unplanned move with no way back turned into an all-night outage, and the team is wary of trying again.
What changes
| Today | With Nesnet |
|---|---|
| No one knows what will break on cutover night. | Every system is migrated and verified on a copy first; on the night, only rehearsed steps run. |
| Dependencies surface after the move, when something breaks. | What depends on what is mapped before anything moves. |
| Downtime is an estimate. | Downtime is measured during the rehearsal and shared with the business in advance. |
| If the plan fails, the fallback is improvised that night. | The rollback step is written from the start, and the old system stays on until verification is complete. |
| Once the move is done, the team is alone with the new environment. | Migrated systems are handed over with monitoring and backup already defined. |
From today to live: how it works
- 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, time windows and owners are agreed with the business.
- 3
Pilot migration
A non-critical system and copies of the critical ones move first, are verified with the application team, and downtime is measured.
- 4
Planned cutover
Groups move in the agreed windows and every system is checked against a list; if the plan fails, the written rollback step runs.
- 5
Handover and monitoring
Migrated systems are handed over with monitoring, backup and firewall rules; the old environment is shut down only on your approval.
What you get
Inventory and dependency report
Resource needs, connections and downtime tolerance for every system, collected in one written report.
Sizing and cost outlook
Current usage is measured to work out the CPU, memory and storage you need in the cloud, so the monthly cost drivers are visible up front.
Written migration plan
Order, windows, owners and communication steps in a single plan.
Rehearsal migration
Critical systems are migrated and verified on a copy first, so the real cutover follows proven steps.
Rollback plan
For every group, how to return to the old system if the plan fails is written in advance.
Verification and handover
Each migrated system is checked against a list, with backup and monitoring defined from day one.
Why Nesnet
Your migration is planned by the team that carries out the Nesnet cloud’s own large platform transformations — step by step, verified, with a written way back.
Example scenarios
A server room at end of warranty
Situation
A manufacturer’s server-room hardware goes out of warranty within six months; ERP, the file server and e-mail all live there.
Outcome
Systems are split into three groups: the file server goes first as the pilot, and ERP moves in a planned weekend window after month-end close.
An online store with a narrow window
Situation
The site can’t stop during campaigns, the database is large and even night traffic never drops to zero.
Outcome
Data is copied ahead of time and kept in sync, and the cutover happens at the quietest hour with a short final sync.
Consolidating branch servers
Situation
Every branch has its own ageing servers, each looked after by a different team.
Outcome
Branch systems are consolidated into one cloud environment, and branches reach the same applications over VPN.
Who does what
| Nesnet | You |
|---|---|
| Inventory, dependency map and sizing | Sign-off from application owners and the business |
| Migration plan and rollback steps | Choosing the downtime windows |
| Rehearsal migration and downtime measurement | Application-level testing (business workflows) |
| Planned cutover and technical verification | Licence and third-party software details |
| Monitoring and backup setup | Approval to retire the old environment |
Related products
Compute
Virtual Servers
Linux and Windows servers, live in minutes and self-healing after failures.
Data Protection
Backup
Back up your servers and restore them yourself, no ticket needed.
Data Protection
Business Continuity
An up-to-date copy of your on-prem servers, ready in our cloud.
Questions to ask before you decide
- Can we lose data during the move?
- The old system keeps running and is not shut down until verification is complete. If the plan fails, the written rollback step runs and the system carries on where it was.
- How much downtime should we expect?
- It varies by system and is measured during the rehearsal. The measured figure is shared with the business in writing before cutover.
- Do we have to reconfigure our applications?
- Usually not: virtual servers move as they are. Any IP, licence or external connection change is listed during the inventory and built into the plan.
- Can physical servers be moved too?
- Yes. Physical servers are converted to virtual servers first, then moved with the same plan and rehearsal steps.
- Will the cost surprise us after the move?
- Sizing is based on measured usage, so the monthly cost drivers are visible before anything moves. Usage is watched in the first months and oversized servers are scaled down.
- How is a migration priced?
- As a project, by the number and complexity of the systems. You receive a written quote after the inventory call.
Questions about these products
Private Cloud
- Will the invoice hold any surprises?
- The invoice is made up of vCPU, memory, NVMe storage, gateways, load balancers, public IPs and internet bandwidth, each on its own line. The number of servers you create inside your quota doesn't change the price on its own; the resources you use do. Nesnet's team prepares the actual figures for your needs.
- Will I face downtime while moving my existing virtualisation environment?
- Migration follows a plan: an inventory comes first, a non-critical system moves as a pilot, and the main cutover happens in a window you choose. Servers can be uploaded as OVA or moved while running with migration tooling. Downtime depends on the size of the system and the route chosen, and the rollback step is written before the cutover.
Virtual Servers
- What is a virtual server, and how is it different from a VPS, shared hosting or a physical server?
- A virtual server is a computer with its own operating system, carved out of a powerful physical host’s CPU, memory and disk. A VPS is the same idea under another name; at Nesnet the difference is that your server isn’t tied to one machine. On shared hosting you never see the operating system, and with a physical server the repairs and spare machines are yours when it breaks.
Business Continuity
- Can I see the plan work before a disaster?
- Yes, you can. Copies are brought up in an isolated network for testing without disturbing ongoing replication, and you check that your applications start. When the test ends, the test servers are removed.
Start your migration plan with one inventory call
We go through the systems to move, the downtime windows and your priorities, then send a written plan and quote.