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
4,295,348
Community Members
 
Community Events
165
Community Groups

Migration fails on user migration phase (Error 100)

Edited

While I found a very similar error reported here (https://community.atlassian.com/t5/Atlassian-Migration-Program/Migration-fails-on-user-migration-phase/qaq-p/1959043)  it's unfortunately not the same.

With the exception of a warning about heap size (we're using 2GB on a fairly small instance of about 15 active users), all the other pre-checks pass fine. Our on-prem site is licensed through to next year and we're using the trial license for cloud that runs for the same period in order to do the evaluation and migration. JIRA version is 8.2.5 and Migration Assistant is 1.6.8. All users on-prem are from JIRA's Internal Directory rather than managed from a domain or SSO vendor.

When trying to migrate from on-prem JIRA to Cloud using the Migration Assistant, it fails almost immediately on the Users and Groups section with the following error:

"100:Server to cloud migration payload format is invalid"

I can't find that described anywhere. Migration settings are :

Users and groupsYou have chosen to migrate all users and groups from the Jira directory
Group membershipUsers and groups will be migrated separately. Users will not be given project permissions and will not be added to your license.

In atlassian-jira.log, the following error appears around the same time but may be unrelated:

2022-04-28 17:18:31,637 http-nio-8087-exec-296 url: /jira/rest/migration/latest/user-interface/log; user: adam.hough ERROR adam.hough 1038x12195x2 12gf2iu 192.168.177.79:49627,192.168.177.56 /rest/migration/latest/user-interface/log [c.a.j.migration.userinterface.UserInterfaceLoggingResource] api/fetchProductLicense: Fetching server products failed - Error: Request failed with status code 401
at t.exports (https://office.talus-tech.com/jira/s/d542cm/802005/e05263495498dc1e48fbd663242d5834/1.6.8/_/download/resources/com.atlassian.jira.migration.jira-migration-plugin:static-resources/fe-resources/vendors.80904690ae541d91481d.js:155:3048676)
at t.exports (https://office.talus-tech.com/jira/s/d542cm/802005/e05263495498dc1e48fbd663242d5834/1.6.8/_/download/resources/com.atlassian.jira.migration.jira-migration-plugin:static-resources/fe-resources/vendors.80904690ae541d91481d.js:186:1298)
at XMLHttpRequest.p.onreadystatechange (https://office.talus-tech.com/jira/s/d542cm/802005/e05263495498dc1e48fbd663242d5834/1.6.8/_/download/resources/com.atlassian.jira.migration.jira-migration-plugin:static-resources/fe-resources/vendors.80904690ae541d91481d.js:155:3047683)

JIRAUserPayload.png

2 answers

1 accepted

0 votes
Answer accepted

I worked with Atlassian support and finally tracked the problem down to a group that had no name. I couldn't do anything with it from within the Admin UI so used SQL to manually remove the offending group from the cwd_group table; initially I just renamed the group via SQL but it still wasn't usable via the Admin UI which is why I opted to delete it. Once that group was removed, the migration made it past that initial sticking point.

Hi @Adam Hough ,

I would suggest you open a ticket with Atlassian support, so they can help you with this topic

https://support.atlassian.com/contact/#/

Thanks for the suggestion; usually I find community boards more helpful than tech support so I typically try (t)here first, but you're right that I should give Atlassian a nudge on this one!

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you