2018-03-17 18:26:18 +05:30
|
|
|
# Migrating projects to a GitLab instance
|
|
|
|
|
|
2018-12-13 13:39:08 +05:30
|
|
|
1. [From Bitbucket Cloud (aka bitbucket.org)](bitbucket.md)
|
|
|
|
|
1. [From Bitbucket Server (aka Stash)](bitbucket_server.md)
|
2018-03-17 18:26:18 +05:30
|
|
|
1. [From ClearCase](clearcase.md)
|
|
|
|
|
1. [From CVS](cvs.md)
|
|
|
|
|
1. [From FogBugz](fogbugz.md)
|
|
|
|
|
1. [From GitHub.com or GitHub Enterprise](github.md)
|
|
|
|
|
1. [From GitLab.com](gitlab_com.md)
|
|
|
|
|
1. [From Gitea](gitea.md)
|
|
|
|
|
1. [From Perforce](perforce.md)
|
|
|
|
|
1. [From SVN](svn.md)
|
2019-10-12 21:52:04 +05:30
|
|
|
1. [From TFVC](tfvc.md)
|
2018-03-27 19:54:05 +05:30
|
|
|
1. [From repo by URL](repo_by_url.md)
|
2018-11-18 11:00:15 +05:30
|
|
|
1. [By uploading a manifest file (AOSP)](manifest.md)
|
2019-07-31 22:56:46 +05:30
|
|
|
1. [From Gemnasium](gemnasium.md)
|
2019-09-04 21:01:54 +05:30
|
|
|
1. [From Phabricator](phabricator.md)
|
2018-03-17 18:26:18 +05:30
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2019-09-30 21:07:59 +05:30
|
|
|
There is also the option of [connecting your external repository to get CI/CD benefits](../../../ci/ci_cd_for_external_repos/index.md). **(PREMIUM)**
|
2019-07-31 22:56:46 +05:30
|
|
|
|
2018-03-17 18:26:18 +05:30
|
|
|
## Migrating from self-hosted GitLab to GitLab.com
|
|
|
|
|
|
2019-07-31 22:56:46 +05:30
|
|
|
If you only need to migrate git repos, you can [import each project by URL](repo_by_url.md), but issues and merge requests can't be imported.
|
2018-03-17 18:26:18 +05:30
|
|
|
|
|
|
|
|
If you want to retain all metadata like issues and merge requests, you can use
|
2019-07-31 22:56:46 +05:30
|
|
|
the [import/export feature](../settings/import_export.md) to export projects from self-hosted GitLab and import those projects into GitLab.com.
|
|
|
|
|
|
|
|
|
|
NOTE: **Note:**
|
|
|
|
|
This approach assumes all users from the self-hosted instance have already been migrated.
|
|
|
|
|
If the users haven't been migrated yet, the user conducting the import
|
|
|
|
|
will take the place of all references to the missing user(s).
|
|
|
|
|
|
2019-09-30 21:07:59 +05:30
|
|
|
If you need to migrate all data over, you can leverage our [api](../../../api/README.md) to migrate from self-hosted to GitLab.com.
|
2019-07-31 22:56:46 +05:30
|
|
|
The order of assets to migrate from a self-hosted instance to GitLab is the following:
|
|
|
|
|
|
|
|
|
|
1. [Users](../../../api/users.md)
|
|
|
|
|
1. [Groups](../../../api/groups.md)
|
|
|
|
|
1. [Projects](../../../api/projects.md)
|
|
|
|
|
1. [Project variables](../../../api/project_level_variables.md)
|
|
|
|
|
|
|
|
|
|
Keep in mind the limitations of the [import/export feature](../settings/import_export.md#exported-contents).
|
|
|
|
|
|
|
|
|
|
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.
|
2019-03-02 22:35:43 +05:30
|
|
|
|
|
|
|
|
## 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](../../../raketasks/backup_restore.md),
|
|
|
|
|
then restore it on the new server.
|
2019-07-31 22:56:46 +05:30
|
|
|
|
2019-09-30 21:07:59 +05:30
|
|
|
In the event of merging two GitLab instances together (for example, both instances have existing data on them and one can't be wiped),
|
2019-07-31 22:56:46 +05:30
|
|
|
refer to the instructions in [Migrating from self-hosted GitLab to GitLab.com](#migrating-from-self-hosted-gitlab-to-gitlabcom).
|
