Please let me know is it possible to migrate all the checkin histories with comments while migrating from TFS 2010 to TFS Cloud?
We migrated out TFS 2010 server to Team Foundation Service using the TFS Integration Platform. This will allow you to migrate your history to Team Foundation Service one-time or you can configure a bidirectional sync, although the latter is admittedly a much more complicated setup.
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.
I'd like to know if it's possible to migrate from a Visual Studio Team Services to a local Team Foundation Server. I've seen many questions about the reveser process but not this.
I know I can download source code from VSTS and upload it manually to TFS, but I'd like to keep as many work items and project structure as possible.
You can try with TFS Integration Platform, it may have some errors but can work. Refer to this link for details: Migrate VSO to on premises TFS.
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.
Team System 2010 has some new features that really interest me including branched history, rollback, and baseless merge. Are these features available with just the new Team System Client, or do I have to upgrade my TFS server to use them?
You can do baseless merges in TFS 2008. Rollback is built into TFS 2010, but is also available in the Team Foundation Power Tools for TFS 2008. The new branch features are only available in TFS 2010 (you'll need to upgrade your server). The good news it that upgrading your server is fairly straightforward and there's an update for Team Explorer 2008 that improves its compatibility with TFS 2010.