User`s guide
 Using Parallels Add-Ons 191 
Migration Scenarios 
Parallels Transporter offers you several typical migration scenarios depending on the purpose of 
migration. After you make up your mind and choose the scenario, you can refer to Parallels 
Transporter Help for further instructions on the selected scenario of migration. 
Using Parallels Transporter, you can migrate: 
  from a remote computer 
  from a third-party virtual machine 
  from a remote computer locally 
Parallels Transporter has two migration modes: 
  Express. This mode allows quick migration of one active volume. As a result, you will get a 
ready-to-use Parallels virtual machine which will have the guest operating system installed 
and all the applications and data you used on that volume. 
  Advanced. This mode allows migration of several volumes at once. In one session of 
migration, only one active volume (if selected so) can be made bootable. The new virtual 
machine will be created with this volume as its virtual hard disk. Other volumes will be 
migrated as data disks if they have file systems supported by Parallels Transporter Agent. 
Migrating from a remote computer 
In this scenario, you should use Parallels Transporter on the host computer and Parallels 
Transporter Agent on the PC you want to migrate. 
The volume where Parallels Transporter Agent is installed is called the active volume. The 
operation is supported for the active volumes with the following operating systems: 
  Windows 2000 
  Windows Server 2003 
  Windows XP 
  Windows Vista. 
Parallels Transporter can apply necessary changes only to the listed operating systems so that 
the images of active volumes can be bootable in Parallels virtual machines. 
If you want to use a migrated disk as a boot volume (system disk) in your virtual machine you 
must provide an installation disc for the operating system that runs on the active volume of the 
source computer (you can also use an ISO image of such an installation disc). Parallels 
Transporter may need to reinstall a few drivers, because hardware on the source computer and 
default virtual hardware of a virtual machine are different. 
Warning: If you migrate a volume with a Windows OS installed on it and want to use its 
image as a bootable virtual disk, please note that there may be activation problems: a 
Windows OS migrated to a virtual machine may detect that the hardware has changed and 
require that you reactivate your copy of Windows. 










