Use Export/Import when you need a portable appliance or want to move a VM to another host; use a full clone for an independent second VM; and use a linked clone only when the original VM and its disks will remain available. VirtualBox exports an appliance in OVF format (or as a single OVA archive), imports that appliance on another installation, and can clone a VM directly. Stop the guest before cloning, plan for enough storage for compressed and unpacked disk images, and review the MAC-address policy before putting the copy on a network.
Choose the right VirtualBox operation
Export/import and cloning solve related but different problems. An export packages a VM as an appliance that can be transported, archived, or distributed. Import reconstructs a local VM from that appliance. Cloning creates another VM directly from an existing VM in the VirtualBox environment.
As an Amazon Associate I earn from qualifying purchases.
| Operation | Best use | Relationship to the source | Disk and snapshot behavior | Typical destination |
|---|---|---|---|---|
| Export, then import | Move a VM to another host, create a portable appliance, or hand a ready-to-import VM to someone else | The exported appliance is transportable; the imported VM is a separate local VM | Exports disk images as appliance contents; snapshot history is not represented and the current state is flattened | Another computer, another VirtualBox installation, or an archive drive |
| Full clone | Create an independent second VM for testing, a lab, or a separate workload | Copies the dependent disk images, so the clone can run without the source | Uses more storage than a linked clone; with snapshots, you choose which part of the snapshot tree to clone | Usually the same host, although the resulting VM can be moved later |
| Linked clone | Save space when making a short-lived test or development copy | Depends on the source disks and therefore on the source VM remaining available | Creates differencing disks; deleting, moving, or otherwise breaking access to the source can make the clone unusable | Normally the same host and storage environment as the source |
If the original computer may be wiped, sold, or disconnected, do not choose a linked clone as your only copy. Export an appliance or make a full clone first.
Free tools Windows power users keep installed
One-click scans. No signup required.
Prepare the VM and storage
Power the guest off cleanly
Shut down the operating system inside the guest and wait until VirtualBox shows the VM as powered off. Do not export or clone a VM while it is running. A clean shutdown reduces the chance of an inconsistent guest filesystem and is required for the cloning workflow documented by Oracle.
#1 Best Overall
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
Keep the source until the copy is verified
Treat the original VM as your recovery copy. Do not delete it immediately after an export, import, or full clone. First boot the new VM, confirm that its virtual disks and applications work, and inspect its network identity. Keep the source until those checks are complete.
Reserve working space
Exports can include compressed VMDK disk images, and imports must unpack and copy those images into the destination VM. The destination therefore needs room for the appliance file or OVF output, the resulting virtual disks, and temporary or unpacked data created during processing. Large operations can take several minutes. If the internal disk is tight, a suitably sized external SSD is a practical way to hold an OVA or the exported OVF directory; capacity depends on the source VM and the amount of free space required during import.
Decide what should happen to network identity
VirtualBox normally generates new MAC addresses for cloned adapters and reinitializes network-card MAC addresses during import. That is the safer choice when the original and copy might be connected to the same network. Preserve an original address only when your network design explicitly requires it and you have ensured that no two active machines will use the same address.
Export a VM with VirtualBox Manager
The graphical workflow creates either an OVF appliance or an OVA archive. OVF is a cross-platform appliance format. OVA is the single-file archive variant, which is convenient when you want to copy one file rather than a directory of appliance files.
- Start VirtualBox Manager and make sure the guest is fully powered off.
- Open File > Export Appliance.
- On the Virtual Machines page, select one or more VMs and click Next.
- Choose the output destination and format. Select OVF when you want the appliance represented as its component files, or OVA when a single archive is easier to transport. The format settings also expose controls for MAC-address handling, manifest creation, and optional ISO inclusion.
- Review Appliance Settings. You can edit the appliance name and product, vendor, and license metadata that will travel with it.
- Confirm the destination has enough free space for the appliance and any processing overhead.
- Click Finish and wait for the operation to complete. Oracle notes that exporting can take several minutes, especially for large virtual disks.
An OVF export may produce a descriptor plus disk-image files and other appliance data. An OVA packages the appliance into one archive. In either case, copy every file produced by the export if you chose OVF; moving only the descriptor without its referenced disks will leave the appliance incomplete.
Rank #2
- Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance may be lower depending on host device, interface, usage conditions and other factors. 1MB=1,000,000 bytes.)
- Back up your content and memories on a storage solution that fits seamlessly into your mobile lifestyle.
- Take it with you on your adventures—up to two-meter drop protection means this durable drive can take a beating. (Based on internal testing.)
- Secure it to your belt loop or backpack for extra peace of mind thanks to the tough rubber hook.
- From Sandisk, a brand professional photographers trust to take on assignments.
Export from the command line
For scripted jobs or a headless host, use the documented VBoxManage export pattern:
VBoxManage export <machines> --output=<name>The output can be OVF, OVA, or a gzip-compressed ZIP. Export options include the OVF version, manifest generation, ISO inclusion, and MAC-address handling. Replace <machines> with the VM name or names recognized by VirtualBox and choose an output name with the appropriate extension. The export directory stores compressed VMDK images, so check free space before starting and do not interrupt the process unless you are prepared to discard the incomplete output.
Import an OVF or OVA
Import recreates local VirtualBox VMs from an appliance’s settings and disk images. Because compressed VMDK files are unpacked and copied, importing can take several minutes and may require more free space than the source appliance alone appears to occupy.
- Open VirtualBox Manager and choose Home > Import. Select the OVF descriptor or OVA archive. If file associations are installed, you can also double-click the appliance in the host file manager.
- Review Appliance Settings. Change the VM’s name, CPU or memory allocation, storage location, or other available settings to fit the destination host.
- Check the base folder. This determines where VirtualBox creates the imported VM and its files.
- Review MAC Address Policy. Leave the normal reinitialization behavior when the imported VM will coexist with the source or another copy. Use a preserved address only when you have a deliberate network plan.
- Decide whether to import hard drives as VDI instead of the default VMDK. VDI can be useful when you want the imported disks in VirtualBox’s native disk format; retaining VMDK may be preferable when compatibility with the appliance’s existing disk format matters.
- Click Finish and wait while VirtualBox copies the disk images and creates the VM.
When the import completes, the VM appears in the Manager on the selected host. Keep the original appliance until the imported VM has booted successfully and you have verified its applications and networking.
Import from the command line
The command-line alternative is VBoxManage import, which reads an OVF appliance and creates VMs from its disk images and settings:
Rank #3
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
VBoxManage import <appliance.ovf>Use the OVF descriptor produced by the export, or point the command at the appliance file in the form supported by your VirtualBox installation. Review the command output for the target VM name, storage path, and any warnings before starting the imported VM.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clone a VM in VirtualBox Manager
Cloning is the direct way to create another VM from an existing one. The source must not be running.
- In VirtualBox Manager, open Machines, select the powered-off source VM, right-click it, and choose Clone.
- Enter the clone’s name and choose its path.
- Review the clone options for MAC-address policy, disk-name retention, and hardware UUID retention. VirtualBox defaults to generating new MAC addresses for all network adapters; keep that safer default when both machines may share a network.
- Select Full Clone or Linked Clone.
- If snapshots exist and you selected Full Clone, choose which part of the snapshot tree to clone. Current Machine State excludes the snapshots; selecting an appropriate snapshot branch includes the corresponding state and disks.
- Start the clone operation and wait for VirtualBox to finish copying or creating the disk files.
When to choose a full clone
A full clone copies the dependent disk images. Once it is complete, the clone can operate without access to the source VM or its disks. This independence makes a full clone the safer choice for a long-lived second installation, an offline archive, a handoff to another administrator, or any situation in which the source may be moved or deleted. The trade-off is storage: the copied disks consume space in addition to the source disks, and the copy may take substantial time for a large VM.
When to choose a linked clone
A linked clone creates differencing disks that record changes relative to the source disks. It is space-efficient and can be created quickly, which is useful for temporary test environments or multiple short-lived labs. Its dependency is also its main risk: the source VM and its disks must remain accessible and structurally intact. Do not use a linked clone as a standalone backup or as the only copy you plan to move to another computer.
Snapshots, flattened exports, and VM identity
What happens to snapshots during export
OVF cannot describe snapshots. If the source VM has snapshots, exporting it does not preserve the snapshot history as a navigable tree. The appliance represents the current state with flattened disk images. Before exporting, decide whether the current state is the one you want to transport; an imported appliance will not give you the original snapshot checkpoints to browse or revert to.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #4
- NEARLY 2X FASTER THAN OUR PREVIOUS GENERATION(8) – move 1,000 high-res photos in under 60 seconds(6) with up to 2000MB/s transfer speeds(2).
- IP65 RATING AND UP TO 3M DROP PROTECTION(3) – protects against spills and drops.
- POCKET-SIZED – fits easily in pockets and small bags.
- SPACE TO OWN YOUR AI CONTENT – speed and capacity to download your high-res clips and photo edits.
- 256-BIT AES ENCRYPTION(4) – helps keep private files secure with password protection.
Why MAC addresses and UUIDs matter
A VM’s network adapter identity can affect DHCP leases, static reservations, licensing systems, firewall rules, and guest operating-system interface naming. Imports normally reinitialize MAC addresses, while clones normally receive new addresses. Retaining an address can be appropriate for a deliberate replacement where the old machine is permanently retired, but duplicating an active address can cause intermittent connectivity and confusing ARP or DHCP behavior. Hardware UUID retention is another clone option; review it when software inside the guest identifies the machine by UUID.
Move a VM to another computer: a safe workflow
For a host-to-host migration, export/import is usually clearer than copying a collection of VirtualBox files manually because the appliance carries the VM’s settings and disk references together.
- On the source computer, shut down the guest and note its current CPU, memory, storage, and network requirements.
- Export it as OVA for one-file transport, or as OVF when you need the appliance’s separate files and format controls.
- Copy the complete OVA or the complete OVF output set to the destination. Verify that the transfer completed before deleting the source copy.
- On the destination, open Home > Import and select the appliance.
- Choose a destination base folder with enough room for the unpacked disks and future snapshots or saved states.
- Review hardware settings and the MAC Address Policy. Adjust resources to the new host rather than assuming the destination has identical capacity.
- Import the appliance, then boot the VM with the network adapter disconnected if you need to prevent an unverified duplicate from appearing on the production network.
- Check the guest’s boot process, disk visibility, applications, time settings, and network configuration. Reconnect networking only after confirming the new MAC address and any DHCP or static configuration are correct.
- Keep the original VM and appliance until the migrated copy has passed these checks.
How to verify an imported or cloned VM
- Boot: Confirm the guest reaches its normal login or service state without disk or bootloader errors.
- Storage: Check that every expected virtual disk is attached and that the guest sees its filesystems at the expected capacity.
- Applications: Open the critical application or service and perform a safe read/write test appropriate to that workload.
- Network identity: Inspect the adapter’s MAC address and verify that it does not conflict with the source or another machine. Check DHCP leases, static settings, hostnames, and firewall rules.
- Integration: Test shared folders, host-only or bridged networking, USB passthrough, and other integrations your VM actually uses.
- Recovery: Confirm that you still have the source VM or appliance until the new copy is accepted. Do not treat a successful import dialog as proof that the guest is fully usable.
Troubleshooting export, import, and clone problems
The export fails for lack of space
Free space must cover the exported appliance, compressed VMDK files, and temporary data. Move the destination to a larger disk, remove unrelated files, or use an external SSD with sufficient capacity. Do not assume that the VM’s apparent used space is the only requirement; the export and later import each perform additional copying.
Import appears stuck
Large VMDK images are unpacked and copied, so progress can be slow even when the interface appears quiet. Check disk activity and available space, allow several minutes, and avoid launching a second import against the same destination. If the operation was interrupted, remove or quarantine the incomplete VM and retry from an intact OVA or complete OVF file set.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteThe imported VM has no network connectivity
First inspect the adapter’s attachment mode and the newly assigned MAC address. A reinitialized address may require a fresh DHCP lease or an update to a static reservation. If the guest operating system retained an old interface configuration, remove or reconfigure that stale entry according to the guest’s own network tools. Do not assign the source’s MAC address while both machines are online.
Best Value
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
A linked clone will not start after the source was moved
That behavior follows the linked clone’s design: its differencing disks refer to the source disks. Restore the source VM and its disks to an accessible location, or create a full clone while the source is available. A linked clone is not a substitute for an independent export or backup.
The imported VM does not contain old snapshots
This is expected. OVF has no representation for snapshot history, so export carries the current state as flattened disks. If separate historical checkpoints are important, retain the original VirtualBox VM and its snapshot files in addition to exporting the current state.
Quick decision checklist
- Need a portable file or a move to another computer? Export as OVA or OVF, then import.
- Need a durable second VM that can outlive the source? Create a full clone.
- Need several temporary copies while keeping storage use low? Create linked clones and preserve the source.
- Need snapshot history on the destination? Do not rely on OVF export; retain the original VM and snapshot data.
- Will source and copy share a network? Use generated, distinct MAC addresses and review guest network settings.
- Working with a large VM? Reserve space for export, unpacking, and the final disks, and expect the operation to take several minutes.
Practical examples
Moving a development VM to a laptop
Power off the development guest, choose File > Export Appliance, select OVA, and save it to storage with enough room. Copy the OVA to the laptop, choose Home > Import, select a suitable base folder, and leave MAC-address reinitialization enabled if the desktop and laptop might both be used. Boot the laptop copy with networking reviewed before reconnecting it to the same network as the original.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Testing a risky update without touching production
With the production VM powered off, choose Clone and select Full Clone. Give the test VM a distinct name and generated MAC address. Boot the clone on an isolated or carefully controlled network, apply the update, and compare application behavior. Because the full clone has its own disks, deleting the test VM does not remove the production disks.
Creating several short-lived training environments
Keep a clean source VM powered off and create linked clones for each trainee or exercise. This minimizes additional disk use, but the source must remain in place for every linked clone. When the training cycle ends, remove the linked clones; if one environment must be kept independently, replace it with a full clone or export it as an appliance.
Quick Recap
Final pre-flight checklist
- Guest is cleanly shut down and shown as powered off.
- Destination storage has room for the appliance, compressed images, temporary work, and the resulting VM.
- Operation matches the goal: export/import for portability, full clone for independence, linked clone for space-efficient temporary work.
- Snapshot expectations are clear: OVF export carries current state, not snapshot history.
- MAC-address and hardware-UUID policies have been reviewed for coexistence and licensing requirements.
- Source VM and appliance are retained until the new VM boots and passes storage, application, and network checks.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
