Heads up! ScriptRunner documentation is moving to docs.adaptavist.com. Adaptavist will keep this site up for a bit, but no future updates to documentation will be published here. ScriptRunner 6.20.0 will be the last release to link to scriptrunner.adaptavist.com for in-app help.

There are two main migration types:

Non-clustered

Migrating from Server to a non-clustered Data Center instance requires you to update your platform from a Server license to a Data Center license.

With regards to ScriptRunner, the only change required is to update ScriptRunner to a Data Center license. You should request a Data Center license from the vendor/partner before beginning any migration.

Please contact us if you have questions about this.

Clustered

As well as the steps required for a non-clustered instance, a clustered setup requires you to move your home directory to a shared location that all nodes can access. The process of moving your home directory is described in Atlassian’s guide. When following Atlassian’s guide for ScriptRunner, you must also include the <scripts> and the <scriptrunner> directory under the list of directories to copy in step 2 (Set up the shared directory) of the Set up and configure your cluster section.

Additional considerations

Additional script roots

If you have custom script roots configured and are moving to a clustered Data Center setup, you need to make sure your custom script roots are available to all nodes in the cluster.

ScriptRunner features and inline scripts

If you follow the Atlassian Data Center migration process, the database that all nodes use should remain the same. ScriptRunner feature configurations and inline scripts are stored in the database, so are not impacted by the migration and should be available on all nodes automatically.

To maintain execution history for a clustered Data Center setup, you must move the <platformHome>/scriptrunner directory to the shared drive.

Partial Migrations with Project Configurator

In some cases, you may want to migrate a specific selection of data from an existing Jira Server instance to a new Data Center instance, rather than convert your current Server instance to Data Center. In these cases, you can use a tool like Project Configurator which lets you pick and choose what to copy over. All supported features can be found here.

Script files must have the same relative file path on the target server for any ScriptRunner features using script files copied with Project Configurator.

This means you must manually copy the <jirahome>/scripts from the source server to the target Data Center server’s shared home. You can be selective with the files you copy, but all script files must have the same path location starting from the '<scripts>' folder so that the features copied can use the same relative path locations.

For more complex migration cases, or for help getting a Data Center license, please contact us.

Have questions? Visit the Atlassian Community to connect, share, and learn with other Atlassian users and experts, including Adaptavist staff.

Ask a question about ScriptRunner for JIRA, Bitbucket Server, or Confluence.

Want to learn more? Check out courses on Adaptavist Learn, an online platform to onboard and train new users for Atlassian solutions.