Purpose

• The purpose of this knowledge article is to supplement existing articles for transferring data from one repository to another and to explain the recommended process behind "merging" workspaces in Bitbucket Cloud
• At this stage, formal merge functionality is not yet possible within Bitbucket Cloud, so the process detailed below serves as a workaround for this limitation
• There is a feature request logged with our developer team to implement merge functionality within the product, please feel free to Watch it for future updates and Vote for it to improve its visibility with respect to our policies concerning feature implementation

Procedure

In the steps outlined below, WorkspaceA refers to the old workspace and WorkspaceB is the new workspace that you wish to keep.

1. If you wish to preserve the WorkspaceID of WorkspaceA and use it on the new workspace immediately (otherwise skip to Step 2), it is important to change the WorkspaceID first (and your username if it's a personal workspace) so that the WorkspaceID is free for usage on WorkspaceB.
   As per our documentation, any deleted workspace takes 30 days to fully delete and release its associated WorkspaceID for usage.
   Once you have renamed WorkspaceA, you can then shift its WorkspaceID over to WorkspaceB by following the same rename process. This is needed so that you do not need to wait for the aforementioned 30-day period after the deletion of WorkspaceA to use its WorkspaceID on WorkspaceB.
   
   
2. Proceed with transferring any repositories and user groups that you may need from WorkspaceA to WorkspaceB.
   
   
3. Once you have finished transferring the repositories across, it is now safe to delete WorkspaceA and begin using WorkspaceB as your newly consolidated workspace.