Migration path from Chiliproject to OpenProject
The migration largely depends on the version of ChiliProject you have currently running and the plugins you have installed.
The bare migration (without plugins) for ChiliProject will be described.
With plugins involved you will first have to check their compatibility with OpenProject. And as we just switched from rails 2.3 to rails 3.2 there will not be many plugins out there right now that fit our altered plugin API. As we are going to release a whole lot of plugins in the near future this will change soon. But plugins you might have installed will have to be addressed individually. If you have plugins installed, please us know and we will try to help you finding out what to do with them.
The approach for a bare ChiliProject to OpenProject migration (without plugins) is basically as follows. This assumes that you have a ChiliProject v3.8.0 running:
- Backup your DB or copy the DB over to a new one.
- Double check that you have a backup of your DB.
- Migrate your current database schema down to a version compatible to OpenProject.
- Install OpenProject (including running the migrations).
Since OpenProject was forked from ChiliProject it shares most of the migrations. But some of the migrations are unique to ChiliProject and will not work when running an OpenProject. Those have to be removed using the following commands (shell in the rails root directory):
rake db:migrate:down VERSION=20100217010520 rake db:migrate:down VERSION=20111025231354 rake db:migrate:down VERSION=20111125191432 rake db:migrate:down VERSION=20120131142400 rake db:migrate:down VERSION=20120131142401 rake db:migrate:down VERSION=20120320220031
Once that is done, you can install OpenProject and use the DB you just prepared. You will first have to install the OpenProject version 2.4. OpenProject 2.4 is a necessary intermediate step as we squashed some migrations from 2.4 to 3.0. We recommend to switch to OpenProject 3.0 after you installed 2.4 and tested that it works.
We hope that this helps. Please let us know if you have any additional questions or comments.