News

TFS to Visual Studio Online Migration Tool Released

Data from TFS versions as far back as 2010 can be transferred.

Although a .NET developer might want to switch to Visual Studio Online for application lifecycle management (ALM), the challenge of moving data from Team Foundation Server (TFS) can be daunting. To help overcome that hurdle, Microsoft has released a migration utility that streamlines the process.

The utility springs from a collaboration with OpsHub, reports Visual Studio Online Product Manager Ed Blankenship. He writes that the utility, which is free, "handles the most common scenarios" for migration. They include version control repositories and source code files; test cases and test results; work items; and mapping between on-premises Active Directory user accounts and Microsoft Accounts used in Visual Studio Online.

The tool works with versions of TFS back to 2010, and there's no need to upgrade to the latest TFS version first. It's a step-by-step process for mapping team projects in TFS on-premises to Visual Studio Online team projects, according to Microsoft's Will Smythe.

It's recommended that developers test the migration before making it live. Smythe noted that some functionality offered in the full, paid version of OpsHub won't be available, including builds, team root history, work item queries, alerts, security and permissions, and "other types of data." He also suggested that developers keep backup copies of TFS databases handy, for data that doesn't make it through the migration.

About the Author

Keith Ward is the editor in chief of Virtualization & Cloud Review. Follow him on Twitter @VirtReviewKeith.

comments powered by Disqus

Featured

  • Mastering AI Development and Building AI Apps with GitHub Copilot

    Two Microsoft experts explain how GitHub Copilot is evolving from a coding assistant into a broader platform for building, customizing and testing AI-powered developer workflows.

  • VS Code 1.123 Adds Agent Session Sync, 1M Context Windows

    Microsoft released Visual Studio Code 1.123 on June 3, adding agent-focused features, larger model context support, integrated browser updates and a new delay for some automatic extension updates.

  • Copilot Billing Shock Hits Developers

    Developer complaints about GitHub Copilot's new usage-based billing model have centered on unexpectedly rapid AI credit consumption, and neither GitHub nor Microsoft has responded directly to the backlash, though they have previously published guidance to lessen model usage costs.

  • Hands On with GitHub Copilot App Technical Preview: Turning a Blazor Issue into a PR

    GitHub's brand-new Copilot desktop app, in technical preview, handled a small Blazor issue from planning through pull request creation, but the hands-on test also showed why developers still need to verify agent work in the running app before merging.

Subscribe on YouTube