CYBBACK|for Bitbucket
Quick User Guide

Your first Bitbucket backup
in under 10 minutes.

From sign-up to an encrypted, restorable snapshot of your Bitbucket Cloud workspaces - code, pull requests, pipelines, deployments and branch rules.

AudienceDevOps & engineering leads
Reading time~ 8 minutes
Setup time~ 10 minutes
VersionEN - 2026
What you'll learn

6 steps to a production-ready backup

1
Get started

Sign up - trial or paid plan

Every plan covers every application, Bitbucket included; only the storage changes.

  1. Open cybback.com/essai-gratuit for a 14-day trial (no credit card), or pick a plan on cybback.com/tarifs.
  2. Confirm your e-mail, then open Dashboard → Bitbucket.
2
Connect Bitbucket

Create a token with the backup and restore scopes

CYBBACK reads Bitbucket with one token that holds both the read scopes (backup) and the write scopes (restore). Use an account that administers the workspace.

Option A - API token with scopes (any plan)

  1. Atlassian account settings → Security → Create API token with scopes → app Bitbucket.
  2. Backup scopes: read:user:bitbucket, read:workspace:bitbucket, read:project:bitbucket, read:repository:bitbucket, read:pullrequest:bitbucket, read:pipeline:bitbucket, read:webhook:bitbucket, read:ssh-key:bitbucket, read:permission:bitbucket.
  3. Restore scopes (write does not include read - keep the read scopes): write:repository:bitbucket, admin:repository:bitbucket, write:pullrequest:bitbucket, admin:pipeline:bitbucket, write:webhook:bitbucket.
  4. Copy the token; you will also enter the e-mail of the Atlassian account (not the Bitbucket username).

Option B - Workspace access token (Premium plan, recommended)

  1. Workspace settings → Security → Access tokens → Create access token.
  2. Backup permissions: repository, pullrequest, pipeline, webhook, project, account · restore: repository:write, repository:admin, pullrequest:write, pipeline:variable.
  3. Not tied to a person, and eligible for Bitbucket's higher (scaled) rate limits on Standard/Premium plans with 100+ users. One workspace per token.
Rate limits

With an API token Bitbucket allows 1,000 requests per hour on repository data. CYBBACK paces itself and waits on 429 answers, so the first backup of a large workspace can take several hours; the next ones only read what changed.

Paste the token into CYBBACK

  1. Open app.cybback.com/dashboard/bitbucket-backup → Settings.
  2. Choose the token type, enter the workspace IDs (from bitbucket.org/your-workspace), the e-mail (API token) and the token, then click Validate.
  3. The token is encrypted (AES-256-GCM) before being stored.
app.cybback.com/dashboard/bitbucket-backup
Dashboard
Settings
Bitbucket configurationEncrypted at rest

Token type: API token (Atlassian account) · Workspace access token

 ✓ acme-dev: 86 repositories · acme-platform: 12 repositories
3
Repository selection

Pick what to back up

Incremental forever

A repository's git bundle is rebuilt only when one of its branches or tags moved. Pull requests are read from the last watermark; the configuration is captured at every run with a frozen copy, so an older backup restores the settings of its own date.

Out of scope

Bitbucket issues and wikis were removed by Atlassian on 2026-08-20 and are not backed up.

4
Bring Your Own Bucket

Use your own S3-compatible storage

Want full data sovereignty? Point CYBBACK at your S3-compatible bucket - AWS S3, GCS, Scaleway, OVH, Wasabi, MinIO. Your data, your provider, your region.

Provision the bucket

  1. In your S3 provider, create a private bucket (no public access, versioning recommended).
  2. Create an access key / secret key with permissions limited to that bucket.
  3. Note your endpoint URL and region.

Configure CYBBACK

  1. Open Dashboard → Storage.
  2. Select My own S3 storage.
  3. Fill the form, click Test connection, then Save.
Dashboard → Storage
S3 ConfigurationEncrypted at rest
 
5
First backup

Run your first backup

  1. Back on the Dashboard tab, click Start backup. A daily schedule (05:00 Europe/Paris) is created automatically after the first backup.
  2. Follow the progress live in the history or on the Events page.
  3. A repository that fails (permissions, empty repository…) is listed with its reason under the backup - the others are still saved.
6
Restore

Restore - same or another workspace

  1. Selection. Tick a repository to restore it entirely, or open it (workspace → project → repository) and choose item by item, with « Select all (N) » on every list: branches and tags one by one (under their name, a safe restored/<date>/ prefix or a name you type), files and folders as they were at the backup date (one commit on a branch, with an optional pull request), open pull requests, branch restrictions and merge checks, default reviewers, webhooks, deploy keys, pipeline variables and schedules, deployment environments and variables, permissions, repository settings, branching model and Downloads files. « Compare with Bitbucket » shows the branches deleted or rewritten since the backup and pre-selects them.
  2. Files and folders. In the Source tab, the Restore files or folders card shows the file tree of any branch or tag as it was on the backup date: expand folders, search a path, tick files or whole folders (a ticked folder covers everything below it), then choose the branch receiving the commit (the source branch or a new branch created from a base branch, with an optional pull request). The rest of the repository is left untouched. The tree is available for backups that captured the code after this feature was released.
  3. Options. Dry run (on by default), destination per repository (the original one, another existing repository in any workspace the token reaches, or a new one), overwrite only with an explicit confirmation, target workspace, repository suffix, project key.
  4. Execution. The worker pushes each chosen ref, writes the files, recreates the configuration item by item (an error on one item never stops the others), logs every step and can be cancelled. Running the same restore again creates no duplicate. Every backup, including an incremental one that reused the previous code bundle, restores the complete state at its date.
Dashboard → Bitbucket → Restore
1. Selection
2. Options
3. Execution
Restore options2 repositories · code + branch restrictions + variables
Dry runNothing is written to Bitbucket
Create the target repository when it does not existIn the original project or the one you choose
 
What cannot be restored identically

Secured variables are recreated empty (Bitbucket never returns their value); webhook secrets must be entered again; only open pull requests are recreated - by the restore account, with the original author and date noted and the comments reposted. Merged and declined pull requests stay available in the export (JSON, CSV, HTML).

You're all set.

Need help? Our team replies within one business day on every plan.

Contact support →