In case you missed it, we recently had our “Migrating to Jira Cloud: Best Practices for Moving to Jira Cloud” webinar. In this webinar, we discussed why organizations choose Jira Cloud, which organizations are best suited for a Jira Cloud migration and best use cases for the Jira Cloud Migration Assistant.
We also lay out some best practices considerations for cloud hygiene, administration, and governance after migration: such as setting up naming conventions, creating a change request protocol, and what objects should be considered when conducting a routine hygiene audit.
If you missed our Jira Cloud Migration webinar, you can watch it on demand now.
In this post, we’ll recap the question and answers from the webinar to help you navigate, and get the most out of, Jira Cloud.
Let’s get started!
Q: Is there any Jira Cloud Migration solution for greater than 5000 users, many custom fields and workflows?
A: Not currently. Enterprise Cloud is being improved to address this limitation. The goal is to be able to offer unlimited users. Jira Cloud is not limited on the number of custom fields, workflows, etc, however excessive numbers of those types of configurations can cause significant performance issues. Enterprise Cloud will be designed to handle large numbers of objects that traditionally have caused performance issues as well.
Q: Are there any extra charges for large amounts of Rest API data download to on-prem apps?
A: The REST API has no limitations currently. The other side of the coin is that it can be a denial of service attack vector, since it’s not limited. Rate limiting is something that has been committed to by Atlassian, but it has not been implemented in Cloud yet. That could potentially address the denial of service concern.
Q: Is there a free Okta account? Is it a single license? Are there limitations?
A: Yes, Okta can be used for free with any Atlassian Access license. The limitation is that it’s only free for use with Atlassian Cloud. You can add additional applications (ex: Office 365) but they are not free.
Q: Do you have this seminar for a Confluence Cloud migration?
A: No, but we are happy to set up a time to chat with you to walk through the process for migrating to Confluence Cloud.
Q: What is the cost for Atlassian Access with AzureAD?
A: There is no additional cost with Atlassian to use AzureAD, OneLogin, Okta, etc.. for identity management. However, there could be additional costs with Microsoft to use AzureAD for identity management of Atlassian Cloud.
Q: How does Jira Cloud address data sovereignty?
A: It doesn’t currently. However, it is included with Enterprise Cloud for Jira and Confluence. Atlassian calls this “Data Residency.” Enterprise Cloud is currently not publicly available, but you may be able to sign up for the Early Access Program.
Q: Does Jira Cloud have the ability to store data in different geographical regions?
A: Atlassian has not provided a lot of details about how this will work in Enterprise Cloud. Early indication is that you will have some control, globally, on where various types of data are stored. It does not seem to be tied to the user’s location at this point.
Q: Does Jira Cloud support Microsoft CASB?
A: Microsoft has a Jira connector for CASB. It connects via Jira’s REST API, so it should be able to connect to modern versions of Jira Server and Data Center as well as all of the Jira Cloud variants.
Q: How do you recommend migrating Jira Service Desk projects?
A: At this point, the traditional method will need to be used. If you have an empty cloud instance, you can import the entirety of your Jira instance data. If you have data in an existing Jira Cloud, you can pull the data out of Cloud, merge together on a Server version, and then push back to Cloud.
We have developed a reliable method for performing these types of migrations as they are fairly involved and messy.
Q: How easy is it to migrate from Fresh Desk to Jira Service Desk?
A: There is not a “tool” available to do this easily. We would write a series of scripts to perform the migration. There are some limitations in the type of data that can be exported from Fresh Desk and imported into Jira.
Generally, it’s difficult or impossible to retain ticket history. We can generally only migrate the data from the “latest revision” of the ticket. We generally can get all field data and the most recent attachment (if the source system has attachment versioning.)
Q: How easy is it to migrate from Jira Core to Jira Software?
A: It’s not a migration, per-se, if you just want to make an existing Jira Core Project a Jira Software Project. That’s just a matter of editing the Project and changing the Project Type. If you want to migrate from one Jira instance to another, it can be fairly messy.
Typically these involve some data normalization (I’m “davet” on the source and “dave.theodore” on the destination. The source system uses Pri 1, Pri 2, etc and the destination uses Blocker, Major, etc Priority, for example.)
This needs to be performed so that you don’t introduce duplication on the destination system. There is no native way to perform an export of a single Project in Jira either. There are a number of methods to accomplish this and the one we use depends on how the Project is configured.
Q: You mentioned that Jira is automatically updated. What if I don’t want it to be updated? Can I pause the update?
A: Not currently. Atlassian has been indicating they will offer some control on pausing updates on their Enterprise Cloud, but that product is only in Early Access currently.
Q: Does Jira Cloud have a firewall? Can I only allow IP addresses from my office?
A: This is not an option currently in the standard Cloud. It is currently available in Cloud Premium, however, it’s only in beta. So I would expect some minor hiccups until it’s available as a general release.
Q: What is Premium pricing?
A: There are currently 2 Cloud tiers, and a 3rd is coming. We’ve been referring to Cloud, as it has traditionally been available, as “Standard.” There is also Cloud Premium that I briefly described in the webinar. Finally, Enterprise is currently in Early Access that started earlier this month.
The cost is higher for Premium, as compared to Standard, but you also get availability guarantees, the IP whitelisting feature I mentioned, and a variety of other features that are not available in the Standard Cloud.
Q: You said there was a 5000 users limit. What other limits are there?
A: With Standard Cloud, you have a storage limit of 250GB. The vast majority of the storage consumed by Jira is attachments, so that is effectively your attachment storage limit. Cloud also has far fewer Apps available, but the number of available Apps is growing daily. There are around 1000 Apps available currently for Cloud.
Q: What do you mean by “complex environment” in regards to the Jira Migration Assistant?
A: The Jira Cloud Migration Assistant has only been released for a little over a month. It’s still not as feature rich as it could be. In our testing, we’ve found it really only to be effective when migrating a nearly default Jira Project.
If you have customized workflows, many custom fields, a lot of 3rd party App provided functionality, etc, it likely won’t be able to migrate everything. This will change, though.
Atlassian is working on enhancing the functionality and will be available in future releases. Given the huge range of things that people use Jira for, I wouldn’t expect it to ever be able to migrate 100% of your data, though.
Q: I already have Jira Cloud. Can the Migration Assistant migrate my Server instance to the existing Jira Cloud?
A: This is actually one of the problems that it was attempting to solve. Prior to the Migration Assistant being available, you needed to download your Cloud data, set it up in a Server environment, merge the two instances together and then push the combined instance back into the Cloud.
Given the current limitations of the Jira Cloud Migration Assistant, this is still the method that most people will need to use, but in the future, you should be able to do this with Jira Cloud Migration Assistant.
Q: How do I test the Migration Assistant?
A: Great question. Atlassian currently does not provide a “sandbox.” We recommend setting up a trial Cloud instance and using that as a sandbox. Atlassian has announced that sandboxes will be available in Cloud Enterprise, but they haven’t announced much in the way of details yet.
Q: Can I connect Jira Cloud to my Active Directory?
You can, but there are some caveats. First, you need to install Atlassian Access. It’s an App that allows you to connect to external identity providers. It also allows you the ability to use two factor authentication, Single Sign On and a variety of other things.
It can connect to AzureAD, Google Auth, Okta and OneLogin. You will need to connect your Active directory to one of those identity providers first, and then set up Access in order to connect to your internal AD.
Q: 99% uptime seems low. Is there something more reliable available?
A: 99% uptime translates to over 1 and a half hours per week of unexpected downtime. Not ideal for an Enterprise. Atlassian’s Cloud premium has 3 nines of uptime, which moves your commitment to a little more than 10 minutes per week of unexpected downtime. Enterprise Cloud will be 99.95% uptime, which is more in line with what larger enterprises expect.
One of the challenges with Cloud is uptime. Most Cloud service providers cannot match the uptime levels you can achieve with your own hardware, but the cost savings is usually significant and encourages you to accept a little unexpected downtime.
If you have a question that did not get answered here, or would like us assistance in planning, executing, and optimizing a Jira Cloud migration, please reach out today.
At Coyote Creek as an Atlassian Platinum Solution Partner, we know it’s the human connection that makes the difference in all that we do.