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)与管理员用户一起使用来迁移用户.