TechPrufer
Get started
Microsoft
Microsoft logoMicrosoft · Feature trail

Repository Migration to GitHub

26 posts · Jan 2006 – Aug 2026

What this trail covers

This thread tracks the evolution of repository migration capabilities. Initially focusing on migrating from Visual Studio and Team Foundation Service to Git, it has expanded to include tools and processes for migrating from Visual SourceSafe to Team Foundation Server and Team Foundation Service. The goal is to provide seamless version control system transitions for developers and teams. This post announces the general availability of importing repositories from TFVC to Git, allowing migration of

All Microsoft trails
  1. Enterprise Live Migrations is now in public previewIntroduces Enterprise Live Migrations (ELM) for Azure DevOps repositories to GitHub Enterprise Cloud with data residency. ELM supports continuous synchronization of repository data, commit history, branches, tags, branch policies (converted to GitHub rulesets), and pull request metadata, comments, and user history. It allows for coordinated multi-repository migrations with a final cutover typically under 30 minutes. ELM is available via Azure DevOps CLI and web UI. It does not migrate work items, pipeline definitions, releases, wikis, test artifacts, or Azure Artifacts. It also details how Azure Pipelines can be rewired to GitHub repositories and how Azure Boards can continue to be used.
  2. Copilot Autofix for GitHub Advanced Security for Azure DevOpsIntroduced Copilot Autofix for GitHub Advanced Security for Azure DevOps, enabling AI-generated fixes for CodeQL alerts. This feature integrates with Azure DevOps to provide suggested code changes as pull requests directly from the alert surface, aiming to shorten the time from vulnerability detection to remediation. It supports all CodeQL-supported languages and a curated set of high-frequency vulnerability classes. Billing is based on AI credits consumed per fix generation, tracked via Azure Cost Management.
  3. Copilot Code Reviews for Azure ReposThis post introduces the integration of GitHub Copilot code reviews into Azure Repos pull requests. It details the technical steps for enabling the feature at the organization and repository levels, the process for initiating a Copilot review on a pull request, and the display of Copilot's comments and suggestions. It also outlines specific technical limitations and guardrails for the preview, such as repository size, number of changed files, and concurrent review limits. Furthermore, it explains the billing mechanism using GitHub AI credits and how to monitor costs in Azure Cost Management.
  4. Enterprise Live Migrations: Moving from Azure DevOps Repo to GitHub with minimal disruptionIntroduces Enterprise Live Migrations (ELM) for migrating repositories from Azure Repos to GitHub Enterprise Cloud with minimal disruption. ELM supports continuous synchronization of changes while development continues, followed by a brief cutover window (typically under 30 minutes), avoiding extended downtime. It begins with a validation step, followed by continuous sync, and concludes with a final cutover. Currently in limited public preview, with script-based migration available and a UI-based experience coming soon.
  5. How Microsoft is migrating repositories to GitHubThis post details Microsoft's internal migration of repositories from Azure DevOps to GitHub, focusing on the CAP organization's experience. It highlights the use of GitHub Enterprise Importer (GEI) and Enterprise Live Migrator (ELM) for large-scale, incremental migrations, moving over 1600 repositories and 3100 developers. The primary driver for migration is gaining earlier access to AI capabilities like GitHub Copilot Coding Agent and agentic workflows. The post also describes a hybrid approach where Azure Boards and Azure Pipelines are retained for planning and CI/CD, connected to GitHub repositories via the Azure Pipelines GitHub app and AB# syntax. It notes that customization shifts from UI extensions to APIs, Actions, and integrations in GitHub, and discusses the benefits of code discovery and multi-surface experience.
  7. Azure DevOps and GitHub: Journeying into the AI EraIntroduces Enterprise Live Migrations (ELM) as a preview feature for migrating multiple repositories from Azure DevOps to GitHub with minimal cutover downtime, allowing continued development during the migration process. Highlights Microsoft's internal migration of 1,575 repositories to GitHub Enterprise as a customer zero example, noting that 45% of pull requests now happen on GitHub. Also mentions the Azure DevOps remote MCP server for connecting agents to Azure DevOps context (work items, builds, pull requests, test plans) for agentic workflows.
  8. Azure Boards integration with GitHub CopilotThis post announces the general availability of the Azure Boards integration with GitHub Copilot, building upon the private preview. New features include the ability to select a specific branch for Copilot to target when generating changes and the display of Copilot activity status directly on Kanban cards. Future enhancements planned include the selection of custom agents and models, and REST API support for automated workflows.
  9. Azure DevOps and GitHub Repositories — Next Steps in the Path to Agentic AIThis post details the ongoing integration and migration efforts between Azure DevOps and GitHub, specifically focusing on the adoption of agentic AI capabilities. It announces the general availability of the Azure DevOps MCP Server, which enhances agentic workflows by enabling tasks such as backlog reprioritization, Epic standardization, build troubleshooting, and test plan generation. It also highlights the integration of Azure Boards with the GitHub Coding Agent (in preview), allowing work items to be assigned directly to the agent for automated coding tasks. For users remaining on Azure Repos, it points to the integration of Copilot's agentic capabilities within Visual Studio 2026 and VS Code, covering a range of development tasks. The post also mentions a new billing and licensing experience for Copilot.
  10. Azure Boards integration with GitHub Copilot (Private Preview)Introduced the ability to connect Azure Boards work items with the GitHub Copilot coding agent. Users can now create and fill out work items in Azure Boards and send them directly to GitHub Copilot for tasks such as fixing bugs, implementing incremental features, improving test coverage, updating documentation, and addressing technical debt. The integration involves sending work item details (description, repro steps, last 50 comments) to the Copilot coding agent, which generates a branch and a draft pull request automatically linked back to the work item for traceability. The status is updated on the work item upon completion, and a comment notifies the user that the pull request is ready for review. Requirements include GitHub repos, enabled Azure Boards and GitHub integration, Copilot coding agent enabled on repositories, and updated Azure Boards app permissions.
  11. Azure Boards + GitHub: Recent UpdatesThis post details recent improvements to the Azure Boards + GitHub integration. Key updates include: automatic linking of merge commits to work items upon PR completion, automatic linking of PRs to work items if the branch is linked, and automatic removal of branch links from work items once the PR is merged and the branch deleted. It also introduces the display of build status from GitHub Repos for YAML pipelines, an increase in the GitHub repository limit per Azure DevOps project from 500 to 1,000, and expanded state transition support for work items using keywords like 'Validate AB#{ID}' or state categories. Upcoming features include pull request mentions in work item comments.
  12. GitHub Copilot for Azure DevOps usersThis post details how GitHub Copilot for Business is accessible to Azure DevOps users, integrating with Visual Studio and VS Code. It highlights Copilot's functionality with Azure Repos for code suggestions, commit messages, and pull request descriptions. Additionally, it mentions Copilot's capability to generate content for Azure DevOps Wiki pages.
  13. Azure Boards, September UpdateThis post enhances the Azure Boards + GitHub integration by displaying AB# links directly in the 'Development' section of GitHub pull requests when included in the PR description, and provides clearer status updates for linked GitHub pull requests directly within the work item view, including draft status, review status, and running status checks. It also introduces new REST API endpoints to automate the addition and removal of GitHub repositories in Azure DevOps Projects, increasing the repository limit per connection from 500 to 2,000.
  14. Update on Azure Boards + GitHub IntegrationIntroduced the ability to create a GitHub branch directly from an Azure Boards work item. Enhanced the process of connecting an Azure DevOps project to a GitHub organization with improved repository search performance. AB# links now appear directly in the Development section of GitHub pull requests when used in the pull request description. Added the capability to view GitHub pull request details (draft mode, needs review, status checks) directly from the work item form. Improved AB# validation within the Azure Boards app to notify users about the validity of work item links before merging.
  15. AB links on GitHub pull request and scale improvements for large organizationsThis post announces the General Availability of an enhanced experience for linking work items to GitHub, allowing users to search and select repositories and drill down to specific pull requests or commits directly within Azure Boards. It also introduces a private preview for improved GitHub connection for large organizations (thousands of repositories) to Azure DevOps projects, addressing previous timeout issues. Additionally, a private preview feature will display AB# links directly in the Development section of GitHub pull requests when used in the PR description, providing a more intuitive experience for viewing linked work items.
  16. Azure Boards + GitHub improvements in private previewThis post announces the general availability of AB# validation for improved traceability between Azure Boards and GitHub. It also introduces a private preview for linking to GitHub Pull Requests and Commits directly from work items with a search experience, and for displaying additional pull request details (draft, review, status checks) on work items. The post clarifies that commit search is limited to the default branch and provides instructions for enrolling in the private preview.
  17. Azure Boards + GitHub Integration ImprovementsThis post details planned enhancements to the Azure Boards + GitHub integration to improve traceability for users who choose GitHub repositories. Planned improvements include: better AB#ID validation to catch invalid work item links before merging pull requests, a more streamlined experience for linking commits and pull requests by allowing search and selection instead of manual URL pasting, richer display of pull request details on work items (ID, creation date, status, check status), the ability to create a new branch from a work item in GitHub repositories (similar to Azure Repos integration), and improved scalability to connect more than 500 GitHub repositories to a single Azure DevOps project.
  18. GitHub Advanced Security for Azure DevOps public preview starts now!This post announces the public preview of GitHub Advanced Security for Azure DevOps, integrating GitHub's secret scanning, dependency scanning, and CodeQL code scanning into Azure Repos and Azure Pipelines. It details the functionality of each scanning type, emphasizing the prevention of secret exposure at push time, identification of open-source vulnerabilities, and detection of code security vulnerabilities using CodeQL. The post also outlines the pricing model and billing through Azure.
  19. Integrate security into your developer workflow with GitHub Advanced Security for Azure DevOpsThis post announces the integration of GitHub Advanced Security capabilities (secret scanning, dependency scanning, CodeQL code scanning) into Azure Repos and Azure Pipelines. It details how secret scanning prevents new exposures by blocking pushes containing secrets, how dependency scanning identifies vulnerable open-source packages and provides upgrade guidance, and how CodeQL static analysis detects code security vulnerabilities. The post also mentions upcoming integrations with Microsoft Defender for Cloud's Defender for DevOps and initiatives to minimize credential theft risks by reducing reliance on PATs and enhancing Azure AD integration.
  20. Introducing the New Pull Request Experience for Azure ReposIntroduced a new, generally available pull request experience for Azure Repos. Key enhancements include: a completion readiness summary in the rollup view to quickly assess policy status, the ability to add required reviewers per pull request, multiple iteration selection for viewing file updates, suggested changes and commit functionality directly within a pull request, auto-complete waiting on optional policies, a separate tab for changes preview on the create pull request page, a warning for wrong target branch selection, direct policy links for reviewers added by policy, the ability to view a team's membership when they are a required reviewer, an improved mobile experience, and significant performance improvements (3x initial load improvement).
  21. Improving Azure DevOps cherry-pickingIntroduced a new Azure DevOps extension called 'Multi-cherry-pick' that adds a context menu item to pull requests. This extension allows users to select multiple target branches and automatically create new topic branches for each selected branch, applying the commits from the original pull request. It also provides an option to automatically open pull requests from these new topic branches into their respective target branches. The extension aims to streamline the process of applying hotfixes or other changes to multiple release branches simultaneously.
  22. Automating Releases in GitHub through Azure PipelinesIntroduced the GitHub Release task for Azure Pipelines, enabling automation of GitHub Release creation, editing, and deletion. The task supports uploading build artifacts as release assets and automatically compiling changelogs from commit history, including commit SHA, message, and linked issues. This feature aims to streamline the release process for projects hosted on GitHub and integrated with Azure Pipelines.
  23. It has never been a better time to migrate from TFS to VSTS!Announces the general availability of the TFS Database Import Service for migrating on-premises TFS data to VSTS. Highlights improvements in speed, reliability, and ease of use, removing the need for import codes and specific queuing times. Simplifies identity mapping by making it a log for understanding import behavior. Mentions benefits of VSTS like frequent feature updates, SLA guarantees, and Azure AD single sign-on.
  24. Import repositories from TFVC to GitAnnounces the general availability of importing repositories from TFVC to Git. Users can select 'Import Repository' from the repository selector drop-down to migrate code. Options include importing individual folders or branches, or the entire TFVC repository (minus branches). Users can also import up to 180 days of history. Recommends reading whitepapers on centralized version control to Git and TFVC to Git before migration and links to feature documentation.
  25. Import your TFS Database into Visual Studio Team ServicesAnnounces the public preview of the TFS Database Import Service for Visual Studio Team Services, a high-fidelity migration service that preserves source code history, work items, builds, IDs, traceability, settings, permissions, and customizations. This service aims to enable teams to transition from on-premises TFS to VSTS over a weekend.
  26. Migrating Your Data from TFS to Visual Studio Online with New Free Utility from OpsHubThis post announces and provides a download link for the OpsHub Visual Studio Online Migration Utility, a free tool designed to help teams migrate data from on-premises Team Foundation Server (TFS) to Visual Studio Online. It details the types of data that can be migrated (version control, work items, test cases, test results, user mappings) and the TFS versions supported. It also highlights the capabilities of the commercial OpsHub Integration Platform for more complex migration and integration needs. Guidance on testing migrations and links to further resources are included.
  27. Visual Studio 2013 Team Foundation Server version control and buildThis post announces the release of Visual Studio and Team Foundation Server 2013, detailing new capabilities in version control (TFVC and Git) and TFBuild. It highlights the choice between TFVC and Git for on-premises TFS, expanded web portal collaboration for codebases, and the ability to use TFBuild to compile code in TFVC or Git projects, run PowerShell scripts in the build process, and benefit from a simpler default build process. A specific bug affecting the Queue Build dialog in VS 2013 RTM against TFS 2013 RTM is identified, and a KB article for the fix is provided.
  28. Create, Connect, and Publish using Visual Studio with GitThis post details the practical steps for using Git within Visual Studio, covering the creation of new local repositories (empty, new solutions, existing solutions), adding existing local repositories, cloning remote repositories (from TFS and third-party services), and publishing local repositories. It also introduces the 'Connect' page for managing repository connections and addresses a common error when publishing a repository without prior commits.
  29. New Visual Source Safe Upgrade Tool is Available!This post introduces a new Visual Source Safe Upgrade tool that provides a wizard-based UI for migrating Visual Source Safe repositories to Team Foundation Server 2012, 2010, or Team Foundation Service. It supports the migration of code projects, files, version history, labels, and user information.
  30. TFS Integration Tools – What is the difference between cloaking and scoping branches?This post details the difference between 'cloaking' and 'merge scope' in the context of migrating version control data using TFS Integration Tools. It explains how 'merge scope' preserves branch and merge operations within a specified path, converting branch/merge actions outside that scope to simple add/edit operations. 'Cloaking', on the other hand, filters out specific branches but may lead to migration conflicts as branch/merge actions are not automatically converted. The post provides a summary table comparing the requirements met by each approach.
  31. TFS Integration Tools – March 2012 ReleaseThis post announces the release of a new version of the TFS Integration Tools that supports Team Foundation Server 11 and Team Foundation Service. It details a substantial list of resolved bugs across general functionality, version control (VC), and work item tracking (WIT) migrations, including specific failure modes like infinite loops during changeset migration, data corruption from merge/branch operations, and issues with WIT field mapping and conflict resolution. It also highlights internal dogfooding findings related to content mismatch and slow WIT syncs.
  32. Team Foundation Service Preview – Upload Source to Your Hosted AccountThis post provides a step-by-step guide for uploading source code from Visual Studio 2010 to Team Foundation Service Preview. It covers connecting to the TFS Preview account, mapping local folders to server repositories using Source Control Explorer, adding files via drag-and-drop, selecting specific files for upload, verifying added files with a '+' sign, and finally checking in pending changes to upload the files to the cloud repository.
  33. Migrating from Visual SourceSafe to Team Foundation Source ControlThis post provides two walkthroughs for migrating from Visual SourceSafe (VSS6) to Team Foundation Source Control. The first walkthrough covers preparation steps, and the second covers the migration process itself. This is an early contribution to the repository migration capability.
  34. Preparing to Migrate from Visual SourceSafe to Team Foundation Source ControlThis post details the preparation steps and the use of the VSSConverter tool for migrating from Visual SourceSafe to Team Foundation Source Control. It outlines backing up the VSS database, identifying and resolving data integrity issues using the VSS Analyze tool, running the converter to identify potential information loss, specifying folders for migration, and creating a user mapping file. Prerequisites include Team Explorer, administrative credentials, SQL Server Express, and Visual SourceSafe 2005 or later.