
Unraid to Proxmox VE Migration: Your Pre-Migration Checklist
Your homelab migration comes down to three checks: Docker LXCs, ZFS pools, and PBS backups — run them before you touch a single disk.
Browse all Proxmox VE articles, tutorials, and in-depth guides on Proxmox Pulse. Expert content written for system administrators, homelab enthusiasts, and DevOps engineers working with Proxmox VE.

Your homelab migration comes down to three checks: Docker LXCs, ZFS pools, and PBS backups — run them before you touch a single disk.

A fresh Proxmox VE 9.2 box with a ZFS pool and a PBS 4.2 S3 backup job configured is not ready to run unattended.

A healthy pool can still hide stale scans, fragmentation, or dataset drift that break PBS restores before backup jobs.

A restore test proves the S3 path, not just that a backup job wrote metadata, so you know it works before an incident.

Catch storage, network, SSH, firewall, and backup failures before your first Proxmox VM starts, not after.

Before Proxmox VE 9.2 migration, verify boot path, ZFS alignment, SSH access, and firewall rules to avoid a locked node.

Move VMs only after you know which VLAN, VXLAN, firewall, and DNS settings actually apply to each Proxmox zone.

Three default OCI LXC settings can break DNS, firewall, and backups before your first production request hits service.

Compare Datacenter Manager inventory with live Proxmox API and SSH checks before automation to prevent wrong installs.

A timestamped text export turns Proxmox SDN state into a diffable restore point before risky cluster changes.

Empty SDN zones are the safest moment to lock down traffic, because renumbering VLANs under live VMs is painful.

New SDN interfaces can bypass old bridge rules, so audit Proxmox VE 9.2 zones before cross-tenant traffic slips through.