### Summary The Geo checksumming feature generates a checksum on the primary site, and the secondary site does the same for its content. The checksums are compared to verify that the data was copied over correctly. Since the Org Mover will perform a similar operation to Geo, this is a prerequisite for the Org Mover to ensure the data was not corrupted in transit and at rest when moved to a cell. ### Proposal Given that Geo will be enabled on GitLab.com for the Org Mover to transfer non-PG data, we need to adapt the Geo checksumming feature to decouple the verification feature flags from the replication feature flags. This way, we can toggle verification separately from replication and turn off the replication on GitLab.com for now. Completion of this effort also gives us the ability to selectively sync by organization. ### Exit Criteria * [x] Organizations can be selectively synced and verified with Geo * [x] All verification/checksumming data is migrated to the state tables ### Participants * `@dbalexandre` * `@mkozono` * `@nsilva5` * `@s_murray` ### Dependencies <!-- STATUS NOTE START --> ## Status 2026-02-03 :clock1: **total hours spent this week by all contributors**: 35 :tada: **achievements**: - The GDK POC works locally https://gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/5555#note_3053642214 :arrow_forward: **next**: - Publish a quick video walkthrough of the POC _Copied from https://gitlab.com/groups/gitlab-org/-/epics/14631#note_3053400485_ <!-- STATUS NOTE END -->