Skip to content

GitLab Migration - Rearrange groups and projects during migration

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem to Solve

When migrating entire group and project structures between GitLab instances, there is often a need to move projects from one group to another and/or change the (sub)group tree structure. Some projects would need to be imported into another group. This is not something that can currently be done. The workaround for this is to do the moves before or after the migration using the UI.

Proposed Solution

Create a user experience that allows the user to view and modify the group/project tree structure before the migration, so that the destination instance reflects the new arrangement after the migration.

Outstanding questions

Before this proposal is implemented, we would need to figure out the desired behavior when it comes to epics, group-level labels, inherited settings/permissions/metadata. Changing the (parent) group for a project of a subgroup may require that some of these also change, which may be unintended and not obvious.

Docs

Following documentation should be updated with the fields added in this issue:

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖