• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 734
  • Last Modified:

Upgrade TFS 2005 databases to a new collection in TFS 2010

I have an existing TFS 2005 server that we've been using for most of our source control. We also have a new TFS 2010 server (new hardware) that's currently available and has some project collections on it. I'd like to get rid of the old server, and that means moving the source control history to the new server.

Ideally, I'd like to create an empty project collection on the new server and import the entire history from our 2005 server into this collection, but I'm not sure if that's possible. From my research, it seems that the only upgrade path is an in-place upgrade (or a new hardware in-place upgrade, where you restore databases and then upgrade). Does anybody have experience doing the type of upgrade I'm describing, or moving the data to a new server?
Ryan McCauley
Ryan McCauley
  • 2
2 Solutions
We had the same situation at my company. We initially attempted an in placed upgrade. But, for some reason or another this failed. So, we built a brand new instance of TFS 2010 and added all the code manually. Losing the history was not such a big problem for us. We did pick up some usefull knoweledge along the way however. If you have any specific questions please ask.
Ryan McCauleyData and Analytics ManagerAuthor Commented:
I actually just completed this upgrade last week - it turns out there's a built-in "migration" tool (I use quotes because it doesn't migrate the Sharepoint content, just the source code and tasks). It essentially takes your existing Source Control database and upgrades it to TFS2010, cramming in all the stuff from the other databases. It deletes your old databases and leaves you with a new one, though, so to leave the possibility of a rollback if it failed, we restored all our databases to a test server and upgraded them there, which worked flawlessly.

Here are the steps I followed:


Also, there were a few gotchas that I detailed on my blog, including the requirement that the SQL Server be at least SQL 2008 (or you'll get an error that doesn't mean anything useful):


Hope that provides some help to anybody else in the same situation - all the folder mappings, the check-in/outs, source history, and work item tracking is persisted, but the Sharepoint work site content has to be migrated manually. We didn't use the Sharepoint component, so no big deal for us, but might be a pain for companies that heavily use the Sharepoint site for development collaboration.
Ryan McCauleyData and Analytics ManagerAuthor Commented:
I accepted my own answer because I found the solution myself and executed it without any other input. I awarded points to the other poster since they were the only ones to respond to the question with their input.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now