Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Pre-migration checks not working


I'm trying to migrate our on-prem Jira Software instance to the cloud.  Unfortunately, I'm running into all sorts of trouble with the migration assistant.

When I try the "Assess and prepare your users", I get this message:


If I try to jump ahead and migrate just the users, I get this message:


Messages include:

We couldn't check for Jira Work Management availability in cloud
We couldn't check for Jira Software availability in cloud
Some required URLs need authorization for migration
We couldn't check for invalid users
We couldn't check Jira Software user limit of your cloud plan
We couldn't check for Jira Work Management user limit of your cloud plan


The server has full access (outbound) to the Internet and I'm not seeing anything blocked on the firewall.

Unfortunately, our Jira instance is small with only 10 users, so I don't qualify for support.  It's super frustrating.

Any help would be appreciated.

2 answers

1 accepted

Posting here in case anyone else has this issue. 

So here's the essential problem: the directions for setting up SSL for Jira (here:  instruct you to create a new Java keystore and put your custom SSL certificates in it.  Unfortunately, this will prevent Java from successfully completing any SSL connection to a server whose SSL certificate chain is not in the new keystore. 

Since the cloud migration assistant needs to talk to AWS servers over SSL, it fails because it cannot create the SSL connection without trusted certificate chains (that are missing from the custom keystore created following the directions above).  Normally, java would use the default keystore here, which includes the necessary root certs:



To resolve the issue, I merged the cacerts into my keystore file.  In the example below jira.jks is the custom keystore that has my server's SSL certs in it.  Obviously set your passwords for your keystores as necessary (default is changeit) and make a backup copy of your jks file before doing this.

e:\Atlassian\jira\jre\bin\keytool.exe -importkeystore -srckeystore e:\Atlassian\jira\jre\lib\security\cacerts -destkeystore e:\Atlassian\jira\jira.jks -srcstorepass changeit -deststorepass changeit

After merging the cacerts file with my custom keystore and restarting Jira, the migration wizard checks now all work as expected.

There's probably some fine print somewhere that I could've read to separately specify the cacerts file or something, but this worked in a pinch and our on-prem server's days are numbered anyway.

So this appears to be due to our Java Keystore configuration that was required to allow us to use our enterprise CA for SSL certificates and LDAPS with Active Directory.  I took our Jira site offline and disabled SSL (taking the java keystore file out of the equation) and then the cloud migration wizard works test all run successfully.

Assumption at this point is that I need to add some certificates to the java keystore file that we're using.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events