A physical-to-virtual migration, or P2V, turns a running Windows PC into a virtual disk that can boot inside VMware, VirtualBox, or Hyper-V. The whole installation, including programs and settings, is captured before the hardware changes underneath it.
This guide explains when P2V is useful, which virtual disk format to choose, and how to create the image of a physical system and run it in a VM.
P2V is worth it when the software on the PC is harder to reinstall than the operating system itself. If the machine runs only fresh apps, a clean VM install is simpler than a conversion.

Most modern hypervisors can read more than one format, so the choice matters less than it used to. When in doubt, create the image first and convert it to the exact format the host software needs.

Windows installs drivers for the physical hardware it detects. Inside the VM, those drivers do not match the virtual devices, so the first boot may take longer while Windows re-enumerates the hardware.
Qiling Disk Master captures a sector image of the physical system disk, including the EFI and recovery partitions that the VM needs to start. Save the image to a drive that the host machine can access.
Watch the video tutorial below to clone the drive step by step with Qiling Disk Master.
Step 1. Open Qiling Disk Master, choose Clone, and then select Disk Clone.

Step 2. Select the physical system disk as the source and click Next.

Step 3. Choose a disk or an image file as the destination and confirm that its data will be replaced.

Step 4. Keep the EFI and recovery partitions, and confirm that the boot volume is included in the image.

Step 5. Click Proceed, wait for the image to finish, then convert it to VHDX, VMDK, or VDI for the hypervisor.

If Windows stops with a boot error, the firmware mode usually does not match the disk style. Switch the VM between UEFI and BIOS and try again.
Yes. A P2V image copies the whole installation, so Windows and all programs start inside the VM.
Use VMDK. VMware products boot VMDK disks natively without conversion.
Not always. A digital licence tied to the hardware may not match the virtual hardware, so reactivation can be needed.
The storage controller mode usually does not match. Switch the VM disk controller to AHCI or SCSI and try again.
For testing, yes. Do not connect both to the same network with the same name and address, or they will conflict.
Capturing a physical system carries risk, and a faulty image can leave the VM unbootable. Create a full backup of the source first, so a failed conversion costs nothing but time.
Watch the video tutorial below to back up Windows and restore it if the clone fails.
Step 1. Open Qiling Disk Master and select System Backup to include the boot partitions.

Step 2. Save the image to a drive other than the target disk and start the backup.

Step 3. Click Proceed to start the system backup and wait patiently until it finishes. You can also tick Shut down the computer when the operation is completed to power off automatically.

Step 4. If the VM will not start, restore the image to the physical drive and adjust the firmware mode.

A P2V migration captures the whole Windows installation and runs it under a hypervisor. Choose a virtual disk format that the target software boots, create a clean image of the physical disk, convert it if needed, and build a VM whose firmware matches the source disk style. Then install guest additions for drivers and performance.
For more on moving Windows to new hardware, see How to Migrate Windows 10 from One PC to Another, How to Clone a VM Disk to a Physical Drive, How to Migrate OS to SSD Without Reinstalling Windows, and How to Clone a Windows Server System Disk.