can i use classic tfvc code (tfs) in ado service/cloud ?

Question

im using on-prem ado and i have 1 project using tfvc (tfs) classic code - i want to migrate to the cloud can i migrate this project? note that i cannot convert it to git i have classic apps using it.

Answer 1

Hello,

Welcome to Microsoft Q&A,

You can migrate an on-premises Azure DevOps Server (TFS) project using TFVC to Azure DevOps Services (cloud) — even without converting to Git. Microsoft supports TFVC in Azure DevOps Services, although Git is recommended for new projects.

• TFVC (Team Foundation Version Control) is fully supported in Azure DevOps Services, so you do not need to convert to Git.
• Your classic apps using TFVC will still work after migration.
• The project, code, history, and workspace mappings will all migrate.
• You must upgrade your on-prem server to Azure DevOps Server 2022 (or at least TFS 2017/2018), and then use the Azure DevOps Migration Tool to move to the cloud.

https://learn.microsoft.com/en-us/azure/devops/migrate/migration-overview?view=azure-devops

https://learn.microsoft.com/en-us/azure/devops/migrate/migration-test-run?view=azure-devops

Please Upvote and accept the answer if it helps!!

Answer 2

Hi Ophir,

Yes, you can absolutely migrate your TFVC project from Azure DevOps Server to Azure DevOps Services (cloud). A few things to keep in mind:

• TFVC is still supported in the cloud, so your codebase and history can come across without needing to change your setup.
• You’ll want to make sure relationships, check-in history, and permissions are preserved so nothing breaks once you’re running in the cloud.
• Large repos or projects with long histories can be tricky to move cleanly, so planning ahead for performance and data fidelity is important.

To simplify the process, you may explore OpsHub Migrator for Microsoft Azure DevOps (OM4ADO) co-built with Microsoft that supports direct TFVC migrations from Server to Services. It can help you with complex ADO migrations, preserve history and relationships, and allow phased or complete migration, no-downtime and non-disruptive moves — so your classic apps keep working while you modernize.

Hope that helps! :)