Migrating the Jira Server to Atlassian CLoud

[KAVIRAJACHOLAN SELVARAJ]

Hi, 

In my organization, we are planning to migrate Jira server in Datacenter to Atlassian CLoud. Could you please advise us what are all the information is needed and is there any detailed documentation available for the same?

As per our knowledge, we have to consider the below points,

• # Projects
• # Users
• # Plugins
• # Incidents
• Support Hours
• Firewall & Security information
• SSO
• Database configuration
• Domain registration details 
• Licensing 
• SSL Certificate details

We would like to know how to start this migration in Atlassian cloud, since we have migrated to other cloud environments like AWS, Azure. But we are new to Atlassian.

Additional to this, we are looking for SLA and role & responsibilities once it onboarded to CLoud from Atlassian and with us, etc.

Do you guys have good call back number, so that we can discuss more on this?

Thanks,

Kavi

[Zoryana Bohutska _SaaSJet_]

@KAVIRAJACHOLAN_SELVARAJ To set up SLA, you can use built-in SLA for Service Desk or additional app like SLA Time and Report for issues in Jira Cloud.

[Peter T]

Hi KAVIRAJACHOLAN,

in addition to the excellent points made by Nick, here are some more to consider:

1. Cloud have a user and performance limit currently 2000 users, but in reality there are very few customers of that size who use cloud, typically they are under 500 users
2. the URL cannot use your company domain - it will be something like company.atlassian.net - this is a huge drawback to a lot of companies.
3. There are limited number of add-ons available for the cloud, and even if there are they have less functionality, this leads to much less customization options.
4. Your admins won't have access to the application log file and thus rely on the Atlassian support for pretty much every troubleshooting. We recommend getting premier support if you want to get a good response and resolution time for your tickets.
5. You cannot implement best practices such as Test - Staging - Production as your cloud site comes with only Production environment. This leads to that all change request will be done directly in production with the associated risk of mistakes and user frustration.
6. You have very little control over the upgrades and thus changes of usability will be forced upon your users and you have to train the users not on your schedule.

Besides that Atlassian is taking care of the infrastructure which is a huge gain for a lot of customers who does not use public cloud services such as AWS and don't have administrative staff.

Let me know if this was helpful and if you need more information.

Cheers,

Peter T

[Nic Brough -Adaptavist-]

I have a couple of very very very minor disagreements with this post:
1.  5,000 now
5.  You can get a "development" Cloud environment, but it is small, no good for any type of scaled testing, or staging, and aimed very much at App developers, so it certainly won't do much for good practice.  Better than nothing though.
6. You have no control over the upgrades (apart from the odd time Atlassian decide they might want to include an on/off switch for something.  Usually reserved for big changes and new features they are very uncertain people might want)

[Peter T]

Hey Nick, have you heard of any customer in the cloud at 5000 users? I haven't so until then i will consider the 5000 user mark pure marketing.

With the upgrades they sometimes give you enough notice to plan things on your side which is still something.

Cheers,

Peter T

[Nic Brough -Adaptavist-]

For most of the answers, see https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html

But also

• Plugins - you will need to read up on converting each one you have in the vendors documentation (Assuming there is a cloud equivalent)
• Support Hours - see https://confluence.atlassian.com/support/atlassian-support-offerings-193299636.html
• Firewall - irrelevant, Cloud is over the internet.
  
• Security information - see https://www.atlassian.com/trust/security
  
• SSO - see https://www.atlassian.com/enterprise/cloud/access
  
• Database configuration - irrelevant to you
  
• Domain registration details  - irrelevant to you
  
• Licensing - irrelevant to you
  
• SSL Certificate details - irrelevant to you
  

[KAVIRAJACHOLAN SELVARAJ]

Thanks for your quick response. Do you have any call back number to contact ?

• Database configuration - irrelevant to you; To make a story internally to move the jira to cloud.
  
• Domain registration details  - irrelevant to you ; If my organization want to use their own Domain is that allowed?
  
• Licensing - irrelevant to you
  
• SSL Certificate details - irrelevant to you; If my organization want to use their own SSL Certificate is that allowed?

[Nic Brough -Adaptavist-]

The things I've flagged as irrelevant are irrelevant because they are part of the service, not things you have to do for yourself any more.

The database lives behind Jira - you don't need to think about it.  You can't use your own domains or certificates, and the licences are simply part of the service.

We're not Atlassian here, we're end-users.  You could ask support for more help, but Atlassian don't do telephone support,and all of your questions are documented across their site.

If you need help with your migration, I'd look for one of the solution partners - most of us are quite familiar with migrations, from simple help through to doing the whole thing for you.  Start at https://partnerdirectory.atlassian.com/?lang=en-us to identify some ones that suit you!

[KAVIRAJACHOLAN SELVARAJ]

Thank you Nic, Let me check on this and will get back. 

Meanwhile, I can create a POC server for free trail and proceed with POC?

[KAVIRAJACHOLAN SELVARAJ]

One more quick question Nic, If we have the data backup, how we can import in the new cloud environment I mean database. Are we using Postgresql database?

What is the timeline to complete if we have all the data for ready to migrate. Data should be in any recommended format?

[KAVIRAJACHOLAN SELVARAJ]

One more quick question Nic, If we have the data backup, how we can import in the new cloud environment I mean database. Are we using Postgresql database?

What is the timeline to complete if we have all the data for ready to migrate. Data should be in any recommended format?

[Nic Brough -Adaptavist-]

Again, the database is irrelevant.  Have a read of the documentation about migrating, it covers that and the format of the data you need to prepare

The timeline is simple - time an export from Server, it's going to take between 3 and 8 times that long to migrate in (that's roughly the range I've seen)