- Enable or disable GitLab Group Migration
- Import your groups into GitLab
Using GitLab Group Migration, you can migrate existing top-level groups from GitLab.com or a self-managed instance. Groups can be migrated to a target instance, as a top-level group, or as a subgroup of any existing top-level group.
The following resources are migrated to the target instance:
- state (open / closed)
- start date
- due date
- epic order on boards
Any other items are not migrated.
Support for GitLab Group Migration is under development and not ready for production use. It is deployed behind a feature flag that is disabled by default. GitLab administrators with access to the GitLab Rails console can enable it.
To enable it:
To disable it:
Before you begin, ensure that the target instance of GitLab can communicate with the source over HTTPS (HTTP is not supported).
Navigate to the New Group page, either via the
+button in the top navigation bar, or the New subgroup button on an existing group’s page.
On the New Group page, select the Import group tab.
- Fill in source URL of your GitLab.
- Fill in personal access token for remote GitLab instance.
- Click “Connect instance”.
After you have authorized access to GitLab instance, you are redirected to the GitLab Group Migration importer page and your remote GitLab groups are listed.
By default, the proposed group namespaces match the names as they exist in remote instance, but based on your permissions, you can choose to edit these names before you proceed to import any of them.
Select the Import button next to any number of groups.
The Status column shows the import status of each group. You can choose to leave the page open and it will update in real-time.
Once a group has been imported, click its GitLab path to open its GitLab URL.