Finding and exporting your Bitbucket data

What it holds

Bitbucket repositories hold source code and its branches, tags and commits. Pull-request conversations and legacy issue-tracker records sit outside that Git history.

Where Bitbucket shows the size

1. Open More actions beside the repository name > Settings > Repository details.
2. Read Size and repeat across the workspace.
3. For a local cross-check, mirror the repository and run git count-objects -v; size-pack is in KiB. Add separate LFS storage where applicable.

Plan and admin role. Workspace or repository administrators can access repository settings. A clone needs repository read access.

Exporting the full history

1. Run git clone --mirror REPOSITORY_URL for every repository. Fetch LFS objects separately if used.
2. If a legacy issue tracker remains available, open Issues > Import & export > Start export and save the linked ZIP.
3. If Issues is absent, locate any migrated issue records in Jira or existing archives.

Mirrors omit pull requests and their comments. Legacy issue ZIPs contain db-2.0.json and an attachments directory.

The legacy issue tracker was scheduled for removal on August 20, 2026; availability must not be assumed.

Repository archive downloads have a 2 GB limit, pushes 3.5 GB, and repositories become read-only at 4 GB after a 2 GB warning. Free workspaces have a 1 GB aggregate repository limit.

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.