Migrate from GitHub to GitLab
Moving repositories, issues, pull requests and wikis from GitHub to self-managed GitLab with the GitHub importer, mapping users and contributions, and moving Actions workflows separately.
Migrating to GitLab
Moving repositories, issues and pipelines into self-managed GitLab from other Git hosts, version control systems and CI tools.
Migrate from Bitbucket Server or Data Center to GitLab
Importing projects from Bitbucket Server or Data Center into GitLab, user contribution mapping, and sequencing the cutover for large numbers of repositories.
Migrate from Bitbucket Cloud to GitLab
Importing Bitbucket Cloud repositories and pull requests into self-managed GitLab, what the importer does not bring over, and rebuilding Bitbucket Pipelines as GitLab CI/CD.
Migrate from Gitea to GitLab
Moving Gitea repositories and issues into GitLab with the Gitea importer when a team outgrows a lightweight Git server and needs GitLab CI/CD, security scanning or compliance features.
Migrate from GitLab.com to self-managed GitLab
Moving groups and projects from GitLab.com to a self-managed instance with direct transfer: what transfers, user mapping, runners and CI/CD variables, and license tier alignment.
Migrate from Subversion to GitLab
Converting Subversion repositories to Git with git svn or reposurgeon before pushing to GitLab: author mapping, branches and tags, large binary history and running both systems during cutover.
Migrate from Perforce, TFVC or CVS to GitLab
Moving from Perforce P4, Team Foundation Version Control or CVS to GitLab given the limited importer support, history conversion choices and Git LFS for large files.
Import Jira issues into GitLab
Bringing Jira issues into GitLab issues with the Jira importer, what fields come across, and deciding between importing and keeping Jira with an integration.
Migrate from GitHub Actions to GitLab CI/CD
Rewriting GitHub Actions workflows as GitLab CI/CD pipelines: jobs, runners, reusable workflows versus includes and components, secrets and the GitLab migration guide.
Migrate from CircleCI to GitLab CI/CD
Moving CircleCI pipelines to GitLab CI/CD: orbs versus templates and components, executors versus runners, caching and contexts, following the GitLab migration guide.
Migrate from Bamboo to GitLab CI/CD
Moving Atlassian Bamboo build and deployment plans to GitLab CI/CD, mapping plans, stages and agents to pipelines and runners, following the GitLab migration guide.
Migrate from TeamCity to GitLab CI/CD
Mapping TeamCity build configurations, agents, triggers, parameters and artifacts to GitLab jobs, runners and CI/CD variables, and the planning GitLab recommends before rewriting pipelines.
Consolidate self-managed GitLab instances with direct transfer
Merging several GitLab instances into one, or moving groups between self-managed instances, with direct transfer: the admin setting to enable, what migrates, known gaps and observed durations to plan a cutover.
Mapping users and contributions after a GitLab import
How placeholder users work after importing from GitHub, Bitbucket Server, Gitea or another GitLab, how reassignment and acceptance work, and why placeholder limits matter for large migrations.
Migrate GitLab from the Linux package to the Helm chart
Moving an Omnibus GitLab onto Kubernetes: externalizing PostgreSQL, Redis and object storage first, backing up and restoring into a chart running the same version, and carrying gitlab-secrets.json into chart secrets.
Move self-managed GitLab to a new server or cloud
Relocating a Linux package GitLab with backup and restore: blocking CI job requests, maintenance mode, disabling Sidekiq cron, moving large Git data with rsync or snapshots and switching DNS without double processing.
