Move a Virtual Machine in Oracle VirtualBox

Learn how to safely move an Oracle VirtualBox virtual machine to another folder or computer, register its .vbox file, check compatibility, and test the relocated VM.

Moving an Oracle VirtualBox virtual machine (VM) means relocating the files that define and store the virtual computer. You can move it to another folder on the same host system, or transfer it to a different physical computer.

The host system is the physical computer and operating system running VirtualBox. The guest operating system is the operating system installed inside the VM. A VM usually includes a configuration file, virtual disks, logs, snapshots, and saved-state data. Keeping all required files together preserves the VM's settings and disk contents.

Moving a VM within one computer versus transferring it

A local move changes the VM's folder on the same host, such as moving C:\VM\Windows7 to C:\VM2\Windows7. A transfer copies the VM files to another computer, possibly with a different host operating system or hardware.

The file operation is similar in both cases, but a cross-computer transfer requires additional compatibility checks. CPU architecture, hardware virtualization, available memory, VirtualBox versions, networking, display settings, USB devices, and shared-folder paths can all affect the result.

Check compatibility before the move

Before copying files, verify that the destination host can run the guest operating system and the VM's configured architecture. A 64-bit guest normally requires a host with compatible 64-bit CPU support and available hardware virtualization. Hardware virtualization is a processor feature that helps VirtualBox run guest operating systems efficiently.

A guest that is 32-bit-capable can generally run on a compatible 64-bit host. The reverse is not generally true: a 64-bit guest cannot be moved successfully to a host that cannot support 64-bit virtualization. Virtualization support may also be disabled in the destination host's firmware.

Source and destination condition	Expected outcome	Reason or required check
32-bit-capable guest moved to a compatible 64-bit host	Usually supported	Confirm that VirtualBox and the destination hardware support the guest.
64-bit guest moved to a compatible 64-bit host	Usually supported	Check CPU support, hardware virtualization, memory, and VirtualBox compatibility.
64-bit guest moved to a host without 64-bit virtualization support	Unsupported or unable to start	Use a suitable 64-bit host and enable supported virtualization features where applicable.
Hosts with substantially different hardware, operating systems, or VirtualBox versions	May require adjustments	Review drivers, networking, display, USB, shared folders, and saved-state compatibility.

Install a compatible, preferably current, VirtualBox release on the destination host before opening the VM. Avoid relying on a saved state created by a substantially different host. A clean shutdown is safer because a saved state contains host-dependent runtime information.

For broader installation and system checks, see VirtualBox system requirements and the guides for installing VirtualBox on Windows or installing VirtualBox on Linux.

Locate and inventory the VM files

The VM directory is the folder containing the VM configuration and often its disks, logs, and snapshots. Find this directory in VirtualBox Manager or by inspecting the VM's storage and settings before copying anything.

The primary .vbox file is the VirtualBox machine configuration file. It describes the VM's virtual hardware and attached resources. Opening this file at the destination lets VirtualBox recognize the existing machine instead of creating a new empty VM.

File or resource	Purpose	Usually located in VM folder	Action before relocation
`.vbox` configuration file	Defines the VM and its virtual hardware	Yes	Copy it and use the destination copy to register the VM.
Virtual disk files such as VDI, VMDK, and VHD	Store the guest's virtual hard-drive contents	Often	Locate and copy every attached disk, including externally stored disks.
Snapshot and differencing-disk files	Store snapshot-dependent changes	Often in a snapshot subfolder	Copy the complete snapshot structure without renaming or omitting files.
Saved-state files	Store suspended runtime state	Sometimes	Prefer a full power-off; discard or avoid transferring saved-state data when hosts differ.
Logs	Record VM activity and assist troubleshooting	Often	Copying is useful but logs are not normally required to boot the VM.
External ISO images or attached media	Provide optical-media content	Not necessarily	Record the path and copy or reattach the media on the destination.
External virtual disks	Provide storage outside the main VM folder	No	Copy them separately and restore the expected path or update the attachment.

Do not assume that every dependency is inside the main directory. A VM may reference an ISO image, virtual disk, shared folder, USB resource, or other path on the source host. Folder-only copying can therefore produce missing-file errors.

Prepare the VM for relocation

Shut down the guest operating system normally.
Confirm that VirtualBox Manager shows the VM as Powered Off, not Saved, Paused, or running.
Close applications that might be accessing the VM files and wait for all disk activity to finish.
Inventory the configuration file, virtual disks, snapshots, external media, and other dependencies.
Create a backup or retain the original VM until the copied VM has been tested.

A full power-off writes the guest's file systems and avoids carrying a runtime state between different hosts. A saved state is not equivalent to a clean shutdown; it is a suspended memory and device state that may fail to resume after hardware or VirtualBox changes.

Copy the complete VM folder

Copy the entire VM directory to the destination rather than selecting only the apparent main disk. This approach preserves the configuration, logs, snapshots, and expected file relationships.

For example, a Windows 7 VM can be copied from:

C:\VM\Windows7

to:

C:\VM2\Windows7

The same principle applies when copying to another local disk, removable media, a network location, or another computer. When transferring between computers, copy every externally stored disk or media dependency as well. Wait until the copy operation completes, then verify that the destination contains the expected files and that their sizes are plausible.

Copy first and test the destination copy before deleting the source. If the transfer is interrupted or a dependency was missed, the original remains available for recovery.

Open or register the VM at its new location

Start VirtualBox Manager on the destination host.
Open or double-click the copied .vbox file in the destination folder.
Allow VirtualBox to add the existing machine to its list.
Confirm that the VM appears in VirtualBox Manager with its expected name and settings.
Open the VM's storage settings and check that every virtual disk is attached and resolves to an existing file.

Opening the destination .vbox file registers the existing VM. Do not choose to create a new VM unless you intentionally want a separate machine with new configuration and storage.

Validate the relocated VM

Start the VM and verify that the guest operating system boots normally. Then test the resources most likely to depend on the destination host.

Confirm that the expected virtual disks and controllers are attached.
Check that snapshots are listed and usable if the VM had snapshots.
Test network connectivity and review the selected network mode.
Check display settings, USB devices, and shared-folder mappings.
On a different host, check guest activation, drivers, device detection, and operating-system stability.
Verify that attached ISO images and other removable media resolve to valid destination paths.

For related configuration, see VirtualBox virtual disks, VirtualBox snapshots, VirtualBox networking, and VirtualBox Guest Additions.

Relocation checklist

Stage	Required action	Validation
Before copy	Power off the VM, identify the VM directory, and inventory external dependencies.	VirtualBox shows a powered-off VM and all required files are known.
During copy	Copy the complete folder and any external disks or media.	The transfer finishes without errors and destination files are present.
Registration	Open the destination `.vbox` file.	The existing VM appears in VirtualBox Manager and storage paths resolve.
Post-move testing	Boot the guest and test disks, snapshots, networking, display, drivers, and shared folders.	The guest operates normally on the destination host.
Source cleanup	Delete the original only after successful testing.	A verified destination copy and a fallback backup are available.

Snapshots, saved states, and migration cautions

A snapshot is a restore point that may use differencing disks and metadata in addition to the base virtual disk. Snapshot files depend on one another in a specific relationship. Copy all snapshot and differencing-disk files with the original directory structure; do not manually separate a parent disk from its dependent snapshot disks.

Externally located disks or media can cause missing-file errors even when the main VM folder was copied correctly. Host changes can also expose CPU, virtualization, driver, network, display, and VirtualBox-version incompatibilities. Never move files while the VM is running, paused, or in a saved state.

Troubleshoot common move failures

VirtualBox reports that a disk image cannot be found

The disk may have been outside the VM folder, or its path or file name may have changed. Locate the missing disk, restore the expected structure, or update the VM's storage attachment to the new path. If snapshots exist, confirm that every related differencing disk is also available.

The VM will not start as a 64-bit machine

Check that the destination CPU supports 64-bit virtualization and that hardware virtualization is enabled where applicable. A host without the required architecture or virtualization support cannot run the configured 64-bit guest normally.

The VM behaves unexpectedly after transfer

Confirm that the guest was fully powered off rather than saved. Review the VM configuration, install a compatible VirtualBox version, and check display, network, USB, and shared-folder settings. Significant host hardware differences can require guest driver or activation changes.

Snapshots are missing or unusable

Restore the complete original VM and snapshot directory structure. Missing snapshot metadata or differencing disks, altered file names, and manually separated parent disks can break the snapshot chain.

An ISO or shared folder is unavailable

The configuration may reference a path that exists only on the source host. Reattach the ISO from a valid destination path and recreate or update shared-folder mappings for the new host.

Key exam and practice notes

The .vbox file registers and opens an existing VM; it does not contain the guest's complete disk contents by itself.
Copy all required disks, snapshot files, and metadata together.
A clean power-off is safer than transferring a saved state.
A 64-bit guest needs a destination host with compatible 64-bit virtualization support.
Test the copied VM before deleting the original.