---
title: "Moving off your own servers: a cloud migration in waves"
updated: "2026-11-17"
url: "https://www.etheon.com/company/news/a-cloud-migration-in-waves"
authors: "Etheon"
published: "2026-11-17"
type: "news"
---

# Moving off your own servers: a cloud migration in waves

Migration moves your systems off your own servers to the cloud you choose, in planned waves, each workload with a rollback point.

Migration moves your systems off your own servers to the cloud you choose, in planned waves, each workload with a rollback point, so the business keeps running while it moves. The old servers are switched off when nothing depends on them.

## What happens first?

Taking stock, the first of four steps:

1. Take stock: every workload, its callers and its data.
2. Plan the waves: which workload moves when, each with a rollback point.
3. Move: one wave at a time, the business running throughout.
4. Switch off: the old servers, once nothing depends on them.

## How are the waves planned?

By which workload moves when, each with a rollback point. On our Cloud page an example board shows the idea: the website and the customer API in the first wave, reports and the data warehouse in the second, batch jobs in the third.

## What does the migration leave you?

- A migration plan in waves.
- The new environment as code.
- A rollback plan for each wave.

## When are the old servers switched off?

Once nothing depends on them. Until then each workload moves with a rollback point, so the business keeps running while it moves.

## Which clouds do you work with?

AWS, Microsoft Azure, Google Cloud and Nebius.

## Who secures what once you have moved?

Your cloud provider, our engineers and your team, each with a clear part. The provider runs the data centres and the hardware; we set up the network, the roles and single sign-on, and build, test and review the application code; your team decides who gets access and what is kept, and holds the keys if you choose. The whole division is on our [Cloud page](https://www.etheon.com/services/cloud#who-secures-what).

## What if the old application must change too?

Then it is replaced in steps, not only moved. Legacy modernization replaces an old system while the business keeps running on it, one module at a time with a rollback at each step: see [Software](https://www.etheon.com/services/software#modernization).

"Moving off our own servers" is one of the needs on our [Services page](https://www.etheon.com/services#which-service): your systems moved to the cloud in planned waves. The migration and its waves are drawn on our [Cloud page](https://www.etheon.com/services/cloud#migration). Tell us your use case and timeline. We reply within one business day.