Proxmox 9.1 is based on Debian 13 Trixie and brings a newer kernel, new features, and long-term support. This guide gives you the real numbers — duration, cost, steps — so you can plan your migration with confidence.
Proxmox VE 9.x marks a major base change: the move from Debian 12 Bookworm to Debian 13 Trixie. Here are the main reasons to migrate now.
Debian 13 base with long-term support. You benefit from the latest security updates and a modern foundation for years to come.
Recent Linux kernel with improved hardware support, performance enhancements, and new virtualisation features (QEMU, LXC).
Debian 12 Bookworm will eventually reach end of life. Planning your migration early prevents running an unsupported OS in production.
Our entire production infrastructure already runs on Proxmox 9.1. See our technical field report on the 8-to-9 migration.
Our 4-step methodology ensures a controlled migration, node by node, with no service interruption in HA cluster environments.
Hardware compatibility check, inventory of third-party extensions and plugins, Ceph/ZFS version verification if applicable, overall cluster health assessment. Potential risks are identified before any work begins.
Update to the latest 8.x release (currently 8.4). This is a mandatory prerequisite before upgrading to version 9. Each node is verified after the update.
APT repository migration, Debian 12 to Debian 13 upgrade, installation of new Proxmox VE 9.1 packages. Each node is rebooted and verified before moving to the next one.
Comprehensive post-migration testing: cluster status, networking, storage, VMs and containers. Any minor issues are resolved, and the entire infrastructure is validated for correct operation.
Total duration depends on the number of nodes and the complexity of your environment. Here are our estimates based on real-world experience.
| Small cluster (<5 nodes, <75 VMs) |
Medium cluster (<10 nodes) |
|
|---|---|---|
| Audit | Half day | 1 day |
| Upgrade per node | 1h30 | 1h30 |
| of which: 8.4 update | 30 min | 30 min |
| of which: 9.1 upgrade | 1h | 1h |
| Post-migration monitoring | Half day | 1 day |
| Total duration (3 nodes) | ~1.5 days | — |
| Total duration (5 nodes) | ~2 days | — |
| Total duration (8 nodes) | — | ~2.5 days |
In HA clusters: VMs automatically migrate to other nodes during the upgrade. Zero service interruption for your users.
Our pricing is based on a daily rate of EUR 850/day. The package includes the audit, the upgrade of each node, and post-migration monitoring.
3 nodes
EUR 1,390
850 + (3 x 180)
5 nodes
EUR 1,750
850 + (5 x 180)
8 nodes
EUR 3,140
850 + 850 + (8 x 180)
For clusters with more than 10 hypervisors, we provide a custom quote tailored to the complexity of your environment.
Request a QuoteThe initial quote may be revised after the audit if unexpected issues are discovered: incompatible third-party extensions, atypical configurations, Ceph versions requiring a specific migration path, etc. The audit is specifically designed to identify these risks before any work begins.
Before starting the migration, several checks are essential to ensure a smooth upgrade.
A complete backup of all VMs and cluster configuration must be performed before the migration. Our NimbusBackup solution is designed for exactly this purpose.
Third-party extensions (DKMS, custom kernel modules) must be verified for compatibility with Debian 13 and the new kernel. Some may require recompilation or updating.
If your cluster uses Ceph, the version must be compatible with Proxmox 9.x. A specific Ceph migration may be required and will be identified during the audit.
During a node upgrade, no live migration should be initiated to or from that node. VMs are moved away before the upgrade begins.
In HA clusters, we always start with a single node. This validates the upgrade process before proceeding with the remaining nodes. If something goes wrong, rollback is limited to a single hypervisor.
A poorly prepared Proxmox migration can lead to service outages, data loss, or hours of debugging. Here is what we bring to the table.
Our entire production infrastructure runs on Proxmox 9.1. We know the pitfalls and best practices. Read our full technical field report.
If a critical issue arises, we know how to revert cleanly. The pre-migration backup and our experience provide a solid safety net.
In high-availability clusters, we migrate node by node. Your VMs remain accessible throughout the entire process thanks to automatic live migration.
Post-migration monitoring (half a day to 1 full day) is included in the package. We verify that everything is running correctly and fix any minor issues.
All-inclusive package: audit, upgrade of each node (8.4 then 9.1), and post-migration monitoring. Base rate: EUR 850/day, EUR 180 per node.
3 nodes
EUR 1,390
~1.5 days
5 nodes
EUR 1,750
~2 days
8 nodes
EUR 3,140
~2.5 days
Cluster >10 nodes: custom quote. Post-migration managed services available from EUR 70/month per server.
Duration depends on the cluster size: approximately 1.5 days for 3 nodes, 2 days for 5 nodes, and 2.5 days for 8 nodes. Each node requires about 1.5 hours of upgrade time (30 min for the 8.4 update + 1 hour for the 9.1 upgrade), plus audit and post-migration monitoring time.
The cost varies by cluster size: EUR 1,390 for 3 nodes, EUR 1,750 for 5 nodes, and EUR 3,140 for 8 nodes. The price includes the initial audit, the upgrade of each node, and post-migration monitoring. For clusters with more than 10 nodes, a custom quote is provided.
In an HA cluster (High Availability), the migration is performed node by node with no service interruption. VMs automatically migrate to other nodes during each hypervisor's upgrade. On a single-node setup, VM downtime is required during the upgrade (~1.5 hours).
Yes. Updating to the latest 8.x release (currently 8.4) is a mandatory prerequisite before you can run the upgrade to Proxmox 9.1. This step takes approximately 30 minutes per node and is included in our package.
Post-migration monitoring is included in the package (half a day to 1 full day depending on cluster size). In case of a major issue, a rollback is possible thanks to the full backup taken before the migration. Additionally, the initial quote may be revised after the audit if atypical configurations require special handling.
Debian 12 vs 13 comparison, kernel opt-in, commands, field report from our production infrastructure.
PBS, deduplication, verify jobs. Our multi-datacenter method before any migration.
Our team has already migrated its entire production to Proxmox 9.1. Leverage our field experience for a stress-free migration, node by node, with zero service interruption.