Migrating Team System Project from one server to another

hi,

How can i migrating a Team System Project (with all the relvant data and configuration) from one server to another

Visual Studio Team System6

Take a look to this article which has links about moving between servers

http://blogs.msdn.com/vstsue/archive/2006/03/22/558178.aspx

As it says in Allen Clark's post here, I do not believe there is any support for moving projects between servers.

That being said, if there is nothing else in the new TFS, you may be able to backup/restore all data to a new server:
http://msdn2.microsoft.com/en-us/library/ms253151(VS.80).aspx
http://msdn2.microsoft.com/en-us/library/ms252516.aspx

Hope this helps-

Cheers,
Adam

Ups, sorry I read quizkly and didn't notice you refered to a single project

Hello,

As it says in Allen Clark's post here, I do not believe there is any support for moving projects between servers.

That's sad to hear as I have the same task - I need to backup/restore only a single project between 2 TFS servers. In VSS it was quite simple task with SSARC utility.

Are there any plans to implement single project migration feature in the future

Thanks.

You can backup and restore the entire database between servers. As for single project move, I know we've had a number of requests for this functionality. I'll check around internally to find out what our plans are, if any, here.

Cheers,
Adam

We are actively working on plans for a single project move, but there are not many details to share at this point. I can assure you that you are not alone in wanting the feature - the feedback on that point has been clear.

Is there anything new to report on this feature To be honest, I'm rather astonished that you guys are surprised this feature would be requested..did you never expect that somone might need to consolidate team projects onto a single server Or that they might have the need to archive team projects with the ability to restore them individually later I realize source control is a different beast, but it should still be designed with certain records management paradigms in mind, namely the ability to move individual records around without breaking the database.

There are many issues with any approach to this problem, including the unique item ids in both version control and work item tracking, and how moving projects on/off of a server might affect all of the cross links between items. Several folks are actively investigating potential solutions, but I am not aware of any definitive decisions being made.

That being said, we do hope to add some functionality to improve this experience in a future release.

Cheers,
Adam