Skip to content
Update Gitlab Migrations authored by Michael Datz's avatar Michael Datz
......@@ -92,7 +92,7 @@ In the newly-created instance, you should be able to access it as an admin. This
After the migration, the issues and project will be created on the new instance, and similarly if you imported a group. Note that issues that are imported will be attributed to the importer.
## Migrating from Omnibus to Various Reference Architectures
You can scale GitLab from a single server to multiple servers able to accommodate more users. In order to migrate to reference architectures, take a backup of your installation and restore the installation on the reference architecture.
You can scale GitLab from a single server to multiple servers able to accommodate more users. In order to migrate to reference architectures, take a backup of your installation and restore the installation on the reference architecture. You can follow the instructions to do that [here](https://gitlab.com/groups/nextlink/-/wikis/Gitlab/Gitlab-Backups).
## Migrating from GitHub to GitLab
If you are migrating to a self-managed GitLab instance, you can use the GitHub import rake task detailed [here](https://docs.gitlab.com/ee/administration/raketasks/github_import.html). As in other migrations, you must have user accounts created with the same email that they have on the source GitHub instance.
......
......