Interpreting the Source Control Migration Report
You can view the source control Migration Report using a Web browser. The report is generated as an XML file, and the supporting files, such as .XSLT and graphic files, are used to display these files to the user.
The report is divided into sections and some sections are divided into subsections. The Error and Warning sections appear only if there were errors or warnings encountered during migration. Each section of the report is collapsible. You can click the icon in the section head to expand or collapse a section.
Most of the sections and content is the same for both the analysis and the migration report.
The report can contain the sections in the following list. Each of these sections is explained in more detail in this topic.
Summary Summarizes the results of the analysis or migration.
The number of actions analyzed versus the number of actions migrated might be different because not all analyzed actions are migrated. Actions that are not migrated include the archive, restore, purge and destroy actions.
Errors Lists data loss errors.
Warnings Contains information about problems that occurred during the migration or analysis, such as a loss of data during migration.
User Input Describes the command-line options provided by the user for the converter.
The following table describes the entries in the Summary section of the report:
Shows whether the migration or analysis was successful or not, and indicates the number of errors or warnings. Click the error or warning number to see its details.
Type of Migration
Specifies if the migration was a full migration, or incremental. For more information, see How to: Incrementally Migrate to Team Foundation.
The name of the source control program from which the source was migrated or for which the migration analysis was done.
The path of the Visual SourceSafe database.
Team Foundation Server (Migration Report Only)
The Team Foundation Server to which the source was migrated.
The number of actions that were migrated or analyzed.
Files and Folders Migrated
The number of files and folders that were migrated.
Verified & Fixed Pinned Versions
The number of items that required fixing so that the pinned version in Visual SourceSafe matches the PINNED label version in Team Foundation version control. For more information, see Version Matching.
Verified & Fixed Latest Tip Versions
The number of items that required fixing so that the latest tip version in Visual SourceSafe matches the latest version in Team Foundation Server. For more information, see Version Matching.
The start time for the migration or analysis.
The end time for the migration or analysis.
The total time it took to run the migration or analysis.
Migration/Analysis done by
The alias of the person who ran the migration or analysis.
Lists the folders that were migrated or analyzed.
This section contains information about the files and folders that were not migrated because the converter could not warn during analysis. If you have errors during analysis or migration, some files or folders were not migrated. The converter is not always able to migrate or analyze files and folders or specific versions of files and folders because the Visual SourceSafe database you are migrating is corrupted or there is an unhandled case in the converter. File and folder migration errors are generated when the converter cannot migrate or analyze versions of files or folders because there is an unhandled case in the VSS Converter. Each error message gives a brief description of the error that was found during migration or analysis.
The errors do not mean that the migrated database is not usable. You can decide to ignore the files that were not migrated and start to use the migrated sources in Team Foundation version control. For more information, see Migration Errors.
This section contains information about the loss of information or modification of information because data in Visual SourceSafe cannot be migrated to Team Foundation version control for a known reason. The warnings are caused by functional differences between Visual SourceSafe and Team Foundation version control. During analysis, the converter warns about this potential loss of information, except for data loss warnings caused by Visual SourceSafe database corruption. When the Visual SourceSafe database is corrupted, you will not be able to retrieve the version through the VSS Explorer or VSS command-line. You can take some action to prevent the information loss, or you can decide to accept the information loss and run the converter anyway.
Each warning gives a brief description of the potential or actual data loss during migration or analysis, and contains a link to a document that explains details about the error.
The user input section shows you the command-line options that were used to run the conversion.
Shows the complete command-line entry used to run the migration or analysis.
Shows details of each option specified on the command line.