In the current version of K2 Five (5.2) and K2 Cloud (Update 6), there is no out-of-the-box way to copy/move/deploy custom workspaces from 1 environment to the next - they must be recreated from scratch, which could easily lead to human errors and confusion.
The attached SQL Server script file, and steps below, will how to copy/deploy a custom workspace to a new environment. You'll need SQL Server Management Studio and read-access to the K2 database in the source environment, and and write-access to the K2 database in the target environment.
Here are the steps:
1. Open SQL Server Management Studio (SSMS), connect to the SQL Server Instance that houses the source environment K2 database.
2. Select the "K2" database, then open the attached SQL script-file.
3. At the top o fthe scriptfile, change the name of the @customWorkspaceName variable to reflect the name of the custom workspace that you want to copy/deploy.
10. Finally, open K2 Management and make sure that the custom workspace was inserted correctly.
