VMware vCenter Converter is back and more relevant than ever. Learn from our latest article what’s new in Converter Standalone 9.0, including security updates, Linux sync, and automation, and how it complements VMware HCX.
VMware vCenter Converter is a classic VMware tool designed to convert physical and virtual systems into VMware virtual machine (VM) formats. Its origins trace back to the VMware P2V Assistant utility, which existed in the early 2000s to support “Physical-to-Virtual” migrations. In 2007, VMware released the first version of Converter (3.0), replacing P2V Assistant.
Converter was offered both as a free Standalone edition and as an integrated Enterprise Plugin included with VMware vCenter. The integrated version enabled large-scale P2V migrations directly through the vCenter interface, while the Standalone edition functioned as an independent application. In its early stages, Converter primarily supported Windows systems and focused on basic P2V, V2V (Virtual-to-Virtual) migrations and cloning scenarios for backup purposes.
Over the following years, the product evolved through versions 4.x, 5.x, and 6.x, adding support for Linux operating systems and additional hypervisors.
However, after version 6.2 (released in 2018), development effectively stalled. VMware even removed Converter from public availability due to outdated security components. Many in the industry assumed that Converter’s functionality had been superseded by more modern migration tools, such as VMware HCX. Indeed, by 2019, Converter was often described as “largely forgotten,” with its large-scale migration use cases being addressed by VMware HCX Enterprise.
Nevertheless, demand for a straightforward P2V tool persisted, prompting VMware to revive the project. In 2022, the company announced the return of vCenter Converter, releasing an updated version with a strong emphasis on security and compatibility with modern platforms. New releases were numbered 6.3 through 6.6 (2022–2024), followed in 2025 by a major release: Converter Standalone 9.0. This change in versioning aligns the product with the vSphere/VCF 9 lineup and symbolizes a new phase in its development.
Core Functionality
VMware vCenter Converter Standalone automates the process of creating VMware-compatible VMs from a wide range of source systems.
P2V (Physical-to-Virtual) and V2V (Virtual-to-Virtual) Migrations
The primary purpose of the tool is P2V migration – converting physical servers (Windows or Linux) into VMware VMs (vSphere, ESX). In addition, Converter supports V2V conversions from other platforms. Examples include migrating workloads from Microsoft Hyper-V to VMware VMs, converting VMware Workstation or Fusion virtual machines into the vSphere format, and reconfiguring existing VMware VMs.
In practice, Converter can take a “live” virtual server on a third-party hypervisor – or a physical host – and directly convert it into a virtual machine on ESX or vCenter. Powered-off VMs can also be converted to ensure maximum compatibility of the resulting VM.
It is important to note that the product retains the familiar wizard-based workflow well known to administrators. The conversion process is configured step by step: the administrator specifies the source system, the target infrastructure, and the required parameters. For example, the source can be selected as a local machine, a remote physical Windows server, a running Linux server accessed via SSH, a VMware Workstation image, or even a virtual machine hosted on Hyper-V.
The wizard then prompts for the target environment – typically an ESX host or a vCenter cluster, or alternatively, the creation of a VM for VMware Workstation/Fusion. In the final steps, VM parameters are defined, including CPU and memory allocation, disk provisioning type (thin or thick), network connections, and other options.
The entire process is fully automated. Converter installs an agent on the source system if required, transfers disk data, and configures operating system drivers and services. This includes disabling hardware-specific services, installing VMware Tools to ensure proper operation of the virtualized OS, and performing other necessary adjustments.
In the example below, a running remote Windows server is selected as the source. The administrator provides the server’s IP address and credentials, after which Converter automatically deploys an agent on the source system to capture its data and configuration for conversion.
Hot Cloning of Running Servers
As shown, Converter supports “hot cloning” enabling the cloning of running systems without shutting them down. During this process, the source server remains online while data is copied in the background. This approach is convenient for many scenarios, but must be used with caution. For example, hot cloning is not recommended for Active Directory domain controllers or heavily loaded database servers; in such cases, “cold cloning” – conversion while the system is powered off – is preferable to ensure data consistency.
Earlier versions of Converter even provided a dedicated Cold Clone CD (a bootable ISO) for offline migrations. Modern versions, however, focus on hot cloning combined with post-migration synchronization. In version 9.0, support was introduced for synchronizing changes on Linux systems after the initial clone. This feature minimizes downtime during Linux server migrations by transferring only the delta before the final switchover. Similar functionality for Windows systems is planned for future releases.
Product Architecture
From an architectural standpoint, VMware Converter Standalone consists of several core components:
- Converter Server – a service that orchestrates the conversion process and manages communication with both the source and the destination systems.
- Converter Agent – a module installed on the source machine (in P2V scenarios) to capture system data. For remote Windows systems, the agent can be deployed automatically via RPC; for Linux systems, built-in SSH access is used.
- Converter Client – a graphical user interface (console) through which the administrator creates, monitors, and manages conversion jobs.
In a Standalone mode, all components can be installed on a single Windows machine (for example, the administrator’s workstation). In more advanced scenarios, the components can be distributed: for instance, installing the Converter Server on a dedicated host and connecting to it remotely via the Converter Client, which is convenient for team-based operations. The console allows administrators to track migration progress in real time, showing data copy status, source and target system states, and detailed operation logs for troubleshooting.
Use Cases
VMware vCenter Converter is aimed at administrators who need to migrate workloads into a VMware environment on a one-time or recurring basis. Common use cases for Converter Standalone include:
- P2V infrastructure modernization: organizations modernize their hardware by migrating physical servers (Windows or Linux) to the vSphere/VCF virtual platform. Converter enables such migrations relatively quickly and with minimal downtime, making it particularly relevant for server consolidation initiatives and transitions toward a software-defined data center.
- Upgrading legacy VMware or other hypervisors: Converter helps migrate VMs from older ESXi/ESX versions or from other hypervisors (such as Hyper-V, legacy VMware Server, Virtual PC, and similar platforms) to current vSphere releases. For example, multiple Hyper-V VMs can be converted directly into an ESX cluster, with automated VMware Tools installation and Virtual Hardware compatibility adjustments.
- Migration between formats and environments: in addition to enterprise vSphere environments, Converter supports VMware Workstation and Fusion. This is useful for moving test virtual machines from a developer’s laptop (running VMware Workstation) into a production ESX cluster, or conversely exporting a production VM into Workstation format for analysis, troubleshooting, or lab use.
- Backup and disaster recovery (DR): although dedicated backup solutions are widely available today, Converter was originally positioned as a way to clone critical physical servers into virtual machines for disaster recovery. Administrators can periodically create a virtual copy of a physical server and retain it as a standby image. Converter can also quickly clone existing VMware VMs (for example, from an old host to a new one), which can be used to create test copies of production systems or to migrate workloads between clusters that do not share common storage.
- Test labs and DevOps: in large organizations, Converter is valuable for cloning different environments. Before a major application upgrade, for instance, a production server can be converted into an isolated virtual environment for testing while preserving all OS and application configurations. This approach is faster and more cost-effective than rebuilding environments from scratch.
Overall, Converter Standalone serves as a universal “first step” toward virtualization. It is particularly valuable for small and medium-sized businesses (SMBs) that lack expensive replication or migration tools, allowing administrators to independently virtualize legacy physical servers without engaging external consultants. In large enterprise environments, Converter also has its place as a supplementary tool for specific tasks, such as converting standard images, preparing demo environments, or migrating atypical or unmanaged hosts. Importantly, it is available free of charge, making it attractive from a cost-reduction perspective.
Integration into the VMware Infrastructure
As its name suggests, vCenter Converter Standalone operates independently; however, it is tightly integrated with the VMware ecosystem and fits seamlessly into existing operational workflows. Converter supports connections to ESXi/ESX hypervisors and to vCenter Server via standard VMware protocols (HTTPS, NFC), using accounts with permissions to create virtual machines. This allows administrators to specify a vCenter address and the target placement (Datacenter or Resource Pool) directly within the wizard, after which the entire import process is performed automatically.
Converter is aware of VMware-specific environment characteristics. For example, it allows administrators to select the appropriate Virtual Hardware version for the newly created VM to match the ESX version on the target host. Network configuration can also be defined during migration, enabling the new VM to be connected to existing virtual switches and port groups so that it is placed in the correct VLAN immediately after conversion.
Converter does not require vCenter to operate – it can work directly with a standalone ESX host using the host’s IP address and credentials. In enterprise environments, however, vCenter is typically specified so that the new VM is immediately added to the cluster inventory. Integration is performed at the API level: Converter acts as an external vSphere client, similar to backup products, and does not require any plugins to be installed in vCenter. In earlier vCenter 4.x days, a Converter Enterprise plugin existed, but this approach is no longer used; all functionality now resides in the external application. This design simplifies maintenance, as updating Converter has no impact on vCenter operations.
From a deployment perspective, Converter Standalone is typically installed on a Windows machine within the same network as the source and target hosts. Modern Windows versions are supported (for example, Windows 10/11 and Windows Server 2012–2022). The product does not require a separate license – it is free for all users and available for download from the VMware/Broadcom portal.
Following VMware’s acquisition by Broadcom in 2023, support for Converter moved under Broadcom’s umbrella. The current 9.0 release can be downloaded from the Broadcom Support Portal, and it remains free of charge for registered users.
In the version 9.0 interface, updated “VMware by Broadcom” branding is visible, while the overall operating principles remain unchanged. A notable enhancement is the introduction of an automation SDK: starting with version 9.0, a Converter SDK with Python support is available, enabling integration of conversion tasks into scripts and orchestration frameworks. This opens the door for large organizations to automate mass conversions or embed Converter into deployment pipelines.
Finally, it is worth noting Converter’s integration with other VMware tools. While Converter is a task-focused utility, its outputs are frequently used in conjunction with backup solutions (for example, a converted VM can subsequently be replicated using Veeam or VMware Site Recovery Manager for DR) or with cloud services (a local machine can be converted and then uploaded to VMware Cloud on AWS). VMware positions Converter as part of the broader vSphere ecosystem, simplifying the onboarding of virtually any workload onto its platform.
What’s New in Version 9.0
The latest release, VMware vCenter Converter Standalone 9.0, introduces a number of enhancements relevant to modern IT environments. The key improvements in this release include:
- Support for new platforms: compatibility with VMware Cloud Foundation 9.0 and related solutions has been added. Converter 9.0 supports the latest vSphere versions (7.x, 8.x, 9.x, and later) and Virtual Hardware Version 22. This ensures proper support for the newest CPU generations, chipsets, and VM capabilities released by VMware.
- Security enhancements: full SSL certificate support has been introduced. Administrators can now use their own signed certificates for secure connections between Converter and target hosts, improving compliance with enterprise security policies. Previously, users had to rely on Converter’s self-signed certificates; integration with third-party certificate authorities is now significantly simplified. The overall architecture has also been reworked with a strong focus on eliminating vulnerabilities, addressing concerns raised about older versions.
- Linux post-P2V synchronization: as mentioned earlier, incremental synchronization for Linux systems is now available. After the initial hot clone, the synchronization task can be rerun, and Converter will copy the changes accumulated on the source server before the final cutover to the virtual machine. This capability is particularly important for migrating active Linux servers with minimal downtime.
- SDK and automation: Converter 9.0 includes an SDK with Python support, making it easier to develop scripts for managing conversion tasks. Administrators can now programmatically create and control conversion jobs, integrate the process into CI/CD pipelines, or embed it into corporate self-service portals. Automation was previously limited; Converter is now a fully programmable service.
- File system improvements: for Linux sources, Converter now preserves specific XFS file system flags (CRC and ftype) during migration, which is critical for data integrity on modern Linux distributions. For example, when migrating CentOS or Red Hat systems using XFS volumes, the target virtual machine retains all required file system attributes.
- User interface updates: icons and GUI elements have been visually refreshed and aligned with the new VMware/Broadcom branding. The interface remains the familiar wizard-based workflow known to long-time users, but with a more modern appearance. Overall stability has also been improved, with the development team focusing on bug fixes, more reliable data transfer, and broader operating system compatibility.
It is important to emphasize that version 9.0 restores official support for Converter from VMware (Broadcom). The product is once again part of the active portfolio and receives updates. For enterprise administrators, this signals that VMware continues to see value in this tool and intends to develop it further, addressing gaps not covered by other solutions.
Relationship with VMware HCX: Similarities and Differences
VMware administrators naturally question how VMware vCenter Converter relates to VMware HCX (Hybrid Cloud Extension), as both tools address VMs migration. However, they are designed for different scales and scenarios, complementing rather than directly replacing each other.
VMware HCX is a platform for large-scale migrations and application mobility in hybrid cloud environments. HCX is deployed as a set of services on both source and destination sites and enables the migration of dozens or hundreds of virtual machines with minimal or zero downtime, while maintaining network connectivity between locations. Its primary use cases include data center migrations and hybrid cloud integration: for example, moving entire VM pools from a private data center to VMware-based public clouds, migrating workloads between different vSphere versions, or balancing resources across sites.
To achieve this, HCX leverages WAN optimization, replication technologies, and Layer 2 network extension between sites. Importantly, HCX supports “Any-to-Any” migrations, including from non-VMware environments such as KVM and Hyper-V, and even from physical servers. The latter is enabled through the OS Assisted Migration (OSAM) component. In simple terms, HCX can perform everything that Converter does – and more – but within the context of a comprehensive, service-based platform intended for large-scale projects.
The primary similarity between Converter and HCX is that both address the migration of workloads onto the VMware platform. The key difference lies in scope and scale: Converter is typically used for one-off, targeted migrations, while HCX is designed for continuous, large-scale operations. For example, if the task is to migrate five physical servers into virtual machines, Converter Standalone is the optimal choice. It is free, easy to use, and requires minimal preparation – install it on a laptop and run the wizard.
By contrast, when migrating hundreds of VMs between geographically distributed data centers or into the cloud with minimal downtime, VMware HCX is the preferred solution. HCX is deployed as part of the cloud infrastructure (for example, integrated into VMware Cloud Foundation and VMware Cloud on AWS) and provides capabilities such as cross-site vMotion, bulk migration workflows, and built-in replication for near-zero-downtime migrations.
There is also functional overlap. HCX Enterprise includes OS Assisted Migration, which is effectively a P2V-like mechanism for systems that are not native vSphere virtual machines. Using OSAM, third-party systems, such as Hyper-V VMs or physical servers, can be migrated into a VMware environment by installing an agent (Sentinel) in the guest OS, in a manner very similar to how vCenter Converter operates. In this sense, both tools can perform comparable actions, but HCX does so as part of a broader hybrid cloud strategy and typically requires an Enterprise license.
Moreover, HCX is designed for long-term coexistence between sites. It not only migrates virtual machines but can also maintain synchronization, provide network connectivity through Layer 2 stretching, and even participate in disaster recovery strategies when combined with VMware Site Recovery Manager (SRM). Converter, on the other hand, is a point-in-time conversion utility: once the migration is complete, there is no ongoing relationship between the source and target systems, aside from the final delta synchronization step.
When Should You Use vCenter Converter and When HCX?
If the requirement is to migrate a small number of physical machines or convert individual virtual machines outside the scope of a large project, vCenter Converter Standalone is the clear choice. It is simple to deploy, does not require complex network preparation, and is ideal for scenarios such as “bringing into vSphere workloads that were not previously running on VMware.”
Conversely, if an organization is undertaking a large-scale infrastructure migration, such as decommissioning an old data center and moving all workloads to a new private cloud or to VMware Cloud on AWS, HCX becomes essential. HCX provides automation, migration scheduling, network address preservation (via Stretch Network), and minimal application downtime through background replication and live migration capabilities.
Cost and resource considerations also differ significantly. Converter is free of charge but requires more manual effort and typically operates on a per-VM basis. HCX is a licensed solution (included in Enterprise Plus editions or certain cloud offerings) and requires the deployment of multiple appliances, but it dramatically reduces time and effort for large migrations. In practice, organizations often use both tools: Converter for preparing individual systems or addressing specific tasks (for example, importing legacy images), and HCX for the main wave of migrations involving standard virtual machines. As a result, vCenter Converter Standalone and VMware HCX are not so much competitors as tools operating at different levels, each finding its place within an organization’s migration and IT infrastructure modernization strategy.
Summary
VMware vCenter Converter Standalone remains a valuable, task-oriented utility for targeted conversion of physical and virtual machines into the VMware format. The latest 9.0 release has restored the tool’s relevance by adding support for modern operating systems and platforms, strengthening security, and improving usability. At the same time, VMware HCX addresses complex migration scenarios, providing a powerful solution for hybrid cloud environments and large-scale VM mobility with minimal downtime.
By understanding the strengths of each tool, enterprise administrators can select the most appropriate approach – from a single P2V conversion using Converter to multi-stage data center migrations using HCX, or a combination of both – to fully address their infrastructure migration and modernization requirements.
from StarWind Blog https://ift.tt/XV94dI3
via IFTTT
No comments:
Post a Comment