This page details migrating GitLab data from one instance to another.
Migrating from Self-Managed to SAAS
Migrating from SAAS to Self-Managed
\ No newline at end of file
## Migrating from Self-Managed to SAAS
This details migrating from a client-managed instance to the base gitlab.com.
Before beginning with the migration you need to know these details:
- The source self-managed instance preferably should be accessible by HTTPS.
- The client must clarify which projects and groups should be migrated and preferably remove any projects/groups that will not be carried over in the migration.
- 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.
### Group/Project Migration
Starting at version 13, project and group export has been deprecated in favor of this process.
### 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.
1. From the source instance, you will need to be an Administrator or an Owner of the project. Projects will be downloaded as zip files
2. Find the project you are looking for, select on the left Settings > General > Advanced
3. Scroll down to Export Project 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, select the group you want to export projects to, and click on New Project
6. Select Import Project
7. Select GitLab export
8. Fill the details for the project
9. The project will be imported after a few minutes
