Blog

Before a cloud migration: what to prepare

November 9, 2026 · cloud · migration · 1 min read

The risk of a cloud migration is not moving the data: it is discovering halfway through a dependency nobody remembered. The most useful work is done beforehand.

1. The inventory

List servers, applications, databases, shared folders and connected services (email, backups, network printers, programs that connect from outside). For each one, note who uses it and how important it is.

2. The dependencies

For each service ask: what does it depend on? A management system may depend on a database, a network folder, a certificate and a nightly export job. Hidden dependencies are the ones that block the cut-over.

3. Which interruptions are acceptable

Not every service has the same weight. Decide for each how long it can be down and at what time of day: it helps choose the order and timing of the steps.

4. The restore test

A backup that has never been restored is a hope. Before migrating, try restoring a copy in a test environment: it is the only way to know the data can be recovered.

5. The cut-over criteria

Define in advance what “it went well” means: services reachable, data verified, access working, and how to go back if something fails. Also keep platform costs separate from management costs.

If you are considering a move, tell us about your current infrastructure. The overview is on the cloud infrastructure page.

← All articles