We got the requirement of migrating SharePoint 2010 to SharePoint 2016 where the existing application is having around 15 workflows build on K2 (version 4.5). As a part of migration we migrate the content from 2010 to 2013 and 2013 to 2016. We are totally new to K2.
Is it possible to migrate from 4.5 to 4.7 by maintaining the workflow instance state? If yes, what is the procedure.
Best answer by EvanM
View originalHello,
Since your current 4.5 workflows are integrated with SP 2010, but you are moving to SP 2013/2016 you will need to rebuild those workflows to use the new SP 2013 integration. This includes a whole new service type as well as Workflow Wizards. Please refer to the below KB that describes the K2 for SharePoint 2013 integration. Also, keep in mind that the integration for K2 for SharePoint with SP 2013 and 2016 will use the same integration pieces.
SharePoint greatly changed their architecture from SP 2010 -> 2013 with the introduction of the High Trust App model. With more lightweight accessibility via 3rd party apps, K2 adapted to Microsoft's best practices and swapped our integration to make use of the new app architecure. With this change the previous SP 2010 integration was now completely different and there is no direct "migration" tool as there are a vast amount of differences. I like to think of K2 for SharePoint 2010 and K2 for SharePoint 2013/2016 as completely different parts of the product.
If you do have any workflows that were built on 4.5, but do not have the SP 2010 integration, those should work as you upgrade the K2 product itself. However, keep in mind that there might be a .NET framework update past what these workflows were originally built on. It might not be bad to rebuild these as well.
Finally, do keep in mind that with the release of K2 Five there is a completely new HTML 5 Web designer available. If you are going to rebuild your processes it might be best to do it on the new workflow designer. K2 Studio, K2 for Visual Studio, and the old Silverlight Workflow Web Designer are working their way into legacy components and will soon be deprecated.
HTH,
Evan
K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member.
Hi EvanM. Thanks for the reply.
How to carry the existing running state of workflows from source environment (version 4.5) to destination (version 4.7 or K2 five) environment? Is there any workaround? (Even if we recreate the workflows in the destination environment).
Thanks in advance.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
