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.
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.
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
Related
We need to migrate projects in TFS from one server to another. On source server we have TFS 2010 with several VS.NET projects in the DefaultCollection. On the destination server, we have TFS 2013 with an empty DefaultCollection but 2 other collections in use by other developers. Each instance of TFS has its own SQL Server.
The problem we face is how to take the DefaultCollection from the TFS 2010 server and place it on the TFS 2013 Server?
I'm aware of several articles about migration but have not found one that exactly fits our situation. I appreciate any ideas anyone may have.
This is a very straightforward scenario.
Something along these lines should work:
Detach DefaultCollection from TFS 2010 using the admin console.
Take a backup of your TFS 2010 DefaultCollection database
Migrate the database to your TFS 2013 database server
Attach the TFS 2010 DefaultCollection database in TFS 2013 via the admin console. As part of the attaching process, you should be able to rename it.
The team project collection database will be upgraded to TFS 2013 and made available to users. At that point, you can go back and clean up unneeded project collections and rename things if you'd like.
Always take backups before you attempt any sort of migration or upgrade. I always recommend performing the upgrade against a test environment first.
We currently have a TFS 2012 Server which is being replaced by a 2015 server, the aim is to gradually migrate our code from one to the other.
When we do this we would like to maintain the checkin history, labels etc, Looking at similar questions the answer seemed to be to use the integration toolkit, however it looks like it (and its successor the integration platform) do not support TFS 2015.
We are using TFVC rather than git, if that makes a difference.
I don't have much knowledge about the integration toolkit, but I would actually suggest to do the upgrade one Team Project Collection at a time, but moving them separately to a new server with TFS 2015 installed. This way you will keep all history, label etc.
We have done this way back when upgrading from TFS 2010 to TFS 2013. Only obstacle that we had was a collection around 500 GB in size so it took around 16 hours for the upgrade to finish.
The following answer specifies the steps needed to move a collection to another server:
Copy TFS 2012 collection to another server with TFS 2015 Installed
We have used this Migration tool for our Client.
It’s possible to migrate TFS 2012 data to TFS 2015 with all information intact without any system downtime. The premium version of OpsHub Visual Studio Migration Utility (OVSMU) supports migration of projects with TFVC repository from one instance to another. It supports the 2010, 2012, 2013, and 2015 versions of TFS and all versions of Visual Studio Online, including the 2017 version. Along with basic data, you can migrate all workitems with history, comments, attachments, relationships, and source control with changesets, history, labels, comments, etc. You can checkout the details here: https://www.opshub.com/products/opshub-visual-studio-migration-utility/
HELP!!
I'm learning on the fly here with no training whatsoever! I'm a system administrator who is responsible for supporting the developers. They use Visual Studio, TFS, Plastic SCM and TeamCity amongst other tools.
My task was to get TFS 2015 and SQL Server 2014 installed on a new VM. This I have done but my biggest task now is setting up TFS which seems complicated.
For your information, The developers use TFS 2012 as a Kanban board.
Can anyone point me in the right direction to documentation that simply explains how to copy a project from one collection to another? I'm reluctant to move the project to the new version of TFS without testing the current project.
Thanks in advance.
You cannot copy a single project, there is the TFS integration platform, but it sucks and doesn't officially support TFS 2015
I would say your best bet is to follow the following steps.
In TFS 2012, detach the collection using the TFS Admin Console.
Backup the collection database in SQL server
Copy the backup to the new SQL server
Restore the Database
In the TFS Admin Console in TFS 2015, attach the collection
Wait for TFS to update the Database Schema.
You should now have the full team project collection available in the new server.
We have a collection in TFS 2012 which contains more than one project.
We are considering to migrate to TFS 2013.
The TFS servers are already up and running.
Is it possible to migrate the data of a specific project in the collection from one TFS server (2012) to the other (2013) or we must migrate the whole collection?
The best way to do it would be to split up the team project in team project collection and then upgrading only the new team project collection. See below for splitting up team project from project collection
http://msdn.microsoft.com/en-us/library/dd936158.aspx
Also, the Tfs To Tfs migration guide will be useful.
http://tfstotfsmigration.codeplex.com/releases/view/37382
We are planning to upgrade from Tfs 2012 to Tfs 2013. Can anyone help me understand the difference in process templates between them? We use all three process templates for different projects.
The changes are very minor, except for:
The introduction of Portfolio backlogs.
Test Plans and test Suites are now Work Item Types (TFS 2013 update 3).
The AgileConfig and CommonProcessConfig files have been merged to a single file inside the template
The minor changes:
Git support for the Source Control options
Stackrank type fields are now hidden by default (because Agile task boards are now features of the Standard CAL).
Tag field support through the API.
The easiest way to visualize all differences is by comparing them through the TFS Team Project Manager which can be downloaded here.
TFS 2013 did not work well with our existing workspaces defined on remote network drives. TFS 2012 did work with this configuration.
After working several hours with our System Administrators, we gave up on trying to get the trying to get the existing network drive workspaces to work with the TFS 2013. Converting the workspaces to local drive locations enabled us to work with TFS 2013.