If you only need code hosting then yes, there are perfect alternatives out there. If you need at least pull requests as well then things are not so nice.

Helix TeamHub looks like a good service but I'm not confident they'll keep hg support for long. Mercurial there seems to be a second-class citizen like at Bitbucket, and [their blog|https://www.perforce.com/blog/vcs/git-vs-mercurial-how-are-they-different] is not exactly reassuring either. If I were you I'd just to with sourcehut.

I am considering three solutions:

• self-hosted HG repository based on RhodeCode Enterprise. It is free for teams up to 25 - https://rhodecode.com/get-started
• HG on Helix TeamHub with mirror for OSS projects on SourceForge.net. Perforce has a strong history and also free for teams up to 5
• HG on sourcehut - feels big potential

Due to Mercurial nature, it is easy to migrate source code from one solution to another (for luck, I have used BB only for code hosting).

Yeah, I've checked out all of those. Unfortunately, it seems to me that there is no other Mercurial hosting option that would a) have a big, profitable and reputable (in my book Atlassian is losing this status pretty quickly which is a shame) company behind it with support for Mercurial for the foreseeable future, b) offer tools for code review at least as good as Bitbucket's and using concepts widely accepted in the software development world and c) offer a hosted solution for a price reasonable for this part of our toolbox.

No need to migrate to git if you like mercurial. Mercurial is till a greate tool, and there is other providers than Bitbucket out there: https://www.mercurial-scm.org/wiki/MercurialHosting

We're using Mercurial at our team primarily, and have been on Bitbucket for the last six years as a company, so this is a huge letdown. I’ve got 8 notifications yesterday about updates to such Bitbucket issues and my “neat, news coming!” was very quickly turned sour. Not to mention all this comes within a year of the same happening with HipChat...

However, if you want help moving to Git (which we might end up doing after advocating Mercurial for years...) check out this: https://lombiq.com/bitbucket-mercurial-to-git-migration We have some free and open source tools for converting repos or otherwise you can hire us to do the whole migration and train your team.

Moving this discussion to a separate issue: BCLOUD-19321

I agree 100% with cowwoc

Atlassian has committed a terrible wrong. You bought one of the few companies that delivered first-rate Mercurial hosting and killed it. If you’re not going to provide Mercurial support, the very least you could do is release this part of Bitbucket cloud to the open-source community.

After much consideration, we’ve decided to remove Mercurial support from Bitbucket Cloud and the API. Mercurial support will be officially removed on June 1, 2020.

The decision to deprecate was not easy as we knew there were customers (like yourselves) who were currently using Mercurial for versioning their code. Ultimately we concluded that sunsetting Mercurial support will allow us to singularly focus on building the best possible experience for the lions share of the market and our users.

That said, if any critical Mercurial issues arise over the coming months, please reach out to our support team. Our goal is to continue offering the same Mercurial experience you have today, until June 1, 2020.

Read on to learn more about what led to this decision, timeline, and migration resource support.

@seanfarley the new LFS experimental extension is now included with all Mercurial 4.6+ distributions. Any chance of revisiting the issue? We have a number of LargeFile repositories that we are hoping to move to migrate to Bitbucket + LFS.