Commit b3159e08 authored by John Long's avatar John Long Committed by Mike Jang

Add clarification to migration from self-hosted to GitLab.com docs

See merge request gitlab-org/gitlab!26398
parent dc9dd4f4
...@@ -29,15 +29,14 @@ If you only need to migrate Git repos, you can [import each project by URL](repo ...@@ -29,15 +29,14 @@ If you only need to migrate Git repos, you can [import each project by URL](repo
If you want to retain all metadata like issues and merge requests, you can use If you want to retain all metadata like issues and merge requests, you can use
the [import/export feature](../settings/import_export.md) to export projects from self-managed GitLab and import those projects into GitLab.com. the [import/export feature](../settings/import_export.md) to export projects from self-managed GitLab and import those projects into GitLab.com.
NOTE: **Note:** 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](../settings/import_export.md#important-notes).
This approach assumes all users from the self-managed 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).
If you need to migrate all data over, you can leverage our [API](../../../api/README.md) to migrate from self-managed to GitLab.com. If you need to migrate all data over, you can leverage our [API](../../../api/README.md) 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: The order of assets to migrate from a self-managed instance to GitLab.com is the following:
1. [Users](../../../api/users.md) NOTE: **Note:**
When migrating to GitLab.com, users would need to be manually created unless [SCIM](../../../user/group/saml_sso/scim_setup.md) is going to be used. Creating users with the API is limited to self-hosted instances as it requires administrator access.
1. [Groups](../../../api/groups.md) 1. [Groups](../../../api/groups.md)
1. [Projects](../../../api/projects.md) 1. [Projects](../../../api/projects.md)
1. [Project variables](../../../api/project_level_variables.md) 1. [Project variables](../../../api/project_level_variables.md)
...@@ -55,4 +54,6 @@ perhaps from an old server to a new server for example, is to ...@@ -55,4 +54,6 @@ perhaps from an old server to a new server for example, is to
then restore it on the new server. 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), 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](#migrating-from-self-managed-gitlab-to-gitlabcom). refer to the instructions in [Migrating from self-hosted GitLab to GitLab.com](#migrating-from-self-hosted-gitlab-to-gitlabcom).
Additionally, you can migrate users using the [Users API](../../../api/users.md) with an admin user.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment