Moving a Team Project from One Version to the Next

Moving a Team Project from One Version to the Next

  • Comments 2

If the team project you are managing has completed a major iteration or milestone, and has grown too large or is not compatible with the desired workflow going forward, you can create a new team project based on the existing one. Moving a team project from one version to the next involves some combination of branching source code, copying items, and recreating existing items in the new team project.

Create the New Team Project

The first step in moving the team project to the new version is to create the new team project using the New Team Project Wizard. Follow the instructions on the wizard pages filling in the name and other information for the new team project. When asked to specify the source control settings, create a new source control branch from the old team project.

Move the Work Items from the Old Team Project to the New Team Project

There are likely to be unfinished work items in the old team project or work items that were created to be accomplished in the next version. You must copy the unfinished work items to the new project one-by-one asTeam Foundation Server does not support the bulk copying or moving of work items across projects.

Note   Making a copy of a work item sets the status of the new work item to Active by default. If you have work items in the old team project with a status other than Active and you copy these work items to the new team project, be sure to set the status on the new work item to the same status it had in the old team project.

Set the User Permission for the New Team Project

It is important that you correctly set the permissions for the new team project. You must set the permissions on each item one-by-one (for security reasons Team Foundation Server does not support the bulk copying or moving of permissions from one project to another).

Copy the Documents from the Old Team Project to the New Team Project

There are likely to be documents and reports in the old team project that are still relevant to the new team project. You can copy the documents to the new project by dragging and dropping the documents within Team Explorer.

Create the Areas and Iterations for the New Team Project

The team project structure and classification used in the old team project may or may not be appropriate for the new team project. You must create the areas and iterations for the new team project one-by-one as Team Foundation Server does not support the bulk copying or moving of areas or iterations from one project to another.

Create the Check-in Policies

The team project check-in policies used in the old team project may or may not be appropriate for the new team project. You must create check-in policies for the new team project one-by-one as Team Foundation Server does not support the bulk copying or moving of check-in policies from one project to another.

Create Alerts

If you are using alerts in the new team project, it is important that you set these event notifications correctly. If you want to continue to use the same type of alerts used in the old team project, you must create the alerts for the new team project one-by-one as Team Foundation Server does not support the bulk copying or moving of alerts from one project to another.

Determine if a New Backup is Appropriate

Because the process of creating a new team project, copying work items individually, and recreating permissions, areas, iterations, check-in policies, and alerts can take a significant amount of time, it is important that your work be protected from loss due to computer hardware failures. You may want to check with your Team Foundation Server administrator to determine if a special backup of the server is warranted.

Leave a Comment
  • Please add 6 and 4 and type the answer here:
  • Post
  • We are currently implementing the team system, and so this is useful information for planning project structure. When transitioning between a v1 and v2 of a product, what would be the motivation for creating a new team project and following all of the painful manual steps you described verses just branching the main version control folder within the same project?
  • hi,

    we have a TFS 2005 in app tire. we are trying to move the project existing in one forest to another forest between 2 diffrent TFS 2005 server. i need more inputs on this if someone know about this.

    Thanks,

    Vijay

Page 1 of 1 (2 items)