Org Data Migration: Support Cohort 0 Organization move
## Problem
The ask is to successfully perform the first small customer organization move.
## Scope - Assurance of reliability
After we've moved an internal organization that we actually use, we should have a good idea of the reliability of an org move of that size. Or perhaps the real move somehow revealed that we need increased assurances.
So, increase confidence of reliability to the point where a handful of customers are willing to be beta testers, and we are willing to move them.
For example we may need:
- More automated testing
- Better observability; implement metrics which indicate reliability and improve them
- Less runbook steps via improved automation or design
## Implementation Plan
In practice, the work in this epic is to:
1. Prioritize the outstanding issues (bug/feature/maintenance), especially those which were raised as a result of moving an internal organization.
2. Determine the minimum work required for us to be ready to move the first customer organization. Note that this will depend on customer appetite. Move all other work into the next epic.
3. Do that work.
## Out of scope
1. Automation sufficient to perform a high rate of moves. This will be extremely important soon after. But the first customer org move can still be a one-off.
2. Low organization downtime. This will be extremely important later, see https://gitlab.com/groups/gitlab-org/-/epics/17331+. But the first customer moves can be small orgs, which inherently requires less downtime. So we expect to find a small customer who can accept such downtime.
### Participants
## Exit Criteria
* [ ] Geo E2E Tests added
* [ ] Metrics for pre/post move identified
* [ ] Org Data Migration Code fully integrated in GDK
<!-- STATUS NOTE START -->
## Status 2026-03-05
:clock1: total hours spent this week by all contributors: 25
:arrow_forward: next:
- MR almost ready for review: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/225219+ - builds on the merged foundation MR to implement core org migration functionality
- MR in review: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/224618+ has feedback to address
- MR in development: https://gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/5677+
- Discussion progressing with cross-team input on Prometheus vs Geo dashboard alignment (https://gitlab.com/gitlab-org/gitlab/-/issues/546269+)
_Copied from https://gitlab.com/groups/gitlab-org/-/epics/17308#note_3132935844_
<!-- STATUS NOTE END -->
epic