[Team System] Migrating Code From VSS to VS2005 and Team Foundation Server

UPDATE: I really, really recommend that you check out this GUI for VSSConverter at http://www.epocalipse.com/blog/2006/04/06/vssconverter-gui/ It was created by Eyal Post and it works like a charm! 

We recently tried to migrate old VS2003 code from VSS to VS2005 and Team Foundation Server using the vssconverter utility that ships with Team System, and it worked pretty well... after a while.

It's pretty straight forward if you follow the guideance on this page, http://msdn.microsoft.com/en-us/library/ms253060.aspx, but I really recommend you make sure the old code and VSS database is backed up first and that you try the migration to a test-project first.

We set up a local VSS database on a client machine and moved (via archiving) the code to that local database first. Then we ran the analyze, test migration, tweaked the user mapping file and then finally kicked off the migration to the production TFS project. It worked without any major problems except that we had to be logged in as a user on the domain and with proper right to the team project. But it's all in the TFS documentation on MSDN... somewhere :D

What may be somewhat itchy is the work you may get into after that, when you open up old solution and project files. It may be that VS2005 fails to load the old project files, but try to do a "get latest" and check out the .vbproj and .csproj files, then try to reload the projects. Good luck! 

UPDATE: It looks as if the best way to open up a migrated solution is to locate the solution file in the Source Control Explorer window and double-click it. I will probably ask you to re-bind the projects, so do that and they should "connect" automatically. Make sure you have "Visual Studio Team Foundation Source Control" selected as your Source Control Plug-in in Tools->Options. It happens that the plug-in selection reverts back to VSS sometimes when the solution is opened.