Migrating ScriptRunner for Confluence from Server
Overview
- Alternative hosting options
Your alternative hosting options for ScriptRunner for Confluence are Cloud and Data Center. This page takes a look at the differences and which route might suit you best.
- Feature comparison
Everything the Server version of the app can do, the Data Center version can too.
On Cloud, there are some notable differences, highlighted below.
Comparing Cloud functionality at-a-glance
Expand each feature below to see more details. Remember, some things work a little differently on Cloud, so we'd recommend taking a closer look at documentation to understand the differences if these features are critical for your processes.
Details of differences available here.
See full list of implemented built-in scripts here.
Details of differences here.
Will work differently on Cloud when completed.
We’re actively seeking further input into use cases: please reach out to us to discuss!
This feature is not currently possible within Atlassian Cloud Infrastructure.
This feature is not currently possible within Atlassian Cloud Infrastructure.
For more specifics about how these features work in Cloud, please check out the ScriptRunner for Confluence Cloud documentation.
Reminder: we’re keen to hear from you about what you’d like to see on ScriptRunner for Confluence Cloud: submit your feature requests here.
Migration process: ScriptRunner from Confluence Server to Cloud
The general approach 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 below.
One of the biggest gotchas for migration is the rewriting of scripts. As mentioned in the ScriptRunner migration FAQs section, 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 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.
Need help writing scripts for Cloud?
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 scripting service can 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
Our 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!
Migration services
Did you know that we were named Atlassian Partner of the Year 2020 for Cloud Migration Services?
With a tried-and-tested, best practice approach to Atlassian tool migration, we’ve helped some of the world’s leading organisations move to Atlassian Cloud—guiding them every step of the way.
Let our team of migration experts help with scoping and planning through to delivery of your migration project.