Export guide
How to export your GitHub data
Last verified: 2026-10-09 · Menu names change between plans and versions; check the vendor documentation below, and we confirm exact steps with you once you qualify.
Short answer
As a code hosting, GitHub holds commits, pull requests, code reviews and issues. You run the export yourself, from the app or through its API, after removing personal and confidential details. Nothing leaves your company until you approve it.
Export from the app
Step 1
Check licenses and ownership
Confirm the repos are yours, not client-owned, and note any open-source licenses.
Step 2
Export the organization
Org owners can request an organization migration archive, or clone each repository.
Step 3
Clone with history
git clone --mirror keeps every commit and branch.
Step 4
Check the file before sharing
Open a sample of the export, confirm the date range and record count, and flag anything personal or confidential. Don't send anything yet — we review the package together first.
Export through the API
Step 1
Create a read-only key
In Settings → Developer settings → fine-grained tokens, create an API token or app with read-only scopes. Keep it inside your company; never send it to SourceX.
Step 2
Pull pull requests, reviews and issues
Use the REST or GraphQL API to list pull requests, review comments and issues per repo.
Step 3
Pull history in batches
Page through records by date range, respecting rate limits. Save raw JSON to your own storage. Large histories can take several days.
Plan limits and formats#
- Limits and formats depend on your plan and are confirmed with you after qualification.
What to leave out#
- Names, emails, phone numbers and addresses of customers and staff
- Passwords, API keys, tokens and other credentials
- Payment card and bank details
- Attachments you haven't reviewed (they often hold IDs or contracts)
- Records covered by client NDAs, privilege or contracts that limit reuse
- Anything you mark confidential, such as pricing or strategy
Terms to check first#
- Your content is usually yours, but plan terms can limit bulk export, API use or automated access.
- Check whether your plan includes the export or API features you need before starting.
- Respect API rate limits; large exports may need to run in batches over several days.
- Don't share admin logins. You run the export yourself, with our guidance.
Vendor documentation
Related
See if your company qualifies
A short company assessment. No data uploads are needed.