JIRA Server to Cloud migration experience - for large instances with tons of customisation

[Evgeniy Terekhov]

Hello Atlassian community

We have a few dozen of JIRA plugins and a few thousands of JIRA users.

The major plugins are:
- Scriptrunner with dozens of groovy scripts & scripted fields
- Behaviours
- JsIncluder
- Zephyr (TM4J)

I am writing this post to seek advice.

How did you manage to solve the problem of JIRA Cloud not being able to support the level of customisation users are used to?

Is it time for a big cleanup, or should we stick to the DC version instead of Cloud?

Please share your migration stories.

Thanks.

[Nic Brough -Adaptavist-]

 If you don't want to clean up and migrate, then yes, you can move to DC.

You will still need to do some migration work, but that is just around checking and migrating apps to DC. 

The notable one on your list is Scriptrunner.  If you are going to Cloud, you are going to have to evaluate each script you have and either throw it away, or translate its functions up to Cloud (Scripts on Server simply don't work on Cloud, you'll need to rewrite and/or replaceevery simngle one).  On server to DC, you just need to check your scripts are ok for DC (most, if not all, will be)

[Dave Bosman [Realdolmen]]

Hi @Evgeniy Terekhov 

In my opnion it all depends on the expectations. 

If you are willing to do without some of the customizations I would recommend moving to Cloud. 

If the customizations are really needed you have no other option than using DC. 

Both have their pro's and con's.

• The migration to Cloud will take up a lot more time than DC 
• DC will have more options to customize than Cloud. 
• DC has more plugins than Cloud to extend the functionality (for the moment, but the amount of plugins on Cloud is growing)
• With Cloud you don't have to worry about upgrading. 
• Some functionalities only exist in Cloud and others only in DC. 
• ....

Regards

Dave