Export (0) Print
Expand All

Planning for Source Control Migration

This section contains information about how to plan to migrate your Visual SourceSafe source control projects to Team Foundation version control. The migration process is time-consuming because you are migrating years of source control data. The converter provides migration options that can minimize the time to migrate by either reducing the migration time or enabling your teams to work on source control during the migration. Evaluate which of the following migration options will work best for your team:

  • Project-by-Project migration   Use this option to migrate the sources of one team or project at a time; typically one folder in Visual SourceSafe. This option makes sure that other teams are not blocked during migration; however, if two teams have dependencies between their sources, you should migrate the sources of both teams, that is project folders, together. The two folders may have some dependencies that could cause data loss if only some of the folders are migrated. The analysis phase helps identify the dependencies between folders.

  • Incremental Migration   Use this option to migrate your Visual SourceSafe database in phases. Migrating a Visual SourceSafe database in phases ensures that users can continue to use Visual SourceSafe while migration is in progress. For more information, see How to: Incrementally Migrate to Team Foundation

  • Use Archive feature of VSS to migrate partial history   Use this option if you are not interested in migrating old history. By using this feature you remove the version history of file and folder before a specific date. For more information, see How to: Migrate a Partial History Using Archives in Visual SourceSafe.

In the first phase, you do analysis of the Visual SourceSafe database under migration and in phase two, you do the actual migration of the Visual SourceSafe database to Team Foundation version control. The analysis phase generates a report that gives you information about potential data loss during migration. You can prevent some of the potential data loss by taking some pre-migration steps; however, some data loss cannot be prevented because some Visual SourceSafe data cannot be mapped to Team Foundation version control. After migration, you receive a report that gives you information about status and any data loss during migration. Post migration, you may have to perform some steps to make sure that you can use the migrated sources.

The approximate free disk space on the data-tier of Team Foundation Server required for migration can be estimated bases on two factors:

  1. The size of Visual SourceSafe database under migration.

  2. Number of actions to be migrated

It is recommended that you have enough free disk-space on the Team Foundation Server data-tier to accommodate twice the size of Visual SourceSafe database under migration.

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

Describes how to prepare Visual SourceSafe for the migration.

How to: Create a Settings File for Source Control Analysis and Migration

Describes how to create a settings file to control your migration.

How to: Analyze your Visual SourceSafe Database for Migration

Describes how to generate a pre-migration analysis report.

How to: Set Up SQL Express for Migration

Describes how to set up SQL Express for the migration.

How to: Prepare Team Foundation for Migration

Describes how to prepare Team Foundation version control for the migration.

Community Additions

ADD
Show:
© 2014 Microsoft