Published: March 11, 2026
By: David Nicholson

Step By Step: Method A Proxmox Import Wizard

We will walk you through the step-by-step process of using the Proxmox Import Wizard to migrate your virtual machines from VMware to Proxmox. If your organization doesn’t have the expertise to handle migrating VMware to Proxmox, Nfina will do all of this for you! Before we dive into the import process, there are a few prerequisites that need to be in place.’

Prerequisites:

1. Proxmox Hardware Requirements must be met
   2. Access to ESXi server – In order to use the Proxmox Import Wizard, you will need access to your existing VMware ESXi server where your virtual machines are currently running.
   3. Exported OVF file – You must have an exported OVF (Open Virtualization Format) file for each virtual machine that you want to migrate. Make sure these files are stored in a location accessible by your Proxmox server.

The import process:

1. Connect to ESXi Server – To begin with, log in to your Proxmox web interface and navigate to Datacenter > Storage > Add > Directory.
2. Give a name for this storage location and enter the path where you have saved all the exported OVF files.
3. Next, click on ‘Content’ tab and enable ‘Default’ as well as ‘VMDK images’ options under format field.
4. Click on ‘Add’ and then click on ‘Storage’ tab again.
5. Select “Content” from drop-down menu beside “View:” option at top left corner of page.
6. Now choose newly added directory storage and hit “Upload”.
7. Browse for OVF files that you wish to import from ESXi server and select “OVF” or “OVA” archive as upload method.
8. Once selected, click on ‘Start Upload’.
9. The upload process may take some time depending on the size of the OVF file(s). Once it is completed successfully, close this window.

First Boot:

1.  Now, you will see the imported virtual machines under the “Virtual Machines” tab.
2. Select a virtual machine that you want to import and click on ‘Start’ button located at top menu bar.
3. Select the storage location where you want to store this VM’s disk and click “Next”.
4. Next, select the format of disk which you want to use i.e., qcow2 or raw (recommended) and then hit ‘Import’ button.

Post-Import Tuning:

After successfully importing your virtual machines from VMware to Proxmox, there are a few additional steps that need to be taken for optimal performance

1. VirtIO SCSI – it is recommended to use VirtIO SCSI as the storage controller for better I/O performance.
2. Guest Agent – Install Proxmox guest agent in each of your virtual machines for better communication between host and guest systems.
3. Network Validation – Make sure all network interfaces are correctly configured after the migration process is completed.

Step-by-Step Method B: Veeam Migration 

This method can be used when you want to have the option of rolling back or performing a staged cutover during the migration process. Additionally, we will also cover the necessary steps for restoring your data and configuring key settings in Proxmox after the migration is complete.

Preparing Migration:

Before beginning the migration process, it is essential to ensure that all prerequisites are met. These include having a valid license for Veeam Backup & Replication and installing the software on both the source VMware server and destination Proxmox server. You should also verify that both servers have enough storage space available to accommodate the backups.

Configuring Job Settings:

Once Veeam Backup & Replication is installed on both servers, you need to configure job settings on your source VMware server. This includes selecting which VMs you want to migrate, setting up schedule options, and choosing whether you want continuous replication or periodic backups during the migration process.

Performing Backup or Replication:

You can choose between two methods with Veeam – backup or replication – depending on your specific needs and preferences.

a) Backup: If you opt for backup as your preferred method of migration, Veeam will take a snapshot of your VMs at regular intervals during which any changes made will be captured.

b) Replication: With replication, instead of backing up at regular intervals, Veeam creates an exact copy of your VMs in real-time and transfers them over to Proxmox.

Restoring to Proxmox:

Once the backup or replication process is complete, you can restore your VMs to Proxmox. This can be done through Veeam’s “Restore to VMware” wizard, where you will select the target Proxmox server as the destination for your migrated data.

Configuring Key Settings in Proxmox:

After restoring your VMs to Proxmox, there are a few key settings that need to be configured for everything to function correctly.

a) Network Settings: You will need to set up network interfaces and connections on your newly migrated VMs in Proxmox.

b) Storage Settings: Mounting storage devices is essential for accessing data during migration and configuring them correctly ensures smooth operation of your VMs.

c) Virtual Machine Configuration: You will need to configure the virtual machine settings such as CPU, RAM, and disk space allocation according to your requirements.

Step-by-Step Method C: Manual Migration

This method involves exporting your virtual machines as OVF/OVA files, converting them into VMDK format, configuring the VM settings, and making note of any boot mode changes.

Exporting as OVF/OVA files: The first step in manual migration is to export your virtual machines from VMware as OVF/OVA files. This is done by selecting the virtual machine in vSphere or vCenter, then navigating to File > Export > Export OVF Template. Choose a location to save the file and click on “Export”. Repeat this process for all the VMs that you want to migrate.

Converting to VMDK format:

Once all your VMs are exported as OVF/OVA files, the next step is to convert them into VMDK format which is used by Proxmox. There are several tools available online for this conversion such as StarWind V2V Converter or VMware’s own vCenter Converter Standalone tool.

Configuring VM settings:

After converting the VMs into VMDK format, you need to configure their settings in Proxmox before importing them. This includes assigning memory and CPU resources, setting up network interfaces, and attaching storage devices. It is important to ensure that these settings match those of your original virtual machine in order for it function properly on Proxmox.

Making note of boot mode changes:

One key difference between VMware and Proxmox is their respective boot modes – BIOS (legacy) and UEFI (modern). If your original VM was set up with one boot mode but Proxmox does not support it, then you may need to change it during the migration process. Make sure to take note of any changes made so that you can adjust accordingly after importing the VM.

Importing the VM:

After completing all the above steps, you can now import your virtual machines into Proxmox. This is done through the “Create VM” option in Proxmox’s web interface. Select “Import existing disk image” and choose the VMDK file that was converted earlier. Once imported, you can start up your VM and make any necessary adjustments to ensure it is functioning properly on Proxmox.

Common Issues & Fixes: 

1. Boot Blocks:

One of the most common issues encountered during a migration is related to boot blocks. This issue occurs when the migrated system fails to boot after the migration process is complete. To fix this issue, you can try re-creating the boot loader with proper configuration settings or check if all necessary files are present in the correct location.

2. NIC/VLAN Configuration:

Another known issue is with network interface card (NIC) and virtual LAN (VLAN) configurations after migration. This can cause connectivity problems, as well as errors while accessing network resources from within the VMs. To address this issue, ensure that all NICs and VLANs are configured correctly on both ends – both on Proxmox and on any external switches or routers.

3. UEFI/BIOS Settings:

For systems using UEFI instead of BIOS, there may be compatibility issues after migrating to Proxmox. This could lead to boot failures or other performance-related problems post-migration. It is important to check and adjust UEFI/BIOS settings accordingly before initiating the migration process.

4. Driver Compatibility:

Driver compatibility can also be a potential roadblock during a VMware to Proxmox migration. When hardware components differ between source and destination platforms, drivers may need to be updated or changed altogether for proper functionality of devices like storage controllers or network adapters.

5.Poor Performance:

After migrating your virtual machines from VMware to Proxmox, you may experience decreased performance levels compared to what was experienced before the migration took place.. There could be several reasons for this – incompatible hardware components, outdated drivers, incorrect CPU pinning settings etc.. Ensure that all hardware is compatible with Proxmox and that the necessary drivers are installed and up-to-date to resolve this issue.

Security and Hybrid Architecture Considerations 

When considering a hybrid architecture for your organization’s cloud infrastructure, security should be a top priority.

Segmentation

Segmentation involves dividing your network into smaller subnetworks or segments. This helps control the flow of traffic between different areas of your infrastructure and allows for better isolation in case of a security breach. When implementing a hybrid architecture, it is essential to segment your network based on the sensitivity of data and the level of access required by different users or applications.

Access controls

With multiple environments involved in a hybrid setup, it is crucial to have strict access controls in place to prevent unauthorized access. This includes implementing role-based access control (RBAC), multi-factor authentication (MFA), and regular monitoring and auditing of user activity. By limiting access only to those who need it, you can reduce the risk of potential attacks.

Proper management of plane hygiene

Plane hygiene refers to the measures taken to secure the communication channels between different components within your infrastructure. In a hybrid setup, this means ensuring that all connections between your on-premise environment and the public cloud are encrypted using secure protocols such as SSL/TLS.

At Nfina Technologies, we understand the importance of having robust security measures in place for any enterprise-level solution. Nfina’s Hybrid Cloud Security service provides advanced segmentation capabilities through SDN technology that allows you to define policies for traffic flow between different environments easily. We also offer RBAC functionality with MFA options for added layers of security.

Nfina’s’ Enterprise Hybrid Cloud solution is designed to provide a seamless and secure integration between your on-premise environment and the public cloud. With our expertise in both VMware and Proxmox, we can help you migrate from one platform to another without compromising security.

Workload-Specific Considerations

If you are considering migrating your AI/ML workloads from VMware to Proxmox, it is essential to understand the GPU considerations involved. Here are some key factors to keep in mind:

1. Compatibility with Proxmox

Not all GPUs are created equal, and not all of them will be compatible with Proxmox. It is crucial to check Proxmox’s Hardware Compatibility List (HCL) before selecting a GPU. The HCL specifies which graphics cards have been tested and found to be working with Proxmox.

2. Type of workload

The type of AI/ML workload you will be running plays a vital role in determining the appropriate GPU for your needs. For instance, if your workload requires high memory bandwidth or floating-point operations per second (FLOPS), then you will need a different type of GPU compared to one that needs massive data transfer rates.

3. Memory size

The amount of memory on your chosen GPU should match the requirements of your workload. If you select a card with insufficient memory capacity, it may result in performance issues or even failure to run certain models.

4. Cooling requirements

GPUs tend to generate a lot of heat, especially when running intensive workloads. It is crucial to ensure that your server has adequate cooling to prevent overheating and potential hardware damage.

For organizations that heavily rely on AI/ML workloads, Nfina has dedicated AI workstations that may the best option. These workstations are specifically designed for high-performance computing and can accommodate multiple GPUs for even more significant processing power.

Proxmox systems are beginning to incorporate PQC algorithms, such as those that support ML-DSA (Dilithium) signatures, to defend against potential breaches of traditional RSA/ECC encryption. Emerging post-quantum cryptographic (PQC) standards and tools like  wolfCLU are being introduced to enhance security, specifically targeting vulnerabilities like “harvest now, decrypt later”

Post-migration Validation Checklist: 

To ensure a smooth migration process, it is important to run a post-migration validation checklist. This will help identify any issues or discrepancies that may have been missed during the migration process. Some key points to consider in this checklist are: 
 
– Verify network connectivity between VMs and external resources 
– Test storage access and performance 
– Check for any errors or inconsistencies in logs 
– Validate CPU pinning settings for proper resource allocation 
– Perform stress tests on critical components like storage and networking