Upgrade OTRS 2.2.4 to 3.0.6 - db problems

[aedm]

Hi all,

starting from an installation of OTRS 2.2.4 already existing and well working (with over 50,000 tickets) we are trying to upgrade the system to version 3.0.6.

We went through various versions from 2.2.4 to 2.3.3 -> 2.4 -> 3.0 -> 3.0.6 to obtain a stable system, but checking the correctness of the data transferred we encountered several problems.

The most noticeable is the loss of the link between services and SLA: the table "service_sla", although correctly created, does not contain any record.

Other issues are, eg., the almost total loss of the ​"until_time" column values in the "ticket" table and the change of "create_time", "create_by", "change_time", "change_by" column values in "group_customer_user" table.

Have we done something wrong? Is there a way to prevent these problems? Which tool could we use to identify which data have been lost (they are both mysql db)?

Thanks in advance!

[jojo]

please follow the steps outlined in each of the UPGRADING files of each version

You have to upgrade

2.2 -> 2.3
2.3 -> 2.4.
2.4 -> 3.0

Actual version in 3.0 is 3.0.12 (don't use the 3.0.6). Actual OTRS version is 3.1.3

[aedm]

Hi jojo,
thanks for the answer! Do you think there may have been an error in one of the upgrades?
Is there any well known problem in 3.0.6 version?
Thank you very much!

[jojo]

if you follow the steps in all of the UPGRADING files everything will be fine.

3.0.6. won't be critical from the upgrading process, but there are a lot of Bugs and security fixes between 3.0.6 and actual 3.0.12

[aedm]

Unfortunately we think we have followed all the steps correctly...
Is there any log file where we could look for potential errors in migration?
Can you suggest us a tool to compare the original and the migrated db (both Mysql)?
Thanks again!

[Even]

We have the same problem by upgrade from 2.4 to 3.0
First we have tryed to follow the UPGRADE but it did not work properly at the end. There were some changes done on the DB and the scripts of 2.4 so we assumed that they are the cause for the issues.
Than we have installed a completely new 3.1.3. We have tryed to import the data from 2.4 or to connect the 3.1.3 OTRS to the old DB and to use the the UPGRADE procedure. In all cases we did not manage to get the old data into the new OTRS.
Any standard process for data export from 2.4.7 and import to 3.1.3?

[jojo]

you need to upgrade from

2.4 -> 3.0
and afterwards from
3.0

Following the UPGRADE files