Skip to main content
The Adaptavist and Scriptrunner Logo
cloud icon
Cloud
data_center icon
Data Center
server icon
Server

Migrating ScriptRunner for Confluence

This page takes a look at the differences between ScriptRunner for Confluence on Data Center and Cloud and which route might suit you best as you leave Confluence Server, plus tips and resources.
A Confluence page exudes lightning

Leaving Server?

If you use ScriptRunner for Confluence Server to accelerate and support your business processes, it's worth understanding your options between Data Center and Cloud, and what may need to be implemented differently if you choose to move to Cloud.

Video walkthrough of differences

In this short 15-minute video, Bobby Bailey shows how the functionality of ScriptRunner for Confluence Server and Data Center compares with ScriptRunner for Confluence on Cloud.
Quickly get to grips with how features work differently, and use the timestamps to skip to the most relevant features for your organisation!

Feature comparison: Data Center

This one is easy: everything the Server version of the app can do, the Data Center version can too.
A person holds the ScriptRunner logo aloft

Feature comparison: Cloud

We've listed below Cloud functionality at-a-glance for a quick comparison. Remember, some things work a little differently on Cloud, so we'd always recommend taking a closer look at documentation (linked for each feature!) to understand the differences if these features are critical for your processes.
A person holds up a magnifying glass
The following features are partially implemented on Cloud:
  • Built-in Scripts
  • Space Admin Scripts
View details of differencesarrow icon
The following features are implemented notably differently on Cloud:
  • Script Console
  • Script Fragments
  • Script Jobs
  • Script Listeners
  • Script Macros
View details of differencesarrow icon
The following features are not currently possible within Atlassian Cloud infrastructure:
  • Script CQL Function
  • Search Extractors
These features aren't currently available in ScriptRunner for Confluence Cloud, but we are actively scoping and seeking feedback about use cases for them:
  • REST API
Please reach out to discuss how you would like to see this brought to Cloud!

Tell us what you want to see

We’re keen to hear from you about what else you’d like to see on ScriptRunner for Confluence Cloud. You can upvote suggestions or submit your requests here.
Reach out to usarrow icon

Try ScriptRunner for Confluence Cloud today

Explore what's possible first-hand with a free trial
Get it free on Atlassian Marketplacearrow icon

Migration process: ScriptRunner from Confluence Server to Cloud

There general appraoch to migrating ScriptRunner for Confluence Server/Data Center to Cloud is:
  • Analyse the purpose of your scripts
  • Identify the equivalent feature in Cloud
  • Adjust your scripts to be Cloud-ready (explained below)
Full details and more possible gotchas for each method are outlined in the documentation linked below.
One of the biggest gotchas for migration is the rewriting of scripts. As mentioned on the main ScriptRunner migration homepage, any migration from Server to Cloud requires some rewriting of your scripts. For instance, interactions with APIs will need to be replaced with calls to the appropriate REST APIs due to differences between Atlassian Cloud and Server infrastructure.
If the equivalent feature in Cloud for what you need does not exist yet, please let us know. We’re prioritising development based on feedback from you!
Migration to Cloud documentationarrow icon

Migration process: ScriptRunner from Confluence Server to Data Center

When it comes to migrating Confluence on-premise, there are two main types of migration:
  • Non-clustered: this is as simple as updating your ScriptRunner for Confluence license
  • Clustered: this also requires you to move your home directory to a shared location that all nodes can access
Full details of steps involved and potential gotchas to look out for can be found via the following link.
On-premise migration documentationarrow icon

Help with rewriting scripts

Script rewriting guide

We wrote a handy guide to help you prepare to migrate the functionality that you need in your new Confluence home.
View guidearrow icon

Scripting service

Don’t have the bandwidth to rewrite your scripts in-house? Whether it’s time restrictions, personnel changes or a lack of confidence holding you back, our colleagues at Adaptavist (also part of The Adaptavist Group) provide a scripting service to help get you up and running quicker.
  • Get production-ready scripts on demand
  • Available across ScriptRunner for Jira, Confluence, or Bitbucket
  • Available across Server, Data Center and Cloud
Their team of Groovy and ScriptRunner experts are here to help you make the most of ScriptRunner and get back to what you do best: on premise or on Cloud!

Help with rewriting scripts

Try this guide with handy pointers or request a script from Adaptavist's Scripting service.

Migration services

Did you know that Adaptavist (also part of The Adaptavist Group) was named Atlassian Partner of the Year 2020 for Cloud Migration Services?
With a tried-and-tested, best practice approach to Atlassian tool migration, they’ve helped some of the world’s leading organisations move to Atlassian Cloud—guiding them every step of the way.
Let Adaptavist's team of migration experts help with scoping and planning through to delivery of your migration project.
A person flies through their Jira issues quickly, sending alerts and messages