Switching Between RhodeCode Enterprise and RhodeCode Community


If you are using RhodeCode Enterprise (2.x or 3.x), you will need to upgrade to the latest version before proceeding. See Upgrade RhodeCode Enterprise. You can then switch between RhodeCode Enterprise and RhodeCode Community editions by following the instructions below.

RhodeCode Control provides an easy way to switch between RhodeCode Enterprise and RhodeCode Community editions using the rccontrol import functionality.

If you’re currently using the Community edition and your setup looks similar to this:

$ rccontrol status

 - NAME: community-1
 - TYPE: Community
 - VERSION: 4.4.1
 - VCS: vcsserver-1
 - URL:

 - NAME: vcsserver-1
 - TYPE: VCSServer
 - VERSION: 4.4.1
 - URL:

…then you can migrate by importing your current community-1 instance as an Enterprise instance.

You’ll need to stop the currently running instance and import it into the new instance, for example:

$ rccontrol stop community-1
$ rccontrol import Enterprise ~/.rccontrol/community-1/rhodecode.ini

Or if moving from the EE to the CE edition:

$ rccontrol stop enterprise-1
$ rccontrol import Community ~/.rccontrol/enterprise-1/rhodecode.ini


Only basic configuration options are moved between the imported instances. Please adjust the rhodecode.ini file after import based on the old values. It’s also possible to use the old rhodecode.ini copy. There’s just 1 changed that needs to be done based on edition. Find and change inside rhodecode.ini:

# For EE edition
use = egg:rhodecode-enterprise-ee
# For CE edition
use = egg:rhodecode-enterprise-ce

After the import has completed, please check if imported instance is running. It’s safe to keep the old instance (in stopped state) for a while as a backup in case of any problems, or in case you decide to stick to the previously used edition. In case of any troubles please check the logs located inside ~/.rccontrol/community-1/ or ~/.rccontrol/enterprise-1/

It’s required to generate new ssh-keys if you use them. Please go to Admin ‣ Setting ‣ Permissions. and use Update SSH keys file

When you decided the migration is finished you can remove your old instance of enterprise-1 or community-1:

$ rccontrol uninstall community-1

Or if moving from the EE to the CE edition:

$ rccontrol uninstall enterprise-1


We recommend backing up the ~/.rccontrol/enterprise-1 or ~/.rccontrol/community-1 directory in case there’s some left over custom files. If you are using sqlite, please make sure to backup, and move your database file before uninstalling an instance. Usually imported instance points to the sqlite database in old location. It’s recommended to adjust the ~/.rccontrol/community-1/rhodecode.ini and point it to new location.