- LFS authentication
- Migrating from self-managed GitLab to GitLab.com
- Migrating from GitLab.com to self-managed GitLab
- Migrating between two self-managed GitLab instances
- Project aliases
- From Bitbucket Cloud
- From Bitbucket Server (also known as Stash)
- From ClearCase
- From CVS
- From FogBugz
- From GitHub.com or GitHub Enterprise
- From GitLab.com
- From Gitea
- From Perforce
- From SVN
- From TFVC
- From repository by URL
- By uploading a manifest file (AOSP)
- From Gemnasium
- From Phabricator
- From Jira (issues only)
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.
When importing a project that contains LFS objects, if the project has an
file with a URL host (
lfs.url) different from the repository URL host, LFS files are not downloaded.
If you only need to migrate Git repositories, you can import each project by URL. 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 to export projects from self-managed GitLab and import those projects into GitLab.com.
All GitLab user associations (such as comment author) will be changed to the user importing the project. For more information, please see the import notes.
If you need to migrate all data over, you can leverage our API to migrate from self-managed to GitLab.com. The order of assets to migrate from a self-managed instance to GitLab.com is the following:
Keep in mind the limitations of the import/export feature.
You will still need to migrate your Container Registry over a series of Docker pulls and pushes and re-run any CI pipelines to retrieve any build artifacts.
The process is essentially the same as for migrating from self-managed GitLab to GitLab.com. The main difference is that users can be created on the self-managed GitLab instance by an administrator through the UI or the users API.
The best method for migrating from one GitLab instance to another, perhaps from an old server to a new server for example, is to back up the instance, then restore it on the new server.
In the event of merging two GitLab instances together (for example, both instances have existing data on them and one can’t be wiped), refer to the instructions in Migrating from self-managed GitLab to GitLab.com.
Additionally, you can migrate users using the Users API with an administrator user.
Introduced in GitLab Premium 12.1.
When migrating repositories to GitLab and they are being accessed by other systems, it’s very useful to be able to access them using the same name especially when they are a lot. It reduces the risk of changing significant number of Git URLs in a large number of systems.
GitLab provides a functionality to help with this. In GitLab, repositories are usually accessed with a namespace and project name. It is also possible to access them via a project alias. This feature is only available on Git over SSH.
A project alias can be only created via API and only by GitLab administrators. Follow the Project Aliases API documentation for more details.
After an alias has been created for a project (such as an alias
gitlab for the
https://gitlab.com/gitlab-org/gitlab), you can clone the repository
with the alias (e.g
git clone email@example.com:gitlab.git instead of
git clone firstname.lastname@example.org:gitlab-org/gitlab.git).