Practical guides

Windows Server and Proxmox migration checklist

Before moving a server, check application dependencies, VM compatibility, backups, downtime and the tests your team will use to accept the new setup.

Published · Reviewed

Server support and Proxmox in Mauritius All guides

Treat the application as the thing you are moving

A server migration is complete when the business can do its work in the agreed new environment. A virtual machine that starts successfully is one check, but staff may still need a working application, shared folders, printers, authentication and a connection to another branch.

Begin with the important workflows: issuing an invoice, opening the shared job folder or running the production application. Name a user who can check each workflow. This turns a vague instruction to move the server into an acceptance checklist.

Map the current server and its dependencies

Record enough information to plan the work without publishing passwords or confidential records. An inventory should identify what must be preserved and which suppliers need to participate.

  • Server platform, operating system, virtual machines, storage and available capacity.
  • Applications, databases, shared folders, printers, scheduled tasks and integrations.
  • User groups, service accounts, permissions, certificates and required remote access.
  • Network addresses, DNS dependencies, VPNs and links to other locations.
  • Backup locations, the latest successful jobs, available restore points and the last restore test.

Choose the right type of change

Moving a VM and upgrading its operating system are separate tasks. Microsoft’s supported migration or upgrade route depends on the Windows Server roles involved. Check the application vendor’s requirements.

For Proxmox, live migration depends on the hosts, CPU compatibility, network and VM configuration. Review the actual environment before assuming a VM can move while running.

Sources: Microsoft: Upgrade and migrate roles and features in Windows Server; Proxmox VE documentation: Virtual-machine migration

Before upgrading Windows Server

Microsoft calls for a full backup and a restore test before an in-place upgrade. Check the supported upgrade path, application requirements and maintenance window for the actual server.

Sources: Microsoft: Perform an in-place upgrade of Windows Server

Prepare a recovery option and a rehearsal

Before the move, confirm a usable backup and a recovery plan. Define rollback triggers, who authorises recovery and how new transactions will be retained.

Rehearse in an isolated test environment and check the business application. Proxmox supplies backup and restore facilities; the administrator must plan storage, guest and application requirements.

Sources: Proxmox VE documentation: Backup and restore

Make the maintenance window specific

Tell staff which systems will be unavailable, when they must stop work and who will announce that the new setup is ready. Allow time for checking and recovery instead of scheduling only the estimated copy time.

  • Take the agreed final backup or data capture and prevent conflicting writes during cut-over.
  • Run the named application, login, file-access and printing checks.
  • Have the business owner or nominated users accept the result before general use.
  • Confirm backups and monitoring cover the new environment, then document the new access and support details.
  • Retain or retire the former server according to the agreed recovery and records plan.

What to send with a migration enquiry

IT Works supports Windows Server, Proxmox, virtual machines, server backups and migrations in Mauritius. Include the current platform, key applications, users, locations, intended destination and acceptable maintenance times. If you have a known backup or capacity problem, mention it at the start.

Frequently asked questions

Can you guarantee a server move without downtime?

No general guarantee fits every environment. Application roles, network dependencies, storage and migration method must be checked. Agree a maintenance window and acceptance criteria for the actual system.

Sources: Microsoft: Upgrade and migrate roles and features in Windows Server; Proxmox VE documentation: Virtual-machine migration

Does moving a Windows VM to another Proxmox host upgrade Windows?

No. Moving the VM and changing the guest operating system are separate tasks. Include an operating-system change explicitly in the project scope if it is required.

Is a successful VM start enough to sign off the migration?

It is a useful technical check, but sign-off should also cover the business application, user access, required files or printers, backups and the workflows agreed before the move.

Sources and further reading

WhatsApp us