带历史记录的TFVC代码从TFS迁移至VSTS：替代工具咨询

Great question! I’ve helped many teams navigate TFVC migrations from on-prem TFS to Azure DevOps (formerly VSTS) while preserving full history, and while OpsHub is a solid choice, there are several other reliable options—including official tools and community-driven solutions—to consider:

Built-in Azure DevOps TFVC Import Tool #

This is my go-to recommendation for most straightforward migrations, since it’s officially supported by Microsoft and requires no third-party software. Here’s what you need to know:

• It lets you directly import an on-prem TFVC repository into Azure DevOps, preserving all history, branches, labels, and check-in comments.
• You can initiate the import directly from your Azure DevOps project’s Repos section (look for the "Import repository" option).
• Note: While it handles code history well, you’ll need to separately migrate permissions and work item associations if those are critical to your workflow.

Azure DevOps Migration Tools (Community-Driven) #

If you need more flexibility—like migrating work items alongside TFVC history, handling complex branching structures, or customizing migration rules—this open-source tool is a powerhouse:

• Supports both TFVC-to-TFVC and TFVC-to-Git migrations, so you can even switch version control systems mid-migration if needed.
• It’s highly configurable via JSON files, letting you map users, filter historical commits, and preserve links between code changes and work items.
• The community actively maintains it, so you’ll find plenty of documentation and troubleshooting help in GitHub issues.

Git-TF (Microsoft Open Source) #

If your team is considering switching from TFVC to Git (a common long-term move for many Azure DevOps users), Git-TF is a lightweight option to migrate TFVC history to Git:

• Use commands like git tf clone to pull full TFVC history into a local Git repo, which you can then push to Azure DevOps Git.
• It preserves commit history, branch structure, and even check-in notes as Git commit messages.
• While it’s not actively updated anymore, it still works reliably for most TFVC-to-Git migration scenarios.

Third-Party Enterprise Tools #

For enterprise-scale migrations with strict compliance or complex requirements, specialized third-party tools are available:

• Rocket Software Migration Tools: Offers end-to-end migration for TFVC, including permission mapping, large file handling, and post-migration validation.
• CloudMigrator: Focuses on seamless cloud migrations, with support for TFVC history preservation and integration with Azure DevOps security policies.

Quick Migration Tips #

• Always run a test migration first to validate history preservation and catch any issues before moving production code.
• Back up your on-prem TFS repository before starting the migration—better safe than sorry!
• For large repositories, consider splitting the migration into smaller chunks to avoid timeouts or performance issues.

内容的提问来源于stack exchange，提问作者Martin Nilsson