TGNG Server/Datacenter and TGE Server/Datacenter to TGNG Cloud migration
This documentation describe a solution to migration from TGNG Server / Datacenter to TGNG Cloud.
In order to migrate from TGNG Server / Datacenter, we build a script to help migrate issues data.
We’re excited to introduce a brand new in-app feature for migrating your grid data to the Atlassian Cloud—no scripts or advanced technical skills required!
For more details, please visit Migration Feature - v2.3.0 .
Contents
TGNG Server/Datacenter → TGNG Cloud migration
Groovy Script
Prerequisites
A plugin/tool for running Groovy code is present on the instance from which the script is being run
TGNG apps installed on both Server and Cloud instances
The project from the source instance was already migrated to the target instance
All Columns in the Grid Config are made editable before running the script (can be changed after)
Please note that the script was written to be used as a sample and requires you to change the variables' values
None of the Target Grids have default rows (they can be re-added after the data is migrated)
Disclaimers
The script was developed to be run from the source Server instance.
The script is not an official solution for migration but it’s a workaround solution and should be used with care and precaution.
Guide
Make sure that all of the prerequisites above are met
Verify whether the grid fields on your Server instance have a multi-context setup
If not, configure identical Grids on the Cloud instance (+ Scopes)
If so, create an identical Grid configuration for each distinct context
Obtain valid authentication strings from both instances
Replace the placeholder authentication values as well as instance URLs with valid ones
Replace the gridCustomFieldIdServer and gridIdCloud for the values corresponding to the first grid or Grid context that is being migrated
Prepare the script to verification by adding a logic gate in the "for" loop or by hard-coding a single issue KEY into the issueKey variable
Change projectId to a project that is relevant to the current grid field
Verify whether object.rows.each { } loop does not contain any mentions of columns that are not present in the Grid configuration and add e.remove("COLUMN_NAME") for all sequence columns
Run the script and verify data, for each Grid or Grid context:
Change the gridCustomFieldIdServer, gridIdCloud, projected or any custom issue-pulling logic to relevant values
Re-do step 11
Run the script
Verify whether the data was migrated correctly
TGE Server/Datacenter → TGNG Cloud migration
Groovy Script
Expand to see the script....
Prerequisites
A plugin/tool for running Groovy code is present on the instance from which the script is being run
TGE app is installed and enabled on Server/Datacenter, TGNG Cloud is installed and enabled on Cloud
The project from the source instance was already migrated to the target instance
All Columns in the Grid Config are made editable before running the script (can be changed after)
Please note that the script was written to be used as a sample and requires you to change the variables' values
None of the Target Grids have default rows (they can be re-added after the data is migrated)
Disclaimers
The script was developed to be run from the source Server/Datacenter instance.
The script is not an official solution for migration but it’s a workaround solution and should be used with care and precaution.
Guide
Make sure that all of the prerequisites above are met
Verify whether the grid fields on your Server instance have a multi-context setup
If not, configure identical Grids on the Cloud instance (+ Scopes)
If so, create an identical Grid configuration for each distinct context
Obtain a valid authentication string from the Cloud instance and replace the placeholder value in the script with it
Prepare the script for verification by adding a logic gate in the "for" loop or by setting a JQL string so that it only returns a single issue
Verify whether object.rows.each { } loop does not contain any mentions of columns that are not present in the Grid configuration and add e.remove("COLUMN_NAME") for all sequence columns
Run the script and verify data, for each Grid or Grid context
After the finalised script has been validated on one of a few (up to 10) issues, proceed to remove the logic gate added in step 4 or expand the JQL string to an expression covering all relevant issues