00
Scenario
Teams migrating between Mercurial / Git / Subversion use RhodeCode for unified workflows across all three protocols.
Consolidating legacy Subversion, modernising a Mercurial code base, or running all three at once: RhodeCode hosts them under one roof, with one auth surface and one review workflow, so governance does not have to wait for the migration.
Profile
Typical deployment
Systems
Git · Mercurial · Subversion
Migration
At your own pace, or never
Binding constraint
Cannot migrate off SVN yet
Review
One workflow, all three
01a
Needs
What the platform has to do here
Four requirements this reader cannot compromise on, and the shape of answer that fails them.
01
All three systems under one permission model, with no conversion required
02
Path-level control inside monolithic Subversion repositories
03
One review workflow regardless of which system holds the code
04
Large file support on Git and Mercurial alike
Where the usual answer fails
Consolidating every repository onto one system before it can be governed means the governance never arrives — the legacy server just stays unmanaged.
02
Cases
How that works in practice
02.1
Unified repository management
Git, Mercurial and Subversion live in the same install. The same admin surface, the same auth and the same permission model apply across every protocol.
02.2
Unified team collaboration
Pull requests, inline review and approval rules work identically across all three. Reviewers learn one workflow and apply it to every repository — no per-protocol retraining.
02.3
Unified code security and permissions
One user-management surface regardless of protocol, with fine-grained access at team or individual level. IP allowlists and audit logs apply uniformly.
02.4
A no-compromise migration path
Move from Subversion to Git on your own timeline. Legacy repositories keep their history and tooling while new work lands on Git, all inside the same install.
03
Next
Tell us the constraint, not the feature list
Deployments in this shape usually turn on one binding constraint. Describe yours and we will say plainly whether RhodeCode answers it — including when it does not.