1. VSS Converter cannot migrate subfolders in a Visual SourceSafe database that contain files older than their parent folders.
Details: VSSConverter cannot migrate subfolders in a Visual SourceSafe database that contains older files that were restored from an archive creating files that predate their parent folders. VSSConverter works in chronological order and cannot migrate files in this condition because the parent folders are not created before the files they contain. Move or rename operations can make the problem worse.
2. VSS Converter cannot migrate files and folders that have name collisions caused by imprecise time stamping.
Details: In Visual SourceSafe, time stamps are recorded to the nearest second. Sometimes, a file or folder operation may have occurred within milliseconds that resulted in what appears to be a name collision based on the recorded time stamp when in fact the events occurred sequentially. When VSSConverter tries to re-create the sequence of events, it encounters the naming collision that did not actually occur in Visual SourceSafe because it tries to perform the operation at the same time.
3. Visual SourceSafe folders that have been moved and renamed many times may not migrate correctly.
Details: When a Visual SourceSafe folder has been moved or renamed many times, VSSConverter may not be able to determine the current name of the folder. Such folders, and their contents, are not migrated correctly. In the migration report, you will see the following errors: "The item already exists." and "The item could not be found in workspace."
4. VSS Converter does not migrate source control bindings.
Details: Visual Source Safe Converter does not migrate source control bindings for Visual Studio solutions. You may receive error messages related to source control bindings when you open a Visual Studio solution after migration.
Workaround: After migrating a Visual SourceSafe database, you must manually change the source control bindings for each Visual Studio solution that was migrated. For more information about manually migrating source control bindings, see the latest version of the Team Foundation Administrator’s Guide that is available on the Web at the MSDN Online site (http://go.microsoft.com/fwlink/?linkid=52459).
5. VSS Converter appends incorrect time stamp to the comment of a migrated changeset.
Details: VSS Converter combines multiple actions into a single changeset to improve the migration performance. The time stamp for the changeset is incorrect.
6. In some scenarios, VSS Converter cannot migrate the version history of file and folders correctly.
Details: In some scenarios, VSS Converter cannot migrate the version history of files and folders correctly. When migration is complete, VSS Converter performs an additional step to affix the latest version, PINNED, and Pinned_Latest label on Team Foundation. When mismatch fixing, you may not see any output (feedback) in the console and the VSS Converter may appear to have stopped working. This is not an indication that anything is wrong and is expected behavior. After migration, the history of files that are fixed may be incorrect. Also, you may see empty folders in Source Control Explorer caused by the mismatch fix process. The summary of the mismatch fix process can be found in summary section of migration report.