UPDATE: The content of this post was originally a gap in the on-line MSDN documentation which has since been filled. The official MSDN documentation can now be found here.
I recently worked with a customer that was upgrading from Team Foundation Server (TFS) 2008 to TFS 2012. After the upgrade, all of the existing Team Projects were available within the new project collection as expected. However, one thing the upgrade process doesn't do for you is upgrade the team projects themselves. That means that the Team Projects were still operating off of the MSF for Agile Software Development 4.2 process template rather than the new 6.0 version of the same template. Since the customer wanted to take advantage of all the new functionality and work item types added since 2008, we needed to upgrade each of their existing Team Projects to add these features.
While there is documentation on TechNet for Adding Features Using a Manual Update Process, this focuses on upgrading from TFS 2010 to TFS 2012. That didn't quite fit the bill for our scenario since there were a great deal of changes between TFS 2008 and TFS 2010 that weren’t accounted for. I also found documentation on MSDN regarding Enabling Interfacing with Microsoft Test Manager for Upgraded Team Projects. Since the customer was interested in using MTM, that sounded promising, but this guidance focused on an upgrade from TFS 2008 to TFS 2010. So I had information for upgrading from 2008 to 2010 and from 2010 to 2012, but nothing to go directly from 2008 to 2012. So we took the approach of combining the two separate pieces of guidance into one concise approach as outlined below.
Since we had to perform the above operation for multiple team projects (upwards of 50) we tried to automate the process as much as possible to creating some simple command line files to accommodate this.
NOTE: The above outline is specific to the MSF for Agile Software Development process template but should be similar for other process templates.
The command files and the updated process template files required for the steps listed above are included in the zip file below for reference.
Upgrade Scripts and Modified WIT Files