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

Migration assistant unexpected errors: "We couldn’t check for group conflicts/space key conflicts"


I'm running into errors trying to use the migration assistant from a server instance to cloud. See the below image.

I've kept trying to refresh, and tried making a new migration instance, but get the same errors. 

Any thoughts on what to do here?

Screenshot from 2021-03-14 17-05-26.pngWe couldn’t check for group conflicts

1 answer

1 accepted

3 votes
Answer accepted

Figured it out.

My confluence logs pointed me in the right direction - I saw this:

2021-03-14 23:34:32,499 ERROR [Caesium-1-3] [] error Error executing space keys conflict check.
-- checkExecutionId: ccdc6716b00bf1afe6995b96bf9d3e746917ff3d
com.atlassian.migration.agent.okhttp.HttpServiceException: Bad request. Status code: 401, message: {"code":401,"message":"Unauthorized"}

so I figured this was related to accounts and permissions - even though I was using the admin account on both the server and the atlassian cloud site, somewhere the streams were getting crossed with my non-admin account

See this page for the solution:

I had to:

- clear browser data

- make sure I wasn't logged in to target atlassian cloud site in any browser tab as my normal, non-admin user account (because it doesn't have privileges for the operations required by the migration assistant)

After this fix, I was able to successfully run the migration assistant and confirmed a space got imported to cloud as desired.

This was really frustrating. I don't understand why something as basic and common as being logged in as my regular user account should lead to an "unexpected error" with no suggested recourse, and for which I have to wade through logs. This is sloppy, bad UX.

Robert Horan Marketplace Partner Jun 08, 2022

I am having this problem now and none of those workarounds are actually working.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events