How to import VDI VirtualBox from Windows 7 to 10 [solved]

[regine]

1. On the same computer 64bit is HDD with Windows 7 and will be SSD with Windows 10.
2. VB 5.1.6 is installed on Windows 7 (HDD)
3. VB 6.1.8 is installed on Windows 10 (SSD)
4. How I must migrate file VDI, PLS step-by step?
5. File VDI with its folder has already been copied.
THX.

I tried according to:
[mod edit]offsite link deleted.
or
[mod edit]offsite link deleted.
but without success (unknowing IT).

I have just exported *.OVA and import appliance. All is OK.

[scottgus1]

While exporting and importing can work, the process changes the VM's UUIDs which can interfere with activation status, etc.

The easiest way to move a Virtualbox VM from one OS to another is to just copy the guest folder over.

A simple file-copy of the completely-shut-down (not save-stated) guest's folder, with the guest .vbox file, Snapshots and Logs folders, and the guest virtual disk file(s), is the best way to copy a guest. The copy can be 'FC' file-compared on local backup media, or hashed for offsite media, to confirm the copies. Note that if the disk file is not in the guest folder next to the guest's .vbox file, the path to the drive file in the .vbox file is absolute, and the full path needs to be duplicated on the new host, or the .vbox file needs to be manually edited. (Not to mention Windows, Linux & Mac paths are not compatible with each other, and I would guess the same about Solaris hosts.) If the guest drive file is in the guest folder with the .vbox file, the path is relative, and the guest can be dropped onto any capable & properly-set-up host, any supported host OS. The guest folder can easily reside on any host drive. Virtualbox 6.0.x and later can easily move the guest folder to the host drive that the guest drive file is on, and then move the drive file into the guest folder so the guest is in optimum format.

[mpack]

Please don't post offsite links to VirtualBox tutorials. Thanks but we don't need any help from offsite blogs. The best sources of information are (a) the user manual, and (b) our own tutorials, which are vetted and kept up to date by experts, often with input from the developers. Plus offsite links have a tendency to break relatively quickly.

In the case of how to move a VM from one place to another, our relevant FAQ has existed for years: Howto: Move a VM.