diff options
Diffstat (limited to 'doc/user/project/import/index.md')
| -rw-r--r-- | doc/user/project/import/index.md | 139 |
1 files changed, 69 insertions, 70 deletions
diff --git a/doc/user/project/import/index.md b/doc/user/project/import/index.md index 1b5a658d209..208bce90453 100644 --- a/doc/user/project/import/index.md +++ b/doc/user/project/import/index.md @@ -5,76 +5,59 @@ group: Import info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Migrate projects to a GitLab instance **(FREE)** - -See these documents to migrate to GitLab: - -- [From Bitbucket Cloud](bitbucket.md) -- [From Bitbucket Server (also known as Stash)](bitbucket_server.md) -- [From ClearCase](clearcase.md) -- [From CVS](cvs.md) -- [From FogBugz](fogbugz.md) -- [From GitHub.com or GitHub Enterprise](github.md) -- [From GitLab.com](gitlab_com.md) -- [From Gitea](gitea.md) -- [From Perforce](perforce.md) -- [From SVN](svn.md) -- [From TFVC](tfvc.md) -- [From repository by URL](repo_by_url.md) -- [By uploading a manifest file (AOSP)](manifest.md) -- [From Phabricator](phabricator.md) -- [From Jira (issues only)](jira.md) +# Import and migrate projects **(FREE)** -You can also import any Git repository through HTTP from the **New Project** page. Note that if the -repository is too large, the import can timeout. - -You can also [connect your external repository to get CI/CD benefits](../../../ci/ci_cd_for_external_repos/index.md). +If you want to bring existing projects to GitLab or copy GitLab projects to a different location, you can: -## Project import history - -You can view all project imports created by you. This list includes the following: +- Import projects from external systems using one of the [available importers](#available-project-importers). +- Migrate GitLab projects: + - Between two GitLab self-managed instances. + - Between a self-managed instance and GitLab.com in both directions. + - In the same GitLab instance. -- Source (without credentials for security reasons) -- Destination -- Status -- Error details if the import failed +For any type of source and target, you can migrate projects: -To view project import history: +- As part of a [GitLab group migration](../../group/import/index.md). You can't migrate only chosen projects, + but you can migrate many projects at once within a group. +- Using [file exports](../settings/import_export.md). With this method you can migrate projects one by one. No network + connection between instances is required. -1. Sign in to GitLab. -1. On the top bar, select **New** (**{plus}**). -1. Select **New project/repository**. -1. Select **Import project**. -1. Select **History**. +If you only need to migrate Git repositories, you can [import each project by URL](repo_by_url.md). However, you can't +import issues and merge requests this way. To retain metadata like issues and merge requests, either: - +- [Migrate projects with groups](../../group/import/index.md). +- Use [file exports](../settings/import_export.md) to import projects. -The history also includes projects created from [built-in](../working_with_projects.md#create-a-project-from-a-built-in-template) -or [custom](../working_with_projects.md#create-a-project-from-a-built-in-template) -templates. GitLab uses [import repository by URL](repo_by_url.md) -to create a new project from a template. +Keep in mind the limitations of [migrating using file exports](../settings/import_export.md#items-that-are-exported). +When migrating from self-managed to GitLab.com, user associations (such as comment author) +are changed to the user who is importing the projects. -## LFS authentication +## Available project importers -When importing a project that contains LFS objects, if the project has an [`.lfsconfig`](https://github.com/git-lfs/git-lfs/blob/master/docs/man/git-lfs-config.5.ronn) -file with a URL host (`lfs.url`) different from the repository URL host, LFS files are not downloaded. +You can import projects from: -## Migrate from self-managed GitLab to GitLab.com +- [Bitbucket Cloud](bitbucket.md) +- [Bitbucket Server (also known as Stash)](bitbucket_server.md) +- [ClearCase](clearcase.md) +- [CVS](cvs.md) +- [FogBugz](fogbugz.md) +- [GitHub.com or GitHub Enterprise](github.md) +- [GitLab.com](gitlab_com.md) +- [Gitea](gitea.md) +- [Perforce](perforce.md) +- [From SVN](https://git-scm.com/book/en/v2/Git-and-Other-Systems-Git-as-a-Client) +- [TFVC](tfvc.md) +- [Repository by URL](repo_by_url.md) +- [Uloading a manifest file (AOSP)](manifest.md) +- [Phabricator](phabricator.md) +- [Jira (issues only)](jira.md) -If you only need to migrate Git repositories, you can [import each project by URL](repo_by_url.md). -However, you can't import issues and merge requests this way. To retain all metadata like issues and -merge requests, use the [import/export feature](../settings/import_export.md) -to export projects from self-managed GitLab and import those projects into GitLab.com. All GitLab -user associations (such as comment author) are changed to the user importing the project. For more -information, see the prerequisites and important notes in these sections: +You can also import any Git repository through HTTP from the **New Project** page. Note that if the +repository is too large, the import can timeout. -- [Export a project and its data](../settings/import_export.md#export-a-project-and-its-data). -- [Import the project](../settings/import_export.md#import-a-project-and-its-data). +You can then [connect your external repository to get CI/CD benefits](../../../ci/ci_cd_for_external_repos/index.md). -NOTE: -When migrating to GitLab.com, you must create users manually unless [SCIM](../../../user/group/saml_sso/scim_setup.md) -will be used. Creating users with the API is limited to self-managed instances as it requires -administrator access. +## Migrate using the API To migrate all data from self-managed to GitLab.com, you can leverage the [API](../../../api/index.md). Migrate the assets in this order: @@ -83,17 +66,9 @@ Migrate the assets in this order: 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#items-that-are-exported). - You must still migrate your [Container Registry](../../packages/container_registry/index.md) over a series of Docker pulls and pushes. Re-run any CI pipelines to retrieve any build artifacts. -## Migrate from GitLab.com to self-managed GitLab - -The process is essentially the same as [migrating from self-managed GitLab to GitLab.com](#migrate-from-self-managed-gitlab-to-gitlabcom). -The main difference is that an administrator can create users on the self-managed GitLab instance -through the UI or the [users API](../../../api/users.md#user-creation). - ## Migrate between two self-managed GitLab instances To migrate from an existing self-managed GitLab instance to a new self-managed GitLab instance, it's @@ -105,12 +80,36 @@ The backups produced don't depend on the operating system running GitLab. You ca the restore method to switch between different operating system distributions or versions, as long as the same GitLab version [is available for installation](../../../administration/package_information/supported_os.md). -To instead merge two self-managed GitLab instances together, use the instructions in -[Migrate from self-managed GitLab to GitLab.com](#migrate-from-self-managed-gitlab-to-gitlabcom). -This method is useful when both self-managed instances have existing data that must be preserved. +Also note that administrators can use the [Users API](../../../api/users.md) to migrate users. + +## View project import history + +You can view all project imports created by you. This list includes the following: + +- Paths of source projects if projects were imported from external systems, or import method if GitLab projects were migrated. +- Paths of destination projects. +- Start date of each import. +- Status of each import. +- Error details if any errors occurred. + +To view project import history: + +1. Sign in to GitLab. +1. On the top bar, select **Create new...** (**{plus-square}**). +1. Select **New project/repository**. +1. Select **Import project**. +1. Select **History** in the upper right corner. +1. If there are any errors for a particular import, you can see them by selecting **Details**. + +The history also includes projects created from [built-in](../working_with_projects.md#create-a-project-from-a-built-in-template) +or [custom](../working_with_projects.md#create-a-project-from-a-built-in-template) +templates. GitLab uses [import repository by URL](repo_by_url.md) +to create a new project from a template. + +## LFS authentication -Also note that administrators can use the [Users API](../../../api/users.md) -to migrate users. +When importing a project that contains LFS objects, if the project has an [`.lfsconfig`](https://github.com/git-lfs/git-lfs/blob/master/docs/man/git-lfs-config.5.ronn) +file with a URL host (`lfs.url`) different from the repository URL host, LFS files are not downloaded. ## Project aliases **(PREMIUM SELF)** |