Content
You are here:
Migrate from Redmine 2.4 to OP4
Added by Peter Harris over 9 years ago
Hi, I am trying to test out OP as a replacement for our old and creaky Redmine (v2.4).
I have read the various guides, and they all seem to indicate that I need OP2.4 for the initial migration to OP, and then upgrade OP2.4 to OP3 (and I assume on to OP4).
I do not seem to be able to find OP2.4 to install. Does anybody know where I can find it? Or is there another more direct (or indirect) route of getting my old data to OP
Thanks in advance
Peter
Replies (8)
Hi Peter,
we have a short migration guide here. I didn’t test it but it looks good.
If you have any problems with that I’m happy to help.
Best,
Jonas
Thanks Jonas.
Yes, I had read that migration guide, but I have been unable to find OpenProject 2.4 to allow the middle step of migrating from Redmine 2.4.
so far I have only been able to find the install files for OP4.
Hi Peter,
you can find the files here.
I hope that helps :)
Jonas
Hi Peter,
Did you finish the migration to OP4? I am trying to migrate from ChiliProject but I am facing other issues with the migration from OP 2.4 to OP3.0. I would like to have some feedback from your side.
The migration from OP3.0 to OP4.2 seems quite simple after the workaround of the problems from 2.4 to 3.0.
Cheers
Luis
Hi Luis,
Alas it was not a straight forward migration for us, mainly due to time available.
Ultimately, a local database head put together some sql scripts to extract from Redmine and insert directly into OP4.
Anything that we were unable to bring across using this method (of which the main was failure to bring across issue/WP status changes) we have either inserted manually or ignored. While not ideal, it has largely worked for us as we were not too far into our critical project on Redmine.
Sorry, not much help to you I am afraid.
Peter
Hi Peter,
Thank you for your prompt answer.
The main problem in my case is also the wiki history; I found that after the migration there are many duplicated rows in the table “wiki_content_journals” and some errors in one field. I also created some SQL scripts to fix the database after the migration and the wiki history is working in OP3.0.
I was hoping to find a better solution than just fixing the database after the error is there.
Your feedback is very helpful indeed; it helped me to realize that I am not the only one with this problem. I was wondering if I was doing something wrong. Now I will also check if the “issues” are migrated properly; I did not see any error until now, but I have to be sure.
Cheers
Luis
I have just been reminded by one of the team, as well as the being unable to import the status change history, we had a problem when importing issues in to work packages. For each insert into the workpackage table, there needs to be a corresponding insert into the various journal tables to match the create.
Peter
Hi Peter,
Thanks a lot for the info. I will have a look and check if the work packages were migrated properly.
Cheers
Luis