Migrating projects to a GitLab instance
- From Bitbucket Cloud (aka bitbucket.org)
- From Bitbucket Server (aka Stash)
- From ClearCase
- From CVS
- From FogBugz
- From GitHub.com or GitHub Enterprise
- From GitLab.com
- From Gitea
- From Perforce
- From SVN
- From TFS
- From repo by URL
- By uploading a manifest file (AOSP)
- From Gemnasium
In addition to the specific migration documentation above, you can import any Git repository via HTTP from the New Project page. Be aware that if the repository is too large the import can timeout.
There is also the option of connecting your external repository to get CI/CD benefits.
Migrating from self-hosted GitLab to GitLab.com
You can copy your repos by changing the remote and pushing to the new server, but issues and merge requests can't be imported.
If you want to retain all metadata like issues and merge requests, you can use the import/export feature.
Migrating between two self-hosted GitLab instances
The best method for migrating a project from one GitLab instance to another, perhaps from an old server to a new server for example, is to back up the project, then restore it on the new server.