Skip to main content

I went through the forum to check similar topics and I have found some useful information. But I need to confirm some points and discuss some concerns:

 

- We have found some old topic refere that we can only upgrade K2 4.7 to K2 Five version (5.0) then upgrade to any other K2 Five higher version. But when checking K2 Five (5.3) download (as attached) It's mentioned that the installer can upgrade from K2 4.7. So, Did anyone try to do it? how was the result and faced issues if any?

 

- After migrating is all APPS, Forums, and K2 workflows are migrated successfully. SharePoint 2016 intgeration with the new upgraded K2 version.

- How we should manage the enviornment comptabilities (Windows server Versions, SQL version .... ).

 

Regards,

Ahmed


11233i70FF8FF599CBA962.png

Hi Ahmed,


 


Let me preface this by saying you should talk to your K2 account manager, or someone from the K2 Professional Services team to work out an upgrade plan that works for you.


 


As for your questions,



  • You can upgrade from 4.7 to 5.3. However my recommendation is to upgrade first to 5.0, then upgrade to 5.3. Reason for that is there are a lot of changes in between 4.7 and 5.0, and I have seen some weird situation where a direct upgrade from 4.7 to 5.3 fails, but if upgrading to 5.0 or 5.1 first, then upgrade to 5.3, it somehow works.

  • If you are doing an upgrade, all your workflows and applications should remain in tact. You should still have access to legacy tools like K2 Studio, so you should still be able to make changes to your workflows. I don't foresee any issues with your SharePoint 2016 integration. You will also need to upgrade the K2 for SharePoin app after you have upgraded your K2 environment.

  • As for Windows and MS SQL server versions, I will recommend you check the K2 compatibility matrix to find out what are the latest versions of Windows and MS SQL server that K2 requires, and upgrade your server to that version. I am not sure if you can perform an in-place upgrade of Windows and MS SQL, but most people I have seen chose to setup seperate servers with the latest versions of Windows and MS SQL, install K2 on those new servers, then shut down the old servers and perform all the necessary configurations (change host names, set ip address etc) to bring the new servers live. As long as you have the K2 database backed up and restored, all your K2 workflows and forms should remain in tact.


 


Reply