Migration, Integration and Synchronization

Migrations from Visual Source Safe (VSS)

In our experience one of three options is used for the migration of version control systems.

The first option is a complete migration of the entire Visual Source Safe history to the Team Foundation Server. This migration can be done piece by piece (one repository part after the other), but is very time-consuming. For more information please click here.

As an alternative, the current state of the Visual Source Safe version control can be transferred to the Team Foundation source control.When doing so, the Visual Source Safe database must be maintained (read-only) in order to analyse the version history retrospectively.

In some cases it also makes sense to migrate single sub-versions (e.g. for releases) from Visual Source Safe.These are mostly marked with labels and serve as possible branching points in the Team Foundation Server for retrospective maintenance of earlier software versions.