Team Foundation Server 2017 reaches end of support on January 11, 2027, and Azure DevOps Server 2020 left mainstream support in October 2025. How to move source control from TFVC to Git, pipelines from XAML or classic builds to YAML or GitHub Actions, and work items to a supported system.
Team Foundation Server was Microsoft's on-premises source control, build and work tracking product. TFS 2017 reaches end of support on January 11, 2027. Azure DevOps Server, its successor, has newer versions, but Azure DevOps Server 2020 moved to extended support in October 2025. Many teams on old TFS still use TFVC, its centralized version control, which modern tooling has largely left behind.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
How much history you need. Full TFVC history is slow to convert for large repositories. Many teams bring recent history into Git and keep the old server read-only for archaeology.
Branching. TFVC branches are folders; Git branches are not. Map the branches that matter and drop the rest.
Binaries. TFVC repositories often contain build outputs and third-party DLLs, which belong in package feeds or Git LFS.
Where pipelines deploy. If you deploy to AWS, GitHub Actions with OIDC roles, or CodeBuild-managed runners inside your VPC, replace stored credentials.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Azure DevOps vs GitHub in 2026: Which to Standardize On
Microsoft owns both, and new investment goes mostly to GitHub, but Azure DevOps is supported and still the better fit for some teams. Boards, Test Plans, pipelines and security compared, Azure DevOps's $6 Basic plan versus GitHub's per-user plans and per-committer security add-ons, and how to move without losing history.
Read
Git Worktrees, Now That Your Coding Agent Uses Them: How They Work and What Breaks
Claude Code runs parallel sessions and subagents in git worktrees: separate checkouts on separate branches, sharing one repository. What a worktree shares and doesn't, the one-branch rule, where Claude Code puts them and when it cleans them up, and the things that still collide: dependencies, ports, local databases and .env files.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.