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?
LVL 28
Ryan McCauleyEnterprise Analytics ManagerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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 McCauleyEnterprise 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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ryan McCauleyEnterprise 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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Development

From novice to tech pro — start learning today.