ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Manits Migration

Added by Terence Miller at 2011-10-14 09:59 am

hello everybody!

I want to migrate from Mantis. I found the destructive script but i need a non-destructive one (the Perl-Script doesn't work either). First question: why does the destructive script delete all data from the exsisting DB and why does it need a default redmine configuration? Why not inserting the issues, projects... and done. Why deleting the existing one? Are there problems with project, bug-id generation in the database? Can't ActiveRecord guarantee unique IDs?

I intend to change the script so it is non-destructive. And i only need to insert the issues with attachments and assigned_to-Users.
Projects, Users... are already in my DB.

Thanks in advance!!


Replies (3)

RE: Manits Migration - Added by Felix Schäfer at 2011-10-15 10:40 am

The mantis migration script is a relique from the Redmine side of the code, I don't think either of us devs have ever administered a mantis install, much less migrated one over.

I personally don't have a clue what the migration script does or why it does it. If you find any bugs, we might be able to help you fix it and commit the result to the core, but I'm afraid we can't do much more than that, sorry.

RE: Manits Migration - Added by Terence Miller at 2011-10-15 12:11 pm

The script i am talking is not that old. http://blog.foaa.de/2010/04/non-destructive-migration-from-mantis-to-redmine/
Yes it shall work for redmine, but so for chiliproject.

Wee need to migrate mantis database to redmine 1.2.1 install and the script is no compatible.
So all other scripts we found need a clear install (no projects, no issues) and can't handle existing projetcs or issues. We think the problem of most of that scripts is that the id generator for keys in the scripts can't handle to find secure ids, which not already exists in a non empty db.

RE: Manits Migration - Added by Felix Schäfer at 2011-10-17 03:53 pm

Terence Miller wrote:

The script i am talking is not that old. http://blog.foaa.de/2010/04/non-destructive-migration-from-mantis-to-redmine/
Yes it shall work for redmine, but so for chiliproject.

Sorry, but you should contact the author for that one.

Wee need to migrate mantis database to redmine 1.2.1 install and the script is no compatible.
So all other scripts we found need a clear install (no projects, no issues) and can't handle existing projetcs or issues. We think the problem of most of that scripts is that the id generator for keys in the scripts can't handle to find secure ids, which not already exists in a non empty db.

Again, as I said, we don't have the manpower to go after a full-fledged importer for mantis, sorry.

If you need help with getting the mantis migrated, there's also third-party commercial support (disclaimer: I work for finnlabs), see Commercial Offerings here and Commercial Offerings on redmine.org.

(1-3/3)