Migration from TFS to Azure DevOps Services from a certain Changeset - tfs

I need to migrate a Project (TFVC) from TFS 2012 to Azure DevOps Service (Git). I would also like to migrate the project history. The problem I have, is that the 10 newest changesets are rubbish. So I would like to migrate from an older changeset with all the changeset history before this changeset. Is this possible? Has anyone got any experience with this? Thanks!

I would like to migrate from an older changeset with all the changeset history before this changeset. Is this possible?
I am afraid there is such way we could migrate from TFS to Azure DevOps Services with a certain Changesets.
As we know, the changesets/bugs/test cases/history are included when migrate TFS to Azure DevOps Services. But all the data operates at a database level rather than data, all the data are stored in the database. So, we could not exclude the date of 10 newest changesets in the database when you migrate from TFS to Azure DevOps Services.
Hope this helps.

Related

Move code from TFVC on TFS 2010 to TFVC on Azure DevOps Server

I have some projects on TFVC source control on TFS 2010. I want just to migrate the source code from TFS 2010 to TFVC on Azure DevOps Server.
I don't want to process an upgrade of the entire collection to a newest version. I Just want to transfer my code with history.
I tried Git-TFS. I cloned my repository on TFS 2010, but I don't know how I can update the remote URL for TFVC repos and push on Azure DevOps Server.
Any ideas how I can do it? Or other tools that I can use?.
In the case I decide to migrate without history how can I do it?
Thanks.
git-tfs is a two-way bridge between TFS (Team Foundation Server) and git, similar to git-svn. It fetches TFS commits into a git repository, and lets you push your updates back to TFS.
If you want to move code from TFVC on TFS2010 to TFVC on Azure DevOps 2019 and keep history.
You have to do the upgrade process of entire project collection.
In the case I decide to migrate without history how can I do it
You could just create corresponding new team projects and workspaces. Pull down your source code from your TFS2010 workspaces/projects. Copy and paste source code files/folders in new workspace. Then check in them back to Azure DevOps Server 2019.
We advise you keep preview TFVC repository of 2010 online but read-only to view history.
Same with Azure DevOps Service, hope this helps.
Disclaimer: I'm the last maintainer of the git-tfs tool (even if I no more work on it)
Git-tfs could be used to migrate from TFVC to git (with history and branches if your history is not too complex).
But in no way it could be used to push this history to another empty TFVC project.
So don't expect something from here.
Fun fact (not so fun for you) :
To prevent regression developing git-tfs, I created a TFVC project on Codeplex used to run smoke tests in a Continuous Integration job.
When Microsoft decided to close Codeplex, I contacted a guy working in the source control team inside Microsoft to help me migrate from Codeplex to Azure Devops (at the time called VSTS) which is the problem you try to solve.
I don't know if they put a lot of effort into this but no one was able give me a solution. The only thing they think about was to use git-tfs, that I confirm you is not able to do it!
That could give you an idea of the problem you're trying to solve...
Ps: that also show that TFVC is not an enough flexible source control and their is a much higher added value to migrate to git (like nearly everyone is doing it...)

Migrating from TFS to VSTS with TFVC

My usecase:
Currently have TFS 2012 (on Prem)
Want to move to VSTS
Want to migrate only the SourceCode with history, don't need any workitems, etc.
Questions:
1. What are the tools I can use?
2. Is it mandatory to upgrade to TFS 2018 first before migrating to VSTS
If you want to migrate the source code only then you have 3 options.
The MS recommended route is to upgrade to TFS 2018 and then use the Database import feature of VSTS. This is the only way to keep using TFVC and keep the full history in tact.
You could use OpsHub however this comes with limitations as it will "replay" the history so the changeset history will reflect the time of the migration rather than the time of the original check-in. Also if you have multiple team projects then you might need to pay for the tool.
If you only want the code and you are happy considering changing version control systems from TFVC to Git then this might be the simplest option. You could use Git-TFS essentially you would clone the TFS (TFVC) repository to a local Git repository. At this point you would have a full "copy" of version control including history and branches, but in Git instead of TFVC. You could then push this up to VSTS, the only "downside" is that you would now be using Git rather than TFVC, Git is good, but different so you will want to think about that.

Migrate one single project from On-premise TFS to VSTS

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.

TFS Checkin history migration

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.

Migrate local TFS to Team Foundation Service

I am trying to migrate my local TFS server to http://tfs.visualstudio.com/. My goal is to preserve code history, work items and etc.
Does this feature exists and if it how to use it?
I've used the TFS Integration Platform to migrate between two TFS servers. The one issue you might run into is the check-in dates are reset to the day of the migration (basically what you are doing is checking in all of the code), but the original check-in date is recorded in the check-in comments.

Resources