NetWarren_

Lessons › Servers & virtualisation

Running a server migration project

12 min lesson · Servers & virtualisation · free

▶ Start the interactive lesson

The plan is signed off: move about 150 physical servers onto the new cluster over six months. You've been asked to run wave 3: the 20 servers behind finance. Your team lead's only advice: "Nobody remembers a migration that went smoothly. Everyone remembers the one that broke payroll."

Discover before you move

Start with an inventory: every server, what it does, who owns it, what it talks to, and when it is busy. Dependency mapping matters most: the app server might need a database, a licence server and a file share that nobody wrote down.

Waves, windows and rollback

Group servers into waves by dependency, so an app and its database move together. Start with low-risk systems to prove the process.

After the move

Watch the VM for a few days: CPU, memory, disk latency and errors. Right-size it if it was given too much or too little.

Key points

Words you'll learn

P2V · Wave · Dependencies · Change window · Rollback plan · Cutover · Decommissioning

The full lesson has more: animations, a hands-on exercise, 3 quiz questions, a practical scenario test and spaced review cards. Open it free →