<!-- * Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/gitlab-docs/issues/ * For information about documentation content and process, see https://docs.gitlab.com/ee/development/documentation/ --> ### Problem to solve We have two options for customers looking to migrate their GitLab data to new infrastructure - Geo and Backup/Restore. The Geo use case is not currently documented but we do have an [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388863) to address this. The backup/restore instructions are documents under the [migrated to a new server](https://docs.gitlab.com/ee/administration/backup_restore/index.html#migrate-to-a-new-server) section in the backup documents. ### Proposal We should create a new page `Migrate data` and consolidate the documentation under this page presenting the reader with both Geo and backup/restore options along with the benefits and drawbacks of each approach. ### Who can address the issue Anyone with knowledge of Geo and Backup/Restore.