Import VMs

Purpose

• Discover unmanaged VMs already running on a connected cluster.
• Review which VMs are available to import and which are blocked, per cluster.
• Adopt one or more available VMs into a chosen account as managed VMs.
• Understand why a VM is blocked from import.

Prerequisites

• Available to root accounts only.
• Minimum permission to view: platform.importvms.read
• Permission to import VMs: platform.importvms.create
• The target account needs a compute quota on the cluster and a storage pool that supports VM disks.
• Run cluster discovery first so unmanaged VMs are detected.

Browse discovered VMs by cluster

1. Open Platform → Import VMs (root account only).
2. Review each cluster card's Available VMs and Blocked VMs counts.
3. Choose Available VMs to list VMs ready to import, or Blocked VMs to list those that cannot be.
4. Expected result: a per-cluster breakdown of unmanaged VMs is shown.

Review available and blocked VMs

1. Open Platform → Import VMs (root account only).
2. Choose a cluster's Available VMs to see VM Name, Proxmox ID, vCPU, RAM (GB), Disks, and vNICs.
3. Choose a cluster's Blocked VMs, then click a row to read why it is blocked.
4. Expected result: you can see each unmanaged VM's profile and any blocking reasons.

Import VMs

1. Open Platform → Import VMs (root account only).
2. Choose a cluster's Available VMs and select one or more VMs.
3. Choose Import VMs to open the import configuration.
4. Choose the target Account.
5. Enter a Base VM Name (imported VMs are numbered, e.g. web-server-1, web-server-2; disk names follow the VM name).
6. Optionally enter a Description.
7. Choose a Storage Pool (only pools that support VM disks are listed).
8. Set the VM Importance (High, Medium, or Low).
9. Choose Import VMs.
10. Expected result: one import task is queued per VM; track progress in the Task Manager.

A single import batch must belong to one cluster, and only VMs marked available (ready) can be imported.

Best Practices

• Import VMs from a single cluster at a time — a batch must belong to one cluster.
• Ensure the target account has a compute quota on the cluster and enough storage quota before importing.
• Use a Base VM Name that produces valid resource names, since VM and disk names are derived from it.
• Check the Task Manager after importing; imports complete asynchronously.