A Handoff operation examines the latest version of a VSS database, and commits the latest version of each file in the selected VSS project into Vault Standard. It can be thought of as a "shallow import." There are several steps in the Handoff process.
This is the path that will be imported.
The contents of the folder will be imported, not the folder itself. If you wish to import a VSS path $/trunk into an empty Vault Standard repository, as $/trunk, you must first create a $/trunk folder in the Vault Standard repository. In general, if you want the imported paths to match exactly, the path of the imported object in VSS should match the target path in Vault Standard.
Shares under this path will be reestablished only with other shares under this path. For example, if you are importing the VSS path $/trunk to the Vault Standard path $/trunk, a shared item with the links $/trunk/src/file.h and $/trunk/dist/file.h would be established as a Vault Standard shared item. An item with VSS share links $/trunk/src/file.h and $/branch/src/file.h would not be established as a Vault Standard shared item, since $/branch/src/file.h is not included in the import.
The repository where the files will be committed.
The repository folder where the files will be committed.
This step shows progress and errors. To begin the handoff, click the Start Handoff button. Once the handoff operation is complete, the next page will be automatically loaded. Please do not navigate away from this page while a handoff is running.
This will display all errors that were encountered during the handoff operation. Please check these files, and manually add them if necessary.