The Proxmox-to-Proxmox Migration
Up to twelve machines and containers moved onto your other Proxmox with the same disks, the same MAC addresses and the same machine IDs. We change nothing inside any of them, and each old copy stays switched off and ready to start.
New hardware is the easy part of a Proxmox refresh. Moving the guests onto it is the part you keep postponing, because you do not want to be the one holding a production machine that will not boot on the other side.
Your guests are already KVM machines and LXC containers, so there is nothing to convert. We move up to twelve of them, one at a time, in windows you pick, and each arrives with the same disks, the same MAC addresses and the same machine ID it had before. We never open a guest on either side, so the software inside it never learns that it moved.
The old copy stays where it is, switched off and ready to start, so any guest goes back in about a minute. Our engineers have been moving production systems between platforms since 2003, and you get the proof per guest before you sign it off.
What's included
Up to twelve guests moved onto the other Proxmox you already run, with machines and containers counting the same, so a dozen containers costs what a dozen machines does
Each guest arrives as the machine it was: same disks in the same order, same MAC addresses, same firmware and same machine ID, which is why your Windows servers do not come up asking to be activated again
We never open a guest on either side, so no new driver, agent or package lands in your machines to go wrong six months from now
Containers moved with their mount points, their privilege level and their feature flags intact, because a rebuilt container is not the container you had
A downtime figure for every guest, worked out from a transfer rate we measure on your own link and handed to you before you agree a window, so you can tell your users a number
Four checks recorded per guest before you sign it off: it starts, it answers on the network from a host you name, every disk and mount point is present at the right size, and its configuration matches the old one line for line
Your old guests left switched off, intact and marked so nobody restarts one by accident, plus a plain-English handover of what now runs where and what is still sitting on the old environment 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.
Your list of up to twelve guests, with each one's disk size and a port it should answer on
Accounts on both Proxmox environments, with the target running, able to reach the source, and carrying the storage and bridges your guests will land on
Which source storage and bridge map to which on the target
High availability and replication taken off each guest before its window
Your migration windows, the person who signs off each guest, and a host on your network we check from
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 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 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.
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 Per-LXC Setup
A new Linux container on your own Proxmox, handed over finished and unprivileged by default: your keys in, root and password logins shut, only the ports you named answering — and the isolation you actually got written down instead of assumed.
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.