summaryrefslogtreecommitdiff
path: root/doc/user/project/import
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-02-20 09:09:13 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-02-20 09:09:13 +0000
commit1ac794623a8be5dee111716a44dd04ff708f3541 (patch)
tree6c18f9fbe0bd9978bd3e8d9b083d3a0ca180686e /doc/user/project/import
parent5247fe0bef72fa922841a79d5dbefb47d95112fa (diff)
downloadgitlab-ce-1ac794623a8be5dee111716a44dd04ff708f3541.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/import')
-rw-r--r--doc/user/project/import/index.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/import/index.md b/doc/user/project/import/index.md
index 571968dd065..8fd4325b5cd 100644
--- a/doc/user/project/import/index.md
+++ b/doc/user/project/import/index.md
@@ -49,9 +49,9 @@ Docker pulls and pushes and re-run any CI pipelines to retrieve any build artifa
## Migrating between two self-hosted GitLab instances
-The best method for migrating a project from one GitLab instance to another,
+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 project](../../../raketasks/backup_restore.md),
+[back up the instance](../../../raketasks/backup_restore.md),
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),