I need to bring backlog tasks from a proprietary system to TFS 2013.
I came across an extension called "Team Foundation Server Integration Tools" and "Team Foundation Server SDK" but they support up to TFS 2012.
Is there any product I could use to create backlog tasks in TFS through REST or other means?
The 2012 integration tools work fine against TFS 2013, you only need to install the TFS 2012 Client Object Model. The 2012/v11 adapter works against TFS 2012-2015 and Visual Studio Online.
There are a few features which are unsupported:
Migration of Test results
Migration of Work item Tags
Kanban colum states
In addition to the items already listed on the Toolkit's page.
Alternative products for work item migrations are:
Tasktop Sync
OpsHub Integration Manager
Should you want to manually code up the migration then the TFS 2013 Client Object Model will have all the functionality you need. You're looking for the WorkitemStore class as your main starting point to create and modify work items.
An alternative approach you may want to investigate is to do an Excel import.
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.
What are the best practices to migrate workitems say PBIs/Features manually from TFS to VSTS? And how to ensure we don't lose any linking to changesets or other linked child workitems?
Have referred the below link and the migration tool mentioned is deprecated and would like to know any other options which will help to migrate the data.
How to migrate work items from TFS to VS Team Services (VS Online)
The recommend way for now is using Migrate to Visual Studio Team Service, a way import your TFS Database into Visual Studio Team Services which definitely along with data.
However, currently only the following versions of TFS are supported for import with this tool:
TFS 2017 Update 3
TFS 2018
You may have to upgrade your TFS server to use. Alternative, the Microsoft official option is using public API-based tools.
Personally, even though Team Foundation Server Integration Tools has been deprecated. You could still use this solution in your case.
Besides, if you have no work item customization, then OpsHub is an
option. VSTS Sync Migration Tools is another way. But none offer a full fidelity migrations. Each tool has its own limitations.
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.
I'd like to take advantage of Visual Studio Online but I have been using Team Foundation Server on-premises and would like to migrate my data (version control, work items, test cases, and test results) to get my team started with our history. How do I do that?
The Team Foundation Server Integration Platform is available as a free platform for migrating/synchronizing data between TFS servers and with Visual Studio Online.
The ALM Rangers have an article in MSDN Magazine with a walkthrough: http://msdn.microsoft.com/en-us/magazine/jj130558.aspx
There are a couple of limitations from what I understand:
Takes some work to get up and going but the walkthrough helps out a lot
This tool does migrate test cases but you need to run the UpdateSharedSteps tool from the product team.
Not actively invested in as new features in Team Foundation Server and Visual Studio Online lights up
Another option is to build your own migration utility using the Team Foundation Server SDK. You can use the Client Object Model to read data from your TFS server and then write it to your Visual Studio Online account.
There is a free migration utility from migrating data from Team Foundation Server on-premises to Visual Studio Online available from OpsHub: http://aka.ms/OpsHubVSOMigrationUtility.
It allows you to migrate team project(s) from TFS 2010, TFS 2012, and TFS 2013 including the history of:
Version Control
Work Items
Test Cases
It handles the most common scenarios by making smart assumptions that are good for most scenarios. For those with more advanced scenarios, the OpsHub Integration Platform is commercially available and helps with synchronizations, custom business rules during migrations including customized process templates, and migration/integrating with other ALM platforms like IBM, Atlassian, HP, etc.