Good day Seng

The workflows can just be deployed on the K2 Five version as long as they are not built in K2.net 2003.
Note This will only be possible if you upgrade and not with a clean K2 Five installation for the legacy tool compatability only come with a K2 five upgrade. The 4.7 workflows will then continue to work on k2 Five and they can be maintained with legacy tools like Silver Light or K2 for Visual Studio.

If you would like to work with the workflows in the new workflow designer, All the workflows will have to be rebuilt. One of our K2 partners has built a tool to automate most of this process and to find the tool you may click here or follow the link below. Note that this is not a K2 Out Of The Box feature and can not be supported by K2.
Link: https://jeylabs.com/products/PowerToolzExpressForK2Five

You may follow this link that will walk you through deploying K2 4.7 workflows in K2 Five.

Link: https://help.k2.com/support-services/kbs100055

Hope this helps. If you find this information useful would you be so kind as to mark this post as a Solution of Kudo? This will show other users with relevant problems that this post contains viable information. Thank You.

Best regards
Jacques.

[K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member]

Good day  @Seng;

Please go through this post(https://community.k2.com/t5/K2-Five/Migration-to-K2-5-1/td-p/104167), 

and---(https://www.bytezoom.com/migrating-legacy-applications-to-k2-five/)

Should find the above information useful, kindly mark such as "Kudo and Accepted Solution".

Thanks & Regards;

Widson.

Hello  @Seng,

As JaquesP said all current running workflows on your production server will still continue to work unless they were built on K2 .NET 2003. To add on this I have just added a link for you to check the Comparison of capabilities between K2 4.7 Workflow Designers and K2 Five/K2 Cloud Workflow Designer: https://help.k2.com/kb002726 

Regards,

BesM

Dear Seng,

There are a couple of paths here, and I'm not 100% sure which one you are looking to follow.

Path 1. Upgrade environment from 4.7 to K2 Five, with no workflow rebuild.

As previously mentioned, as long as the workflows were not built in k2.net 2003, your 4.7 workflows will continue to run in Five. No rebuild required. This is true for all currently available "versions" of K2 Five (up to and including 5.3).

Path 2. Upgrade 4.7 or build new K2 Five environment, "convert" or rebuild workflows using new K2 Five/HTML Designer.

Again, your 4.7 workflows will continue to function. When you rebuild, you will create new workflows in the HTML Designer, which will be distinct from the old workflows. Instances started on the old workflows will need to complete against the old workflow version.

You can either build your workflows from scratch, or you can use third-party tools (such as Jeylabs PowerToolz Express) to analyze and help convert your workflows.

I hope this helps,

Gail