GitHub Enterprise Importer adds general availability for GitLab migrations

GitHub has made GitLab-to-GitHub migrations generally available in GitHub Enterprise Importer, giving enterprise teams a supported self-service route for moving repositories from gitlab.com and currently maintained GitLab Self-Managed installations into GitHub Enterprise Cloud.

The August 3 changelog entry says the release works through the gh gl2gh command-line extension and supports both one-off repository moves and scripted bulk migrations. That matters for larger engineering organizations because migration projects usually involve more than copying Git data: teams need repeatable runs, archive handling, and a way to stage work without turning each repository into a separate manual project.

What changed

According to GitHub, the general availability release can migrate repositories from gitlab.com and supported GitLab Self-Managed versions. Teams can stage migration archives either in GitHub-owned blob storage through the --use-github-storage option or in their own AWS S3 or Azure Blob Storage accounts. The destination scope is also clearly defined: the capability supports migrations into organizations on GitHub Enterprise Cloud on github.com and ghe.com, but it does not support migrations from GitLab to GitHub Enterprise Server.

The announcement is a practical software-platform update rather than a flashy AI feature, but it is consequential for companies standardizing developer infrastructure. A generally available migration path lowers the operational risk of consolidating repositories, especially when a business wants to centralize policy, security scanning, code review, automation, and identity controls around GitHub Enterprise Cloud.

• Source systems: gitlab.com and currently maintained GitLab Self-Managed versions.
• Destination systems: GitHub Enterprise Cloud organizations on github.com and ghe.com.
• Workflow: single repository migrations or scripted bulk migrations using the gh gl2gh extension.
• Storage options: GitHub-owned blob storage, AWS S3, or Azure Blob Storage.

For technology leaders, the key takeaway is that GitHub is turning GitLab migration into a productized enterprise workflow instead of a bespoke services engagement. The company still points customers with complex plans toward its documentation and Expert Services team, but the core tooling is now positioned as ready for self-service use by administrators who need predictable migration mechanics.

Sources

• github.blog

Cover photo by Jakub Zerdzicki on Pexels, used under the Pexels License.