About migration
About this topic
This topic provides an overview of the Migration Wizard for upgraded VWorks 12.3, 13.0, or 13.1.x installations.
This topic is not applicable if you are upgrading from VWorks 14.0.
When to use the Migration Wizard
You can use the Migration Wizard if VWorks 14.1 or later version is installed on a computer where you uninstalled a previous version of the VWorks software, including VWorks 12.3, 13.0, or 13.1.x and you want to migrate all the VWorks files and records.
Note: Even though you must uninstall any previous VWorks versions before installing VWorks 14.1, the files and records created by VWorks 12.3, 13.0, or 13.1.x remain on the hard drive of the computer and are accessible by the Migration Wizard.
The Migration Wizard migrates all the files and records at one time. After you select a runset or protocol to migrate in the Migration Wizard, the wizard automatically selects all VWorks records found on the computer by default, including device files, labware entries, liquid classes, and so forth.
You can use the VWorks Export (.vzp file) and Import features instead of the Migration Wizard to transfer any protocols and their associated files in the following situations:
• If the computer did not have a previous VWorks version installed
• You want to transfer only a few records
How the Migration Wizard works
In the wizard, you select the runset, protocol, or form files you want to migrate, and the software automatically locates any additional records associated with the selected files (dependencies). For example, if you migrate a protocol, the wizard looks for a device file, form file, inventory file, and so forth. If any of these records are missing, the protocol will not be migrated.
Previous versions of the VWorks software stored some records in the Windows Registry. The migration process copies these records from the Windows Registry into files in the Shared Services storage repository.
The following table shows all the files types that are migrated and their associated records.
Table VWorks records and record dependencies
File or record type | Associated records (dependencies) |
|---|---|
Protocol file (.pro) | Device file (.dev) |
Form file | |
Device profile | |
Inventory file | |
Labware entry | |
Labware class | |
Liquid class | |
Pipetting technique | |
HitPick format file | |
Form file (.VWForm) | Protocol file |
Runset file | |
Device file | |
Form file | |
Form icon and image files | |
Device file (.dev) | Device profile |
Device profile | Teach point file (BenchCel Microplate Handler only) |
Runset file (.rst) | Protocol files |
Labware entries | Labware image |
Labware classes | Labware entries |
Liquid classes | none |
Pipetting techniques | none |
Macro library (.mlb) | none |
Error library (.elb) | none |
External files (.js, .sql, .xls, xlsm, HitPick format files) | none |
Global options | none |
Devices supported in migration
If your device files contain profiles for an unsupported device, the profile for that device will not be migrated in the migration process.Device type | Description |
|---|---|
Labware-handling devices | • Agilent Benchcel • Agilent Centrifuge • Agilent Centrifuge Loader • Agilent Labware Minihub • Agilent Microplate Labeler • Agilent Microscan Barcode Reader • Agilent PlateLoc • BioTek Gen5 Reader |
Liquid-handling devices | Agilent Bravo BioTek Liquid Handler |
Phantom devices | Virtual devices that permit the manual movement of labware during a protocol run: • Agilent Phantom Human Robot • Agilent Phantom Stacker |
Location devices | Devices where you can place a piece of labware: • Platepad (installed outside of Bravo Platform) • Waste Bin |
Devices for manufacturing use only | Agilent Generic I/O Module Agilent Generic RS-232 Device |
Related information
For information about... | See... |
|---|---|
Exporting and importing protocols files | |
Backing up and restoring | |
Setting up the VWorks software |