Migrating projects to a GitLab instance · Gitlab 中文文檔

# Migrating projects to a GitLab instance > 原文：[https://docs.gitlab.com/ee/user/project/import/](https://docs.gitlab.com/ee/user/project/import/) * [Migrating from self-managed GitLab to GitLab.com](#migrating-from-self-managed-gitlab-to-gitlabcom) * [Migrating from GitLab.com to self-managed GitLab](#migrating-from-gitlabcom-to-self-managed-gitlab) * [Migrating between two self-managed GitLab instances](#migrating-between-two-self-managed-gitlab-instances) # Migrating projects to a GitLab instance[](#migrating-projects-to-a-gitlab-instance "Permalink") 1. [From Bitbucket Cloud](bitbucket.html) 2. [From Bitbucket Server (also known as Stash)](bitbucket_server.html) 3. [From ClearCase](clearcase.html) 4. [From CVS](cvs.html) 5. [From FogBugz](fogbugz.html) 6. [From GitHub.com or GitHub Enterprise](github.html) 7. [From GitLab.com](gitlab_com.html) 8. [From Gitea](gitea.html) 9. [From Perforce](perforce.html) 10. [From SVN](svn.html) 11. [From TFVC](tfvc.html) 12. [From repo by URL](repo_by_url.html) 13. [By uploading a manifest file (AOSP)](manifest.html) 14. [From Gemnasium](gemnasium.html) 15. [From Phabricator](phabricator.html) 16. [From Jira (issues only)](jira.html) 除了上述特定的遷移文檔之外，您還可以從 New Project 頁面通過 HTTP 導入任何 Git 存儲庫. 請注意，如果存儲庫太大，則導入可能會超時. 還可以選擇[連接您的外部存儲庫以獲得 CI / CD 好處](../../../ci/ci_cd_for_external_repos/index.html) . ## Migrating from self-managed GitLab to GitLab.com[](#migrating-from-self-managed-gitlab-to-gitlabcom "Permalink") 如果只需要遷移 Git 倉庫，則可以[通過 URL 導入每個項目](repo_by_url.html) . 問題和合并請求無法導入. 如果要保留所有元數據（例如問題和合并請求），則可以使用[導入/導出功能](../settings/import_export.html)從自我管理的 GitLab 導出項目，并將這些項目導入 GitLab.com. 所有的 GitLab 用戶關聯（例如評論作者）都將更改為導入項目的用戶. 有關更多信息，請參閱[導入說明](../settings/import_export.html#important-notes) . 如果您需要遷移所有數據，則可以利用我們的[API](../../../api/README.html)從自我管理遷移到 GitLab.com. 從自我管理實例遷移到 GitLab.com 的資產順序如下： **注意：**遷移到 GitLab.com 時，除非要使用[SCIM，](../../../user/group/saml_sso/scim_setup.html)否則需要手動創建用戶. 使用 API??創建用戶僅限于自我管理的實例，因為它需要管理員訪問權限. 1. [Groups](../../../api/groups.html) 2. [Projects](../../../api/projects.html) 3. [Project variables](../../../api/project_level_variables.html) 請記住[導入/導出功能](../settings/import_export.html#exported-contents)的局限性. 您仍然需要通過一系列 Docker 推和推來遷移 Container Registry，并重新運行任何 CI 管道以檢索任何構建工件. ## Migrating from GitLab.com to self-managed GitLab[](#migrating-from-gitlabcom-to-self-managed-gitlab "Permalink") 該過程與[從自我管理的 GitLab 遷移到 GitLab.com](#migrating-from-self-managed-gitlab-to-gitlabcom)的過程基本相同. 主要區別在于，管理員可以通過 UI 或[用戶 API](../../../api/users.html#user-creation)在自助 GitLab 實例上創建[用戶](../../../api/users.html#user-creation) . ## Migrating between two self-managed GitLab instances[](#migrating-between-two-self-managed-gitlab-instances "Permalink") 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](../../../raketasks/backup_restore.html), then restore it on the new server. 如果將兩個 GitLab 實例合并在一起（例如，兩個實例上都有現有數據，并且不能擦除），請參閱[從自我管理的 GitLab 遷移到 GitLab.com 中的說明](#migrating-from-self-managed-gitlab-to-gitlabcom) . 此外，您可以將用戶[API](../../../api/users.html)與管理員用戶一起使用來遷移用戶.