Member-only story
Journey to migrate multiple legacy projects from old legacy Microsoft Visual Source Safe (VSS) to GitHub
As a Github’s Soluton Architect who has been closely working with enterprise customers for last 2.5 years, I met customers wanting to move to GitHub for all different types of source control systems. Easiest ones are ones that are based in git, such as another GitHub repositories/organizations, GitLab, BitBucket, or Azure DevOps’s git repositories. However, for non-git based Version Control Systems, for example Subversion, Team Foundation Server (TFS), just to name a few, the migration process can be quite tricky. For git based systems, GitHub has been built multiple, official migration tools to help with the process easily. For example, we have GitHub Enterprise Importer (GEI) that can help to migrate from GitHub, BitBucket, or Azure DevOps cloud:
Even for these git based systems, things like Tasks, Project boards, and pipelines are not exactly one-to-one compatible. Nevertheless, GitHub engineering teams did a great job in converting even some of these non-available GitHub components to something similar…
