We're currently using TFS 2010 for both source control as well as task tracking however the structure of both our projects and project collections leaves quite a bit to be desired. That being said, we're looking to restructure everything in a more efficient way when we move to TFS 2012.
My question is this, is it possible to move our existing projects into a new TFS 2012 project collection (including work items, tasks, etc.) for legacy/historical purposes? I'd like to have the current project structure and history available for historical purposes with active development on-going in a different project collection using our new project structure.
Everything I've seen so far suggests that its difficult (or impossible) to move entire projects between collections due to work item numbering, etc. I've considered detaching our 2010 project collections and re-attaching them individually in 2012 but I really don't want a whole list of project collections (which is part of our current problem). That then brings me to the challenge of merging project collections or moving a project between collections.
Any suggestions, work-arounds or tips would be greatly appreciated! Thanks in advance!
Best Answer
This is very much possible with TFS Integration Toolkit but it is extremely tedious and time consuming process. There is a learning curve. Tool is buggy so you have to work around it. I recommend don't get into it unless it's a high priority for team/management. Here is the procedure, do clean TFS 2012 install and then migrate work items and source using this tool. Make sure you also install TFS 2010 team explorer along with toolkit (it uses 2010 object model to migrate). You should setup a test environment and try it multiple times to achieve desired results. This item was raised numerous times for TFS 2008->2010 and you can pretty much follow same guidelines. See my response here. You may not be able to migrate work item IDs but can add a field to show old work item ID:
Tool Limitations from documentation: