Data guides · Source code
Finding and exporting your GitHub data
Inventory organization repositories, then measure complete mirrors and separately downloaded Git LFS objects in GB. Git history and repository collaboration records require different export routes.
- Unit
- GB
- Category
- Source code
- Updated
- October 2026
What it holds
Repositories contain source files, branches, tags and the sequence of commits. Issues, pull requests, reviews, releases and discussions are related records stored outside the Git repository itself.
Where GitHub shows the size
- As an organization owner, review Repositories or paginate GET /orgs/ORG/repos with credentials permitted to read private repositories. The API size field provides a quick inventory estimate.
- Run git clone --mirror REPOSITORY_URL for each repository; inside each clone run git count-objects -vH and inspect size-pack.
- Where LFS is used, run git lfs fetch --all and measure its objects separately. Sum the measured storage in GB.
Plan and admin role. Organization-wide coverage and the organization migrations API require an organization owner. Read access suffices for cloning individual repositories; token permissions must include private repositories when applicable.
Exporting the full history
- Mirror every repository with git clone --mirror REPOSITORY_URL and retrieve LFS using git lfs fetch --all. Clone repository wikis separately where present.
- For issues, pull requests, reviews and comments, start POST /orgs/ORG/migrations with the desired repository list.
- Poll until the migration state is exported, then download the tar.gz archive within seven days. Avoid exclude_attachments and exclude_releases when those records are needed.
- Personal repository owners can use the user migrations API; Enterprise Server offers ghe-migrator.
A mirror is not a copy of issues, pull requests, discussions or release assets.
Migration archives omit LFS objects, discussions and packages. Download LFS separately and treat migration output as an archive, not a supported GitHub restore package.
size-pack measures packed Git objects, not every loose object or supplementary file; measure the complete stored folders for a comprehensive disk total.
You don't need to run an export to talk to us, and there's no need to clean it first — removing personal data is part of our work.
Know roughly how much GitHub data the company has? That's enough for a first valuation.
Get your free valuation