In https://gitlab.com/groups/gitlab-org/-/epics/19413+ we created the first iteration of the capability to transfer a top-level group to an organization. This epic will expand on that work to support the additional tables required to successfully transfer Cohort A. In general, any tables that is sharded by `organization_id` will require specific support in the transfer service. Some records can have their `organization_id` updated to the move the record directly to the new organization. In other cases, such as labels, we will need to make copies of the record in the new organization because other groups and projects that are staying in the old organization may rely on those records. ## Exit criteria (FY26Q4) * The ability to successfully transfer any top-level group and associated user(s) from Cohort A to a new Organization. * Work should be kept updated with the table(s) in https://gitlab.com/groups/gitlab-com/gl-infra/tenant-scale/-/wikis/Sharding-Priorities ## Current known tables that need to be supported - `fork_network_members` (and `fork_networks`? - unclear) - `personal_access_tokens` - `keys` - `authentication_events` - `labels` (copy) - `integrations` (copy) <!-- STATUS NOTE START --> ## Status 2026-03-19 <!-- Create a high level summary (optional but encouraged) --> :clock1: **total hours spent this week by all contributors**: 40 :tada: **achievements**: - https://gitlab.com/gitlab-org/gitlab/-/work_items/589232+ - https://gitlab.com/gitlab-org/gitlab/-/work_items/589237+ :issue-blocked: **blockers**: - https://gitlab.com/gitlab-org/gitlab/-/work_items/588905+ - https://gitlab.com/gitlab-org/gitlab/-/work_items/588904+ Both of these issues are blocked because the auth team aren't 100% sure how these should be migrated. \ See https://gitlab.com/gitlab-org/gitlab/-/work_items/590835+ for more context :arrow_forward: **next**: - https://gitlab.com/gitlab-org/gitlab/-/work_items/593762+ _Copied from https://gitlab.com/groups/gitlab-org/-/epics/19841#note_3172490619_ <!-- STATUS NOTE END -->