diff options
Diffstat (limited to 'doc/user/project/import/index.md')
| -rw-r--r-- | doc/user/project/import/index.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/user/project/import/index.md b/doc/user/project/import/index.md index 05fd04f6e48..dcc41c6c85e 100644 --- a/doc/user/project/import/index.md +++ b/doc/user/project/import/index.md @@ -49,7 +49,7 @@ When migrating to GitLab.com, you must create users manually unless [SCIM](../.. will be used. Creating users with the API is limited to self-managed instances as it requires administrator access. -To migrate all data from self-managed to GitLab.com, you can leverage the [API](../../../api/README.md). +To migrate all data from self-managed to GitLab.com, you can leverage the [API](../../../api/index.md). Migrate the assets in this order: 1. [Groups](../../../api/groups.md) @@ -74,6 +74,10 @@ best to [back up](../../../raketasks/backup_restore.md) the existing instance and restore it on the new instance. For example, this is useful when migrating a self-managed instance from an old server to a new server. +The backups produced don't depend on the operating system running GitLab. You can therefore use +the restore method to switch between different operating system distributions or versions, as long +as the same GitLab version [is available for installation](https://docs.gitlab.com/omnibus/package-information/deprecated_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. |