GitLab Migration - Users
<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *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.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ## Add Users to Group Migration ![image](/uploads/12392e722cecd09358e969d98fef7781/image.png) (Complete) ### Problem to Solve When migrating GitLab Groups, Users have to be manually migrated first in order for objects to be mapped to users. This process presents high friction for someone migrating their data from one instance of GitLab to another and is prone to errors. ### User experience goal A Group Owner (or Admin) should be able to migrate their group including the Members from one instance to another via a single click. If any Member migration is prevented by overriding security concerns, the user should be informed. ### Proposal 1. Include group members when migrating a group - https://gitlab.com/gitlab-org/gitlab/-/issues/267949 1. Associate the users with any objects in the group - https://gitlab.com/gitlab-org/gitlab/-/issues/267950 1. Migrate Project Members - https://gitlab.com/gitlab-org/gitlab/-/issues/341886 ### Documentation * The documentation delivered in [this doc issue](https://gitlab.com/gitlab-org/gitlab/-/issues/292107) should be updated with the details of this epic's implementation.
epic