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
Related
how to migrate a single project alone (where project collection contains 30+ projects) from TFS to VSTS with all history, build-definitions, changesets
Microsoft has documentation on this exact scenario which can be found here: Migrate to Visual Studio Team Services : Move from Team Foundation Server (TFS) to Visual Studio Team Services (VSTS) and bring your data along.
This link also contains the download link for the migration tooling which you will want to use
Currently the following versions of TFS are supported for import:
TFS 2017 Update 3
TFS 2018
TFS 2018 Update 1
As described in About VSTS and TFS, Scope and scale data, the
long term direction for VSTS is to support grouping of accounts within
organizations. This would lead to:
VSTS accounts that serve as the equivalent of TFS project collections and VSTS organizations that serve as the equivalent of
TFS deployments.
This is why the TFS Database Import Service only supports importing single TFS collections as single VSTS accounts.
If you need to migrate individual team projects you will need to use
one of the other options—manual copy or public API based
migrations.
Source Link
It's very clear why you could not use TFS Database Import Service to migrate at team project-level directly.
You can also have a try for VSTS Sync Migration Tools,it allows you to bulk edit and migrate data between Team Projects on both Microsoft Team Foundation Server (TFS) and Visual Studio Team Services (VSTS). Note this without history. How to please refer: TFS 2017 Migration To VSTS with VSTS Sync Migrator
If you insist on keeping all history, the only way is using TFS Database Import Service, you may take the workaround as Daniel suggested.
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
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.
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.
There are a lot of questions about upgrading here, but I have another, very specific one, that I don't see asked.
When installing TFS 2010, on the first run, you get a wizard, which lets you choose a database (which you presumably backed up, and restored onto the new instance) to use, and it allows you to upgrade that instance in-place.
If I'm performing a dry-run, during the course of which I do not want to disable access to the OLD tfs, is it possible for me to do this upgrade a second time without reinstalling TFS?
IE: can I create a new team project collection and point it to a tfs 2008 database and have it upgrade that?
I dont think it is possible to point to a TFS 2008 database from TFS 2010.
We have migrated our TFS 2005/2008 too.
We installed a fresh new TFS 2010 and migrated the old projects into the new TFS 2010.
All files of the projects in TFS2005/2008 are set to read only, workitem history and changesets are migrated into the new TFS2010.
We decide to switch the process template too so we created another team project with the Scrum Template.
Afterwards the source and all needed files are copied to the new Scrum team project.
Now if I let me show the history of a item under source control, it shows the history till the beginning of each item (points to the "old"/first migrated team project in TFS 2010).
I did it an upgrade test on a dummy machine and when i get to the real thing I had to uninstall and remove all leftover db's (tfs_configuration) you can see migrate data from TFS 2008 to an already working TFS 2012