Convert VMDK to PVM

A VMware guest must be imported when you are moving it to Parallels Desktop on a Mac without reinstalling its operating system. The resulting PVM package gives Parallels a native container for the guest configuration and virtual disk.

What the VMDK format is

VMDK is VMware’s virtual hard-disk format. VMware Workstation, VMware Fusion, VMware vSphere, and some backup or migration products use it to store a guest operating system, applications, and virtual disk sectors.

A VMDK can be a single monolithic file, a descriptor file with separate extent files, or part of a snapshot-linked disk chain. Keep the descriptor and every referenced extent or snapshot file together. Selecting only one extent can produce an incomplete or unbootable disk.

What the PVM format is

PVM is a Parallels virtual-machine package, usually shown by macOS Finder as a single package or bundle. It contains the VM configuration, virtual disks, hardware settings, snapshots, and Parallels metadata. Unlike VMDK, PVM is not a virtual disk-sector format.

Parallels commonly stores an imported disk inside the package in its own HDD/HDS representation, although the exact files depend on the Parallels Desktop version and import choices. PVM is useful when the destination is Parallels Desktop because the guest configuration and disks can be moved and opened as one package. It does not inherently make the guest smaller.

How to convert VMDK to PVM

Parallels Desktop on macOS is the appropriate conversion tool because it creates the Parallels configuration and converts or incorporates the disk in the same operation. Menu names vary between Parallels Desktop releases.

1. Shut down the VMware guest; do not use a suspended or running VM as the source. Make a backup of the complete VMware VM directory, including the .vmx file, VMDK descriptor, extent files, and snapshots.
2. Install and open Parallels Desktop on the destination Mac.
3. If the complete VMware machine is available, use File → Open or the equivalent import command and select its .vmx file. Importing the VMX preserves more information than selecting a disk alone, including the guest’s virtual hardware, firmware choice, memory, network adapters, and disk references.
4. Follow the import prompts and choose to copy or convert the disk when Parallels offers that choice. Save the new VM in the required location. A copied or converted disk keeps the VMware source unchanged; retaining an external source disk can leave the PVM dependent on files outside the package.
5. If only a VMDK is available, create a new VM in Parallels using the option to continue without an installation source or to use an existing disk. Select the VMDK descriptor, not an extent file, and remove any newly created empty disk if necessary. Configure the guest operating system, firmware, memory, processors, and disk controller before starting it.
6. Start the VM and install or update Parallels Tools. Remove VMware Tools when appropriate; Windows may detect new virtual hardware, request a reboot, and require reactivation.
7. Shut down the guest and verify the generated .pvm package by opening it on the destination Mac. Test multiple boots and check the guest’s files before deleting the VMware backup.

Use the complete VMX-based import for snapshot chains, independent disks, encryption, or several virtual disks. A standalone VMDK does not contain all of the VM’s configuration, and selecting only its current extent can lose snapshot data or make the guest unbootable.

Command-line and online alternatives

qemu-img can convert VMDK to raw, QCOW2, VDI, and other virtual-disk formats, but it does not create a valid PVM package or Parallels VM configuration. It is useful only for an intermediate disk conversion when Parallels cannot read the source directly. Renaming .vmdk to .pvm changes no data and cannot work.

There is no generally suitable reputable online converter for this task. A PVM may contain many gigabytes of private guest data, and web services typically do not produce a bootable Parallels package with correct hardware settings. Convert locally with Parallels Desktop; avoid uploading the source unless a service explicitly supports complete VMware-to-Parallels VM migration and meets the required privacy and size constraints.

Compatibility and quality limits

The guest operating system must be supported by the installed Parallels Desktop version and the Mac’s processor architecture. An Intel VMware guest may not run directly on an Apple silicon Mac: x86 operating systems need a compatible virtualization or emulation path, and an ARM guest may need an ARM-compatible operating-system image.

Match the source firmware mode where possible. A UEFI guest may fail to boot when imported as a legacy-BIOS VM, and the reverse can also occur. If the guest reports an inaccessible boot device, check the firmware setting, virtual disk controller, and boot order before repairing its boot loader.

Conversion changes the virtual hardware. VMware-specific drivers, network adapters, hardware identifiers, activation records, and VMware Tools may need removal or reconfiguration. Encrypted VMware disks, unsupported snapshot formats, damaged descriptors, and disks with missing extent files may require repair or export from VMware before Parallels can import them.