We have to upgrade TFS version from 2012 to 2017. The problem we are facing is we have some team projects in TFS 2017 lower environment and some team projects are in 2012 production instance. We want to migrate 2012 team projects and 2017 team projects to a new TFS 2017 production instance under one team project collection. We need some help in defining the upgrade/migration strategy keeping this scenario in consideration. Please let us know if someone can lend help.
2
votes
2 Answers
3
votes
It supports to move collections from TFS 2012 to TFS 2017 directly follow the move collection document. You don't need to upgrade your TFS 2012 to TFS 2017 first. It does the upgrading When it attaches to the new TFS instance, just follow theses steps:
- Detach the collection
- Back up the collection database
- Move the collection database
- Attach the collection
- Configure Features for team projects(option)
Note: The step5 is done when you move TFS 2012 collection. If you move TFS 2017 collection to your new TFS 2017. This step doesn't need to do.
And you want these 2 collection to merge to one collection totally. This is not support currently. There are two many conflicts: changeset numbers, work item IDs, builds,etc. And it also doesn't support to move team project from one collection to another. Here is a user voice about move team projects between collections which has many votes already:
We still plan to evaluate picking this work up and possibly getting it into the following next major release. We’ll provide an update once a decision has been reached.
1
votes
I'd suggest that you do the migration from TFS2012 to TFS2017 just as described by Microsoft here and after your new TFS2017 is up and running, move the Team Project Collections from your current TFS2017 to the new one which is described here
