Cross-recovery

This article outlines the cross-recovery options for GitHub.

Cross-recovery allows you to restore repositories, issues, pull requests, and other metadata to a separate GitHub organization or another supported Git platform, ensuring resilient disaster recovery and seamless cross-environment migration.

---

Available Git platforms

In general, GitProtect allows you to restore data across all supported DevOps platforms. Different vendors provide various types of metadata, which may not be common to all providers. As a result, during the restore process, some metadata might not be available for restoration.

The table below outlines protected GitHub metadata and where it can be restored.

Metadata	GitHub	Azure DevOps	Bitbucket	Bitbucket DC	GitHub Enterprise	GitLab
Repository	✅	✅	✅	✅	✅	✅
Wiki	✅	✅	✅	❌	✅	✅
Issues (open)	✅	❌	✅	❌	✅	✅
Issues (closed)	✅	❌	❌	❌	✅	✅
Issue Comments	✅	❌	✅	❌	✅	✅
Deployment Keys	✅	❌	✅	❌	✅	✅
Pull Requests (open)	✅	✅	✅	✅	✅	✅
Pull Requests (closed)	✅	❌	❌	❌	✅	✅
Pull Requests Comments	✅	✅	✅	❌	✅	✅
Webhooks	✅	❌	❌	❌	❌	❌
Milestones	✅	❌	❌	❌	✅	✅
Labels	✅	✅	❌	❌	✅	✅
Pipelines	✅	❌	❌	❌	❌	❌
LFS	✅	✅	✅	✅	✅	✅
Tag	✅	✅	✅	✅	✅	✅
Releases	✅	❌	❌	❌	✅	❌
Collaborators	✅	❌	❌	❌	❌	❌
Commits	✅	✅	✅	✅	✅	✅
Branches	✅	✅	✅	✅	✅	✅
Projects (classic)	✅	❌	❌	❌	✅	❌
Projects (v2)	✅	❌	❌	❌	❌	❌
Teams	✅	❌	❌	❌	❌	❌
Additional Data	✅	❌	✅	❌	✅	✅
Release Assets	✅	❌	❌	❌	✅	❌
Dependabot Settings	✅	❌	❌	❌	❌	❌
Commit Comments	✅	❌	❌	❌	✅	❌
Branch Protection Rules	✅	❌	❌	❌	✅	❌

---

Useful links and items

Cross-recovery for DevOps organizations