The Hyper-V-to-Proxmox Migration
Up to five guests moved off Hyper-V and onto the Proxmox you already run — each one back up on its own address with its own services, and its Hyper-V copy left shut down and ready to start if you do not like what you see.
Leaving Hyper-V is the easy decision. Going first with the server that runs the business is the hard part, because a Windows guest that comes up to a blue screen on a new hypervisor is not a problem you want at 2am.
We move up to five guests onto the Proxmox host or cluster you already run, one at a time, inside windows you pick. Each one comes back with its own address, its own disks and every service that was running before it moved, checked line by line against the picture we took beforehand. Our engineers put the drivers a Windows guest needs into it while it is still running on Hyper-V, which is why the first boot on the other side is a boot rather than a rescue.
We delete nothing on the Hyper-V side. Every guest we move stays where it is, shut down and ready to start, so going back takes one action and a few minutes. You get up to five business days to put your own applications through their paces before you commit.
What's included
Up to five guests moved onto the Proxmox host or cluster you already run, each on real VirtIO storage and networking instead of crawling along on emulated hardware
Windows guests treated as the normal case rather than the awkward one — Generation 2 machines rebuilt on UEFI firmware, Integration Services handed over to the Proxmox guest agent, and your fixed addresses put back where they were
A downtime figure for each guest, worked out from your own disk sizes and given to you before you agree a window, so you can tell your users a number
Every guest checked back against how it looked on Hyper-V: every service that was running is running again, the same ports answer, and every disk is present and readable
Your Hyper-V copies preserved and startable, with a one-line way back for each guest and up to five business days to test before you commit
A written report of where each Windows guest stands on activation, naming the ones whose Hyper-V licensing stops working the moment they leave the host
A plain-English handover of what runs where now, what to test first, and what is still sitting on the old host waiting for you to reclaim it
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
Administrator access to the Hyper-V host and inside each guest, plus root or an API token on your Proxmox
A read-only share over the folder holding the guest disks, with Hyper-V and Proxmox on the same site and a 1 Gbps or faster link
Checkpoints merged, Hyper-V Replica removed and BitLocker suspended on every guest that moves
Up to five guests named, each with the Proxmox bridge its network lands on
Your downtime windows, and how many business days you want to test before you commit
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The VMware-to-Proxmox Migration
Up to ten VMware guests moved onto your own Proxmox, one at a time, in windows you choose. Each one is proven booting and reachable before the next starts, and your original VM stays switched off and intact, so going back takes about a minute.
The Proxmox Cluster
Three Proxmox servers joined into one cluster with working high availability, proved by deliberately killing a node in a window you choose, so you watch the platform recover before you trust anything to it.
The Per-VM Setup
A new Linux VM on your own Proxmox, handed over finished: your keys in, root and password logins shut, and only the ports you named answering — each of those proved by trying it from a machine you choose rather than by reading a config file.
The Proxmox Backup Server Setup
Proxmox Backup Server standing behind every guest on your node or cluster, with one of your machines restored from its backup, booted in front of you and timed before we hand anything over.