This documentation is archived and is not being maintained.

How to: Prepare your Visual SourceSafe Database for Running the Converter

Before you analyze or migrate the source-controlled files from Visual SourceSafe to Microsoft Visual Studio Team System, you may want to prepare your Visual SourceSafe database.

Required Permissions

To perform these procedures, you must have administrative permissions for the Visual SourceSafe database that you will migrate. For more information, see How to: Assign Project Rights on the Microsoft Web site.

To prepare your Visual SourceSafe database for migration, you should check in all files, fix any data integrity errors, back up the database, and decide which projects to migrate.


You should install the latest Visual SourceSafe update before you start the migration. For more information, see article Q950185, "FIX: Some items may not be retrieved from the Visual SourceSafe database when you use the VSSConverter.exe tool to migrate from Visual SourceSafe 2005 to Team Foundation Server."

To prepare users for migration

  • Ask all Visual SourceSafe database users to check in their files.

To prepare projects for migration

  1. Install Visual SourceSafe 2005 on the computer on which you are running the converter. By default, Visual SourceSafe 2005 is not installed when you install Visual Studio.

  2. Copy your Visual SourceSafe database to a local folder on the computer on which you are running the converter. Although you can migrate a Visual SourceSafe database in a shared folder on a remote computer, the migration takes longer.

  3. If your Visual SourceSafe database is a version earlier than Visual SourceSafe 6.0, upgrade it to 6.0 by using the Visual SourceSafe DDUPD utility. For more information about the DDUPD utility, see DDUPD Utility in the Visual SourceSafe Reference.

  4. Fix data integrity errors. Use the Visual SourceSafe analyze utility to locate, and if it is possible, fix any data integrity issues in the database. For more information about the analyze utility, see ANALYZE Utility in the Visual SourceSafe Reference.