Bitbucket cleanup of free unused workspaces: what you need to know

7 min read Original article ↗

Hello Bitbucket Community. 

At Atlassian, we’re committed to delivering a secure, high-performing Bitbucket Cloud experience for all our customers. As part of our ongoing platform improvements, we’re taking steps to clean up unused or empty free workspaces.

Why are we doing this?
Removing unused free workspaces helps us:

  • Unblock critical Atlassian platform migrations and improvements

  • Ensure a smoother experience for active users

  • Adopt Atlassian platform and its security and compliance features

Who is affected?

This cleanup only applies to free Bitbucket workspaces that are empty or have been inactive/unused.

It does not apply to:

  • Any paid Bitbucket workspaces

  • Free workspaces that are actively being used 

Your Bitbucket user profile, your other active workspaces, and all your other Atlassian cloud products are not affected by this cleanup.

What’s changing?
Starting November 2025, we’ll notify administrators of empty or unused free workspaces.

      If your workspace doesn’t contain any repositories

  • It has been scheduled for deletion. No action is needed.

      If your workspace contains repositories but hasn’t been used in the past 6           months           

  • These workspaces are considered unused.
  • We’ll be deactivating these workspaces starting January 15, 2026, making all content inaccessible.
  • To keep your workspace, sign in before May 15, 2026, and click Reactivate workspace. Only workspace Admins will be able to reactivate the workspace that was deactivated due to not being used.
  • After May 15, 2026, workspaces that remain deactivated will be permanently deleted, along with their content.

      If your free workspace contains repositories and has been actively used in       the last 6 months

  • Your workspace is considered active and won’t be affected by this cleanup.
  • Your workspace is considered active if there has been activity by authenticated user in the last 6 months, for example:

    • Running git operations such as pushing or cloning repository

    • Bitbucket UI activity like creating or merging pull requests, creating branches, or updating repository or workspace Settings

    • Making changes using Bitbucket API

Note: Atlassian will attempt to notify all impacted users via email. If your information is not up to date or you have unsubscribed from Atlassian emails, you may not receive these notifications.

What if I need a workspace later?

You can create a new Bitbucket workspace anytime at admin.atlassian.com and follow the steps outline in Add a new Atlassian app or collection to your organization | Atlassian Support.

Your Bitbucket user profile, other active workspaces, and all your other Atlassian apps are not affected by this cleanup.

Thank you for being part of our community and helping us build a better Atlassian platform for everyone.


FAQ 

What is a Bitbucket workspace and where do I see it in the UI?

A workspace is the top‑level container for your Bitbucket content.
It is the part that comes after bitbucket.org/ in the URL.

  • Example: https://bitbucket.org/acmeinc
    Here, acmeinc is the workspace.
  • Inside a workspace you can have:

    • Projects

    • Repositories

    • Pipelines / runners / variables, etc.

A user can be member of several workspaces, there is not limit to the number of workspace an individual user can be a part of.

To see a list of workspace you are a member of, once you are logged in to your Bitbucket profile, click on your Avatar in the top right corner and select “All Workspaces“ on dropdown.

For more details:
What is a workspace? | Bitbucket Cloud | Atlassian Support

How do I know which of my workspaces are affected / marked for deactivation or deletion?

After January 15, 2026, we will start deactivating unused workspaces.

If your workspace is active, as described in this post, your workspace is not affected by this cleanup.

your workspace is deactivated, we will indicate it in Bitbucket UI while accessing the workspace, or show the message when user attempts CLI/API update. Admins of the workspace will be able to self-reactivate that workspace or reach out to Support to get help.

Any workspace that remains deactivated after May 15, 2026 will be deleted along with all its content.

Where is the “Reactivate workspace” button and when does it appear?

You will only see a “Reactivate workspace” option after January 15, 2026 if your workspace was deactivated . Any actively used workspace will remain active and will never see the “Reactivate workspace” option, since it is not applicable to them.

What counts as an “active” workspace? What do I need to do to take to make sure my workspace is considered active?

Your workspace is considered active if there has been authenticated user activity in the last 6 months, for example:

  • Running git operations such as pushing or cloning repository

  • Bitbucket UI activity like creating or merging pull requests, creating branches, or changing repository or workspace Settings

  • Making changes using Bitbucket API

Why are workspaces that are obviously active (daily pushes/pulls) still flagged for deletion?

Why are you deleting content in an active account / long‑lived projects? Will my old public repos be lost?

Workspaces that have daily/weekly authenticated user GIT, UI or API updates are considered active and are not flagged for deletion.

Only workspaces that do not have repositories (empty) are scheduled for deletion. Those that have been abandoned/unused, but have repositories will be deactivated with ability to reactivate before May 15, 2026 by a workspace Admin. Any workspace that remains in deactivated state after May 15, 2026, will be permanently deleted.

How do I navigate between all my workspaces and see them in one place?

To see a list of all your workspaces:

  1. Log in to Bitbucket Cloud by going to www.bitbucket.org

  2. Once logged in, click your avatar in the top‑right corner.

  3. Click All workspaces.

Or go directly to:
https://bitbucket.org/account/workspaces/

From there, you can:

  • See every workspace you’re a member of.

  • Click into a specific workspace to view its projects and repositories.

Which exact workspaces are in scope vs. out of scope for this cleanup?

  • In scope

    • Legacy Bitbucket free workspaces that are unused in the last 6 months. Or workspaces that are empty and contain no repositories

  • Out of scope for this cleanup

    • Your Atlassian and Bitbucket user

    • Active Bitbucket workspaces

    • Other Atlassian cloud products (Jira, Confluence, Trello…)

Does this cleanup mean Bitbucket is being wound down / should we migrate to another provider?

Absolutely not. This cleanup is not about shutting down Bitbucket.

In fact we are investing more into Bitbucket as a product, please read our recent blog The 2025 Year in Review (and what's coming soon) - Work Life by Atlassian

If you are currently actively using Bitbucket today please continue to do so and we hope you stay with us to benefit form all the upcoming exciting features.

Is this a one‑time cleanup, or will this keep happening?

This is a one time initiative that is necessary prior to Bitbucket being able to fully migrate to Atlassian platform and benefit from security and compliance features that Atlassian platform has to offer today and in the future.

What if I need a workspace later?

You can create a new Bitbucket workspace at anytime at admin.atlassian.com and follow the steps outlined in Add a new Atlassian app or collection to your organization | Atlassian Support.

What happens after deletion? Will workspace names be reused or repos be archived somewhere?

Once a free unused workspace is deleted after May 15, 2026, all repositories and content in that workspace are permanently deleted and cannot be recovered.

The Workspace ID is not released for 30 days after deletion. Please refer to Delete a Bitbucket Cloud workspace | Bitbucket Cloud | Atlassian Support.

After 30 days, the workspace ID is released and can be un-restrictively re-used on a first claim basis.