Symptoms
Which options are available for migrating live instances to newer process definition version?
Diagnoses
Normally you should design your process in such a way that LIM is not required. I.e. never embed literal values in a workflow. If an email address or destination assignment is entered literally, you are stuck. If instead, the value for either of these is loaded from an external configuration table, or role management mechanism (e.g. a settings table in a database), then the value is easily corrected. You will then need to use Process Instance Management to GOTO the activity fresh so it will instantiate again and then load the corrected value. Also noting prevents you to complete old versions and then deploy new one for use. Unless you have that hardcoded wrong value which prevent you from completing process instance on old definition.
Community tools are not supported by K2 support. You can ask questions about them on Community and get responses there. From what I heard that community tool works fine for simple processes but I can recommend or guarantee you anything. LIM requires you to write custom code so this is not something support can help you with either.
But if you ask more specific questions I will try to reply. We can have Lync call and discuss. But essentially all I can tell you from support perspective is this:
There is not much options when it comes to "in-flight" process migration also known as live instance migration.
1) You supposed to complete instances before deploying new version and the only thing you can in certain scenarios is Repairing processes in error state option available in Visual Studio.
Outline of the Retry process:
You can use the Process Management view in Visual Studio to repair and redeploy a particular process instance in error to a new version of the process:
-Open Visual Studio on the machine where the K2 Workflow project resides.
-Select View > K2 Process Management
-In the tree view on the left drill down to the desired Error Profile
-In the right-hand pane select the process instance in error and click the Open button.
-This will open the K2 project/process and you can make the necessary changes to correct the problem.
-Save the project.
-Navigate back to the Process Management tab and click the "Redeploy" button
-Enter a 'Repair Label' and 'Repair Description' as desired and click OK to redeploy the process.
The newly deployed process will only be applicable to the process instance(s) being repaired. Note that this will not change the default version of the process either.
Links to documentation:
https://help.k2.com/onlinehelp/k2blackpearl/userguide/4.6.11/webframe.html#Reference-ST-Error_Repair.html
2) There is a tool on the K2 Underground that was designed and created by the K2 community to migrate running instances to a newer version.
This tool can be found here:
http://www.k2underground.com/groups/process_version_migration_utility/default.aspx
Please keep in mind that this tool is not supported by K2 Support, so you use it at your own risk.
3) You can utilize K2 Live Instance Management API, which provides methods for on-the-fly or live instance management. Keep in mind that this requires custom development against K2 and your custom code issues are not covered by K2 support. You can consider to engage with K2 Professional Service to get assistance with writing custom code for K2.
You can find details regarding the LIM API here:
https://help.k2.com/onlinehelp/k2blackpearl/devref/4.6.11/default.htm#Live_Instance_Management.html
Before attempting to write any code which uses LIM API make sure to familiarize yourself with notes about process design evaluation at runtime:
https://help.k2.com/onlinehelp/k2blackpearl/devref/4.6.11/default.htm#Important_Notes.html
Developers should pay careful attention to the list of supported and unsupported changes when migrating between process versions. A rough guide is that REMOVING of items from workflow definitions are NOT supported, while ADDING items to workflow definitions are generally supported.
Resolution
Possible options and considerations listed above.
