Hi all, my company is at long last looking into upgrading Spiratest from the ancient 3.2 to the new & shiny v5.0 in the very near future. I've had a trawl through documentation as well as the knowledge base & forums and have found info describing the upgrade from 4.2 to 5.0 and I know that there are DB changes between 4.x & 5.0, I also assume that there were changes between 3.2 & 4.x. We have been using Spiratest for about 5 years, although ive only been with the company for 2 years. During that time the Upgrade has been discussed several times & then parked due to Timescales, Resource & Risk. We have somewhere in the region of 50 active projects and need to retain our existing Test Cases, Incidents and all Workflow & User Data. From what I've seen there is not a logical upgrade path directly from 3.2 to 5.0, and so I am expecting this to be quite painful & time consuming. Is it best to plan for an upgrade from 3.2 to 4.2 and then a second upgrade from 4.2 to 5.0? Are we best going through the upgrade process or starting again with a brand new v5.0 install & then trying to import data from our current system - assuming that is possible. Can someone please confirm what the best method is going to be to perform this upgrade. Many thanks Tim en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spiratest/issues-questions/1539.aspxthreadId=1539Tim Page (tim.page@worksmart.co.uk)upgrade Hi all, my company is at long last looking into upgrading Spiratest from the ancient 3.2 to the new & shiny v5.0 in the very near future. I've had a trawl through documentation as well as the knowledge base & forums and have found info describing the upgrade from 4.2 to 5.0 and I know that there are DB changes between 4.x & 5.0, I also assume that there were changes between 3.2 & 4.x. We have been using Spiratest for about 5 years, although ive only been with the company for 2 years. During that time the Upgrade has been discussed several times & then parked due to Timescales, Resource & Risk. We have somewhere in the region of 50 active projects and need to retain our existing Test Cases, Incidents and all Workflow & User Data. From what I've seen there is not a logical upgrade path directly from 3.2 to 5.0, and so I am expecting this to be quite painful & time consuming. Is it best to plan for an upgrade from 3.2 to 4.2 and then a second upgrade from 4.2 to 5.0? Are we best going through the upgrade process or starting again with a brand new v5.0 install & then trying to import data from our current system - assuming that is possible. Can someone please confirm what the best method is going to be to perform this upgrade. Many thanks Tim Thu, 15 Sep 2016 12:10:42 -04002016-09-16T14:10:24-04:00/Support/Forum/spiratest/issues-questions/1539.aspxmessageId=2760Jim R (donotreply5@kronodesk.net) Hi Tim I just checked and as described in this article about upgrading versions , you can actually upgrade directly from v3.2 -> v5.0 without needing to install intermediate versions! I would make a backup of your system on another box, install v3.2, copy across the database and then test the direct upgrade to v5.0 and if that works do it in production. You can use the same license key for both your production box and the test box, that is allowed! Regards Adam Fri, 16 Sep 2016 02:24:06 -04002016-09-16T02:24:06-04:00/Support/Forum/spiratest/issues-questions/1539.aspx#reply2760messageId=2762Tim Page (tim.page@worksmart.co.uk) Hi Adam, Many thanksFri, 16 Sep 2016 14:10:24 -04002016-09-16T14:10:24-04:00/Support/Forum/spiratest/issues-questions/1539.aspx#reply2762