@@ -9,14 +9,20 @@ Before beginning with the migration you need to know these details:
- 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.
### Group Migration
### 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.
2. On the destination instance, select the group you want to export groups to, and click on New Group
2. On the destination instance, select the group you want to export groups to, and click on New Group.
3. Select Import Group
5. Fill the details for the group, including the https URL and access token.
5. Fill in the details for the group, including the https URL and access token.
6. The group will be imported after a few minutes.
### Group Migration (File Export)
1. On the source instance, go to the group and select Settings > General > Advanced > Export Group. This downloads the compressed group to your computer.
2. On the destination instance, select the group you want to export groups to, and click on New Group.
3. Select Import Group
5. Fill in the details for the group and select the group file on your local computer.
6. The group will be imported after a few minutes.
### Group/Project 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
