From VMware to Proxmox: an exit with a plan

Moving from VMware to Proxmox runs through an inventory, a target design on Proxmox VE and Ceph, a migration sequence, a move in waves, and a handover. We work with IT leads who have to decide on a VMware renewal or new hardware. We run Proxmox VE and Ceph ourselves, in production.

Request an intro call

Fixed-scope entry offer

VMware Exit Check

For whom: IT leads who, after a new VMware renewal quote or ahead of a hardware refresh, have to decide whether a move to Proxmox will work for them, and how.

Scope

  • One VMware estate, as it runs today.
  • Inventory: virtual machines, storage, network, backups, dependencies between systems, and the VMware features you rely on today (such as high availability or live migration).
  • Target design on Proxmox VE and Ceph: cluster, storage, network and backups.
  • Migration sequence: which systems move first, which move together, and where maintenance windows are needed.
  • Risks: what does not carry over one to one, and how to handle it.
  • A rough estimate of the migration effort.

DeliverableA written target design, a migration plan with sequence and risks, and a rough effort estimate, so you can decide whether and when to move. If something speaks against the move, the report says so.

Prerequisites

  • Read-only access to your VMware management, or an export of the inventory data.
  • Someone on your team who knows the estate, for questions.
  • What cannot be seen technically: dates such as the end of your contract, hardware you want to keep using, and business applications with vendor requirements.

Not included

  • The migration itself, including any pilot move of single systems. We quote the implementation afterwards as a separate project.
  • Building or running the Proxmox cluster, buying hardware or licences.
  • A cost comparison between VMware and Proxmox.
  • A review of your VMware contract or licence terms.

Request this offerfrybad.de/en/contact/?thema=vmware-proxmox&angebot=vmware-ausstiegs-check

Where teams usually start

  • The renewal quote does not fit the budget. The contract is running out, and you need a decision you can defend internally before it does.
  • The hardware is at the end of its life. New servers are due anyway, and you do not want to lock yourself into the same platform for the next cycle.
  • Unclear licences and features. You are not sure which VMware features you really use, and what a move would touch.

Migration path: how we work

  1. Inventory.

    Virtual machines, storage, network, backups, dependencies, and the VMware features you rely on. This is the VMware Exit Check.

  2. Target design.

    A Proxmox VE cluster, Ceph as shared storage, network and backups, on existing or new hardware. You get the architecture and the migration sequence.

  3. Build and first systems.

    We build the Proxmox environment next to VMware and move non-critical systems first. VMware stays usable until sign-off, as the way back.

  4. Move in waves.

    Proxmox VE ships with an import for virtual machines from ESXi. Each wave: import the VMs, adjust drivers (VirtIO for Windows guests, for example), move storage to Ceph, check. Every wave runs in an agreed maintenance window, with a rollback plan.

  5. Handover.

    Documentation, runbooks and a measured restore rehearsal on the new environment. After that you run it yourselves, or we run it within the agreed hours.

What we run ourselves

We run Proxmox VE and Ceph ourselves, in production. We run our own hardware in a data centre in Munich.

Our Kubernetes clusters and our product Fortlauf run on it. What we operate there and which restores we have measured: Where your data lives.

Since 2 Oct 2026, the storage and system disks of our virtualisation hosts have been encrypted.

Period: since

Kubernetes on Proxmox

After the move, not everything has to stay a virtual machine. Our own Kubernetes clusters run on Proxmox VE, with Ceph for storage. If you want to move applications into containers after the migration, Kubernetes platforms, built and run describes how we set that up. For GPU workloads: GPU servers in Germany.

Case study

Our own product

Fortlauf: running a SaaS on our own infrastructure

Fortlauf is our product. We built it, and we run it on our own hardware. In production since July 2026: tenant isolation in the database, immutable document storage, delivery by GitOps, measured recovery.

Who you will talk to

One fixed contact from the intro call to the handover.

Send a message

What we do not do

  • No resale of VMware or other licences.
  • No migration without a rollback plan: VMware stays usable until you sign off the move.
  • No review of your VMware contract or licence terms. That is for your legal or licensing advisers.

Frequently asked questions

How long does a migration take?

It depends on the number of systems, their dependencies and the maintenance windows you can offer. A reliable estimate is one of the results of the VMware Exit Check; before that, we do not name a figure.

Do we need new hardware?

Not necessarily. Proxmox VE runs on standard x86 server hardware. Whether your existing servers suit Ceph depends mostly on their disks and network; the Check answers that.

Is Proxmox VE ready for production?

We run our own production on it, including our product Fortlauf. What we have measured there is on Where your data lives, with dates.

What happens to backups and monitoring?

Both are part of the target design. Not every backup tool you use with VMware supports Proxmox VE. We check this in the inventory and propose what stays and what gets replaced.

Can it be done without downtime?

Not for every system. Many virtual machines need a short maintenance window for the switch. We plan the windows with you, move in waves and keep the way back to VMware open until you sign off.

Insights

Want to talk about the move?

Tell us what your VMware estate looks like today and when you need to decide.