Migrate Team Project from TFS 2013 To TFS 2015

4
votes

I need to migrate one Team Project from TFS 2013 update 4 server to instance of TFS 2015. The source project is located in default collection. The default collection contains many team projects and I can not migrate them because there is security reasons. There is no possibility to get whole team collection database. The splitting of collection is also not possible because the database and TFS application server manages another company. I can use only TFS API.

I found TFS Integration Tools but I'm not able to install it. There are two errors while i'm installing it:

  • Unsupported API (integration tools requires team explorer 2008, 2010 or Dev11)
  • Probably Unsupported version of DB

Is there any other approach how to migrate specified team project to another instance TFS?

3
visual-studio-2013tfsmigrationvisual-studio-2015tfs-2015

3 Answers

1
votes

If splitting the team project collection is unachievable, you need to use TFS Integration tool. And to fix the error message you got above (integration tools requires team explorer 2008, 2010 or Dev11), please first try installing Team Explorer 2012 then install again. Also have a check on this blog for the details on how to handle it: http://blogs.msdn.com/b/willy-peter_schaub/archive/2012/07/04/tfs-integration-tools-issue-this-tool-requires-the-tfs-client-object-model.aspx

1
votes

It is possible to single team project from a default collection of TFS2013 update 4 to TFS2015. Along with basic data, OVSMU can migrate Work-Items (including test artifacts) with history, relationship, attachments & comment. Source control (TFVC to TFVC) also can be migrated with history, comments & labels. Links between Changesets & Work items are also restored. Look at the OVSMU solution from OpsHub. The premium version of the solution would be of your use.

0
votes

You could consider using the GIT-TF client. Similar to the approuch highlighted here: http://www.teamfoundation.co.za/2014/10/move-from-git-to-tfs-version-control/ but you will start from a TFS repo to a new TFS repo.

Both options are going to be lossy (some of the metadata will go lost), it is a lot easier to split out the collection.