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.

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.

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.