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.
PLease.. this would be of great use to us.
Bill Simpson commented
A recent reorganisation request to move projects around collections to make it simpler for our company to record support issues for all our applications from one place, would require this feature to be implemented
Shawn McNabb commented
I can add our voice to this request as well. We recently moved to 2013 and need to separate projects by business units. Plus we have many projects that can be archived. It looks like all movement on this has stopped. We would rather not use third party tools to augment the functionality of TFS. If the ability to migrate collections can't easily be built in, why can't Microsoft can provide a tool?
Bart Janson commented
Note, when moving a team project, all data should be removed from the source collection (not just the versioning files, but also all work item data).
I created a separate uervoice story after finding out that during a split, not all project data is removed.
Andrew Barker commented
TFS Collections are great for organizing projects by the teams responsible, I just wish that I could easily move projects between collections to indicate when a project has been assigned to a new team or has been archived.
Vik Jaggi commented
We'd like this feature too. Right now folks have to muddle through an array of tools to migrate the data and still a lot of it is lost. Why can't MS make it easier for everyone and provide a tool to do it?
Randy in Marin commented
This is one of the major failings of the current TFS design. Having a single changeset sequence for a collection limits options. I think a changeset sequence per team project would have been better. Perhaps every team project needs a globally unique guid. A single checkin would generate a new sequence number in every team project that is part of the checkin. A new collection method would be required to simulate a collection changeset sequence. Perhaps a table that relates the team project changesets? The collection level sequence would change as projects are exported or imported, so using it as a key would not be good. Stable references would have to use the team project guid (or id mapped to the guid - I don't like guids) and team project changeset number.
Perhaps another option is to use a universal time to the nanosecond instead of an integer sequence. When moving team projects around, the changeset values will mostly merge. If the some changeset times are the same, introduce a tracked change to make them unique. When exporting the team project, undo any changes used to make records unique. (Add a ns? Add a fraction of a ns? Add a sequence id column that is normally 0?)
Without a redesign, it will be close to impossible to move projects correctly without re-sequencing changesets. That does not sound fun at all. A TFS 2016 with a new design could import an old collection and add new team project sequences just by using the old values. After that, projects are free to roam.
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.