Your Crucible review history doesn't have to die in 2028

Tell us what you're running and we'll get you into the beta. The questions below help us work out our priorities, but none of them commit you to anything.

Our import tool will work against either your live Crucible instance or an XML export of the data (live is preferred for improved data fidelity). This will bring over all your historical data, and leave you set up to start doing code reviews in Review Board.

All of the following will be carried over:

• Users
• Repositories (CVS, Git, Mercurial, Perforce, and Subversion)
• Review Requests
• Diffs (including multiple iterations of patch reviews)
• Reviews and comments, mapped to the right file and line

Review Board also has a full REST API, a framework for building custom extensions, and a variety of integrations with chat, CI, and issue trackers. If you've built something on top of Crucible that you can't live without, you can almost certainly build it for Review Board.

Crucible does a few things differently from Review Board, so some aspects of the data models don't map one to one.

The biggest difference is in how reviews are structured. In Crucible, each comment can have a fully threaded discussion. Review Board groups comments into reviews, and each comment has a single threaded list of replies (like most e-mail clients). Imported discussions will keep all the comments, but the threads will be flattened down into a linear discussion.

Crucible has a lot of categorization and taxonomy for comments and state that don't have exact analogs in Review Board. We'll do our best to map these where they make sense, and we'll store the original values as extra data so you can still get them via the API.

Crucible also supports multi-repo reviews in a single object. These will be split into per-repo review requests upon import, with a master request referencing the children.

Can I keep running Crucible after May 2028?
It'll keep working. It just won't get security patches or bug fixes, and Atlassian has already stopped selling additional seats. If your organization has a security policy, SOC 2/ISO 27001 compliance needs, or a regulated audit requirement, running unpatched server software usually isn't possible.

Does Review Board support my VCS?
Review Board supports every system that Crucible does (CVS, Git, Mercurial, Perforce, Subversion) along with a few more.

Do we have to migrate to Git?
Git is great, but it's not for everyone. Review Board is built to support many different systems. If you're a multi-VCS shop, you can use them all together on the same server, keeping your review process consistent across your entire stack.

We're planning to move to Git eventually
Review Board supports Git too, so it comes with you. You can migrate your code reviews now, and continue using the same process when you migrate your source code. And Review Board will support whatever comes after Git, too.

Can Review Board run on-premises or air-gapped?
Yes, Review Board can run entirely in your environment, even in places with extremely tight security postures.