make it possible to move a Team Project between Team Project Collections
Currently you need to move an existing Team Project to a new Team Project Collection. I would like a feature to move Team Project between Team Project Collections without using TFS Integration Toolkit or other 3rd party tools.
Michael Dynes commented
This is a very relevant feature/functionality. I currently have a need to migrate a development project from TFS 2010 collection instance to a TFS 2013 collection instance. Currently, that does not appear to be possible.
The ability to move a project and/or consolidate collections is a capability that needs to be addressed. TFS Intergration tool is/was not the answer.
Eric Aldinger commented
I would like this feature as well. I have had several occasions to do this and it is less fun than other tasks in TFS
Suman Brar commented
This would definately be a very useful feature as it will help in solving the database size issues. By moving a particular project to new collection, bloating datatbase size will reduce and help in overall backup, maintenance and upgrades.
Alex Drozdowicz, AVEVA Solutions Ltd. commented
Microsoft now recommend we put all our projects all in one collection. Unfortunately they forgot about the existing users who had separate projects before collections came into being. It's naïve to think that everybody can start with a clean page, most projects live for many years ... if MS wants us to move to new releases we need much better out of the box tools to move from the old world to the new one.
Would be a wonderfull feature!!!!
Don Kirkham commented
Having a dozen projects (or more, possible hundreds) in one collection can get very confusing when only a few of them are active projects. The ability to move these projects into an Archive collection, including all history, code, etc., for the project, would be very valuable. This would allow active projects to managed more easily, while archived projects are available for reference.
It would be great if that is possible. Please let me know!
Jonas Brock commented
A copy project feature (i.e. with the need for the user to delete the source afterwards if a move is desired) would be enough but we need initially to move 50-60% of our projects to another collection, and regularly archive projects (i.e. not delete) but to facilitate a change in backup and security profile etc. on older projects that are no longer active but still valuable source code wise and so on.
Can't understand why it is not obvious that this feature is very relevant. We've recently upgraded from TFS2008 SP1 straight to TFS2012 using the upgrade wizard and the only option we had was to make one project collection with all projects in.
It would have been fine with us if we in the upgrade process had given us the option of splitting the projects into x number of project collections at that point. But being able to do it afterwards is even more valuable.
We don't at present need team site copy and so on only the "native" TFS stuff like source code including history and comments, and work items etc. however a complete project copy would be preferable.
We really do not want to have to rely on third party tools and plug-ins for our enterprise work.
Moving projects is fundamental to organizing code
This would be very helpful, particularly in the scenarios of enterprise re-orgs or any change of structure, such as having TPC initially organized by region then by function.
Nicholas S commented
This would be extremely useful for me as well. Particularly if you could use it to move a team project between servers.
This seems like a "no-brainer" feature to have...like moving a folder from one directory to another...or a table from one database to another...or a database from one server to another...or a ...I think you get the idea.
I would also welcome this feature!
Chris F commented
We are trying to test the upgrade of a custom process template and I want to copy the Team Project we need to test to a different collection so that we can run the upgrade on that specific collection and verify everything is working.
I ran the following commmand with the /clone option
TFSConfig Collection /attach /collectionName:http://SERVER:8080/tfs/DefaultCollection_TESTING /collectionDB:SERVER;Tfs_DefaultCollection_TESTING /clone
TF253021:The following team project is duplicated in at least two team project collections: IT. The collection cannot start while the duplication exists. You must delete this project from all but one of the collections before the collection can be started. The project exists in the following collections: DefaultCollection,DefaultCollection_Testing
But when I try to bring the collection online I get the following error:
I would like to "move" a Team Project from one collection to the other.
I dont need to "merge" into another team project etc. So hopefully there wont be any data conflicts etc or issues.
Its so that we can manage collections effectively and still preserve history without having to recreate projects.
Charles Herrington commented
We didnt realize until just now that you cant have projects shared across collections. Now that we know this we want to move all the projects that use the same shared projects into one collection but cant.
Manish Jain commented
We also have need for this feature. We are creating new projects in 2010. Later we would like to migrate 2008 team projects into existing collection. Just like tfs integration platform, its okay to renumber work item, change set numbers etc. I understand this is a complex feature to implement but this should be part of TFS suite and less complex than integration platform.
Visual Studio ALM Team commented
Wow, this is a tough one. The challenge has to do with all kinds of data conflicts that would be encountered when you tried to merge a team project into another collection. As an example, to do it with full fidelity, almost every changeset in the target collection would need to be renumbered, every link to those changesets would need to be updated, every work item in the source project would likely need to be renumbered, etc. Any place you've stored a reference to those items outside of TFS (such as work items in Excel-bound spreadsheets) would need to get updated.
What is more realistic, and perhaps more valuable overall, is for us to eliminate the limitations imposed by the project collection boundary. Can you tell us which limitations are frustrating you? Is it linking between work items in disparate collections? Branching/merging code between collections? Backup/restore consistency of projects in different collections?
In the meantime, Martin's proposed solutions are the best thing going. They aren't perfect, but they are better than nothing.
Daniel Steiner commented
@martin, TFS Integration Platform is far away from being an ideal solution for the described scenarios if you really want to migrate all data of a Team Project.
From Visual Studio Code Gallery "Team Foundation Server Integration Tools (March 2011 Release)":
As mentioned above, there are items that are not migrated when using the tool and this should to be taken into consideration when deciding on whether to do a migration or upgrade.
What IS NOT migrated by the Toolkit
* Check-in notes