@@ -6,7 +6,7 @@ Before beginning with the migration you need to know these details:
...
@@ -6,7 +6,7 @@ Before beginning with the migration you need to know these details:
- The source self-managed instance preferably should be accessible by HTTPS.
- 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 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 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).
- The client should be at the most recent version of GitLab- at the bare minimum they should be within two minor revisions of the current latest version. 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, API and file exports.
Once at the most recent version of GitLab, there are two primary methods for migrating data to SAAS, API and file exports.
