When a server hardware replacement is due or a complete reinstallation on a different machine is coming up, the question quickly arises whether the existing Proxmox subscription can move along or has to be purchased again. The good news: Proxmox allows the subscription key to be transferred to new infrastructure, but under certain conditions you should know in advance.
The process can be completed via the customer portal without support having to step in, as long as the policies are followed. First, log in to the shop area and navigate to your services. There you will find the corresponding subscription entry, which you need to open. The “Reissue” option generates a new key, which is then entered on the target server. Finally, check the status in the Proxmox web interface under the “Subscription” tab so that the system recognizes the change and enables the correct package repositories.
It is important to note that reissues are not unlimited. Proxmox explicitly reserves this option for hardware replacements or fresh installations on a different physical basis. Anyone who wants to move their subscription around seemingly at will runs into a limit. In that case, contacting support directly is necessary to discuss an exception or open a new ticket. A common mistake is pressing the reissue button for every minor update; the limited quota is used up quickly.
One frequently overlooked point concerns the sales channel. If the subscription key was purchased through a Proxmox partner, the transfer is not handled via the public shop portal but directly through the partner. There you receive the necessary support and the correct workflow, since the key is administered by the partner and is not visible in the public customer area.
Cluster users should pay particular attention: in a Proxmox VE cluster, all nodes must have the same subscription level. A single node with a different key leads to inconsistencies and can block updates or features. So if you are only moving one node, check beforehand whether the key covers the entire cluster or whether additional licenses are required. The Basic, Standard, and Premium levels do not differ in the transfer process, but they do in the features available after the switch.
For the practical procedure, it is advisable to note down the old key before the handover and to prepare the new server in maintenance mode first. This ensures that the correct subscription is recognized immediately after the reboot and that there is no downtime due to missing repository access rights. After uploading the new key and clicking “Check”, the status in the web interface should switch to “OK”. If it does not, it is worth looking at the network configuration and the correct entry of the key, since even a trailing space can cause the error.
Conclusion: Moving a Proxmox subscription is no rocket science, but it does require attention to the reissue rules and the sales channel. If you keep these points in mind, you save yourself a new subscription and avoid unnecessary support tickets. Above all, a quick check of the cluster setup is worthwhile before the new key becomes active.