nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

BitBucket Server 5.x Cloud Migration

IT TGM

Hi.

We are a very small internal dev team (Less than 5) and only use the BitBucket GIT services. We do not use or need to use and CD/CI facilities as this is an internal (non-productised) code base.

As such we have been very lax in keeping our on-prem BB Service to the latest release as the existing installation (v5.1.2) is stable and just chugs along doing what it needs to.

With the EOFL looming for Self managed BitBucket Server I have been contemplating a shift to the Cloud managed version.

However, the migration assistant requires that the installation is at least 7.0.

After reviewing the initial upgrade notes it seems to me that we could be in for a lengthy and problematic journey just to get to that point.

Is there a simple and straight-forward approach we could use to move our Projects and Repositories to the new Cloud Server without using the migration assistant?

For example could we simply clone out each repo to a local filestore and then push to a new remote host (ie. the new cloud server)?

We do not work very much within the GIT CLI and really use BitBucket as a way to ensure that the code base has a single point of truth that can be used by the other team members.

thank-you in advance

Accepted answers

Dave Theodore [Coyote Creek Consulting]

Simple answer is "no." If you don't care about the pull request history, it's not that hard to write a script to batch clone all your repos to a workstation, then batch push them in to Bitbucket Cloud. You will need to create the Projects and Repos in Bitbucket Cloud first, though. You will also need to merge or cancel any open pull requests in the repo. It gets messier if you are using LFS, but you essentially do those separately.

All comments

Dave Theodore [Coyote Creek Consulting]

IT TGM

Appreciate your reply. We actually don't have PRs at all. We are not that type of development environment. I can experiment with your suggestion. However, will the clone-push method carry over the change history, branches etc.?

thank you again

Ulrich Kuhnhardt _IzymesCo_

I second @Dave Theodore [Coyote Creek Consulting] simple approach. Git is a DVCS and the local repository is an exact copy of the remote. The idea is to clone the full repository to a local machine, just like the codebase you’d be working on and then push it to a new (Bitbucket cloud) remote. Make sure you push with

git push -u <bb_cloud_remote> —all

to get all branches across.

IT TGM

Thanks to you and @Dave Theodore [Coyote Creek Consulting]

Will try this as I think in our case it is the most direct path.

Appreciate your time.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

bitbucket

bitbucket-server

migration-customer-care