How to find and export your Bitbucket data.
Bitbucket Cloud shows each repository's size on the Size line of the Repository details page in repository settings. Add the sizes across your workspace and report the total in GB.
Where Bitbucket shows how much you have.
- Next to the repository name in the left sidebar, select More actions, then Settings.
- On Repository details, read the Size line.
- Repeat for each repository in the workspace. For an exact number, run git count-objects -v on a mirror clone and use the size-pack value.
Plan and role. Workspace admins and repository admins can open repository settings. Free workspaces are limited to 1 GB of total repository storage, and Standard and Premium repositories are limited to 4 GB each.
What to report on the Polyshares intake.
Report Bitbucket in GB. The intake also asks how many years the company has used it and how many seats it has.
Report the total across all repositories in GB. For years in use, use the oldest commit date in your main repositories. For seats, count the users on your workspace plan.
Export the full history.
- Run git clone --mirror for each repository to copy every branch, tag and commit.
- If a repository still shows the issue tracker, open Issues > Import & export and select Start export, then download the ZIP from the link shown or in the email notification.
Bitbucket warns at 2 GB and sets repositories to read only at 4 GB. Pushes are limited to 3.5 GB and .zip archive downloads to 2 GB, so use git clone rather than downloaded archives. Pull requests and their comments are not part of a clone.
Issue exports come as a ZIP with a db-2.0.json file and an attachments folder. Atlassian announced it would remove the issue tracker from Bitbucket Cloud on August 20, 2026, with export to ZIP or migration to Jira as the options, so check Jira if issues no longer appear.
The intake only needs the size, so you do not have to run an export to fill it in. You also do not need to clean or scrub an export. Polyshares handles anonymization before anything moves.
Why Bitbucket data has value for AI training.
Bitbucket repositories often sit beside Jira, so commit messages and branch names carry work item keys. That link lets code changes be matched to the tickets that asked for them.
What stays private.
We anonymize identifying details before anything moves. Polyshares does that work, so your team does not have to scrub records first.
Your company keeps ownership of its data. The license is bounded to defined material and a defined use.
Polyshares is the buyer and pays your company directly. There is no fee or commission, and Polyshares reviews the record before it makes any offer.
Common questions about Bitbucket data.
Does the Bitbucket Size line include Git LFS files?
Atlassian's size limits page does not say that LFS counts toward repository size. Check LFS usage separately and add it to your total.
Can we still export Bitbucket issues?
Atlassian announced removal of the Bitbucket Cloud issue tracker on August 20, 2026, with ZIP export or migration to Jira as the options. If your repositories still show Import & export under Issues, export now.
Are Bitbucket pull requests included in a mirror clone?
No. A clone holds branches, tags and commits. Pull request discussions stay in Bitbucket and are not part of the clone.
Source: What are the repository and file size limits?, Export or import issue data, How To: Check your repository's size and identify large files. Checked September 2026.
Related
- GitHubMirror clones for code and history, migration archives for issues and pull requests
- GitLabUsage quotas page for storage; project export includes issues and merge requests
- Azure DevOpsRepositories REST API or git count-objects for size; mirror clone and CSV work items
- All data source guidesEvery system on the Polyshares intake, grouped by category.
Put your numbers on the intake.
List your systems, their sizes and your headcount in one intake. Polyshares reviews the record and prices it. There is no fee or commission to your company.
Check your data