Skip to content
GitLab
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Changes
Page history
Update Gitlab Migrations
authored
Nov 21, 2022
by
Michael Datz
Show whitespace changes
Inline
Side-by-side
Gitlab/Gitlab-Migrations.md
View page @
ce0ba618
...
@@ -27,7 +27,18 @@ If the clients' self-managed instance is not accessible by HTTPS, you must follo
...
@@ -27,7 +27,18 @@ If the clients' self-managed instance is not accessible by HTTPS, you must follo
5.
On the destination instance, select the group you want to export project/group to, and click on New Project
5.
On the destination instance, select the group you want to export project/group to, and click on New Project
6.
Select Import Project
6.
Select Import Project
7.
Select GitLab export
7.
Select GitLab export
8.
Fill the details for the project/group
8.
Fill
in
the details for the project/group
9.
The project will be imported after a few minutes
9.
The project will be imported after a few minutes
## Migrating from SAAS to Self-Managed
## Migrating from SAAS to Self-Managed
This details migrating from gitlab.com to a self-manged VM.
Before beginning with the migration you need to know these details:
-
The client must specify which cloud they wish to host their instance in.
-
You must have admin access to the target instance
### Group/Project Import
In the newly-created instance, you should be able to access as an admin. This allows you to use the project and group import tool.
1.
On the target instance, select New Project.
2.
Select Gitlab.com
3.
Fill in the details for the project
4.
The project will be imported after a few minutes
\ No newline at end of file