@@ -8,7 +8,7 @@ Before beginning with the migration you need to know these details:
- The client should find a way to create user accounts on gitlab.com- and the credentials should match up to their existing instance.
- The client should be at the most recent version of GitLab. If they are not, you should follow an upgrade [process](https://gitlab.com/groups/nextlink/-/wikis/Gitlab/Gitlab-Upgrades).
Once at the most recent version of GitLab, there are two primary methods for migrating data to SAAS.
Once at the most recent version of GitLab, there are two primary methods for migrating data to SAAS, API and file exports.
### Group Migration (API)
Starting at version 13, group export has been deprecated in favor of this process.
1. On the source instance, create a personal access token. Give yourself all permissions to keep things simple. Save the token to your clipboard, we will use it later.
...
...
@@ -18,22 +18,22 @@ Starting at version 13, group export has been deprecated in favor of this proces
6. The group will be imported after a few minutes.
### Group Export
If the clients' self-managed instance is not accessible by HTTPS, you must follow this process. It involves taking archive downloads of each group and project you want to migrate over. The process is generally the same for groups and projects
If the clients' self-managed instance is not accessible by HTTPS, you must follow this process. It involves taking archive downloads of each group and project you want to migrate over. The process is generally the same for groups and projects.
1. From the source instance, you will need to be an Administrator or an Owner of the project/group. The items will be downloaded as zip files.
2. Find the project/group you are looking for, select on the left Settings > General > Advanced
2. Find the project/group you are looking for, select on the left sidebar Settings > General > Advanced
3. Scroll down to Export Group and generate an export. Wait a few minutes, you may need to refresh the page.
4. Download the export and keep the archive where you can easily access it.
5. On the destination instance click on New Group
5. On the destination instance click on New Group.
6. Select Import Group
7. Select GitLab export
8. Fill in the details for the group
9. The group will be imported after a few minutes
8. Fill in the details for the group.
9. The group will be imported after a few minutes.
### Project Migration (API)
1. On the source instance, create a personal access token. Give yourself all permissions to keep things simple. Save the token to your clipboard, we will use it later.
2. On the destination instance, click on New Project.
3. Select Import Project and then Repository by URL.
5. Fill in the details for the project, including the https URL and access token.
5. Fill in the details for the project, including the HTTPS URL and access token.
6. The project will be imported after a few minutes.
