Org Mover - Decide how to handle data on object storage

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

• Work on this issue
• Close this issue

Background

See for more background context: #490482 (comment 2127050655).

Problem

How should we mark the tables related to data on object storage? Do they need sharding keys, or will they be exempt_from_sharding? Is there a single migration approach of all non-database content on object storage?

Proposal

• Investigate and decide how Org Mover will operate during replication and during cutover
• Investigate and decide if there are any application changes we need to make to the Rails monolith

Acceptance Criteria

• Decisions are documented in https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/migration/
• Org Mover MVC epic is aligned with these decisions. For example, if an implementation issue is needed, then open it.