You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello Everyone,
We have 50 active users on our Jira server and 42 inactive users. Our license on the cloud is also for 50 active users. When I try to run the migration I receive the error :
“133:We couldn't migrate your users because you have exceeded your user limit for Jira Software. Upgrade your cloud plan and try again.”
I am not seeing any way to just migrate active users or migrate all users with same status as they have on our Jira server, meaning the inactive stay inactive on cloud and don’t count towards our license limit of 50.
Can you please let me know how to proceed ? Is there a way I can run the migration currently or do I need to delete all inactive users from our Jira server and then run the migration ?
Thank you,
Kamal
Hi @Kamal Jebelli welcome to the Atlassian Community!
Inactive users can not login to Jira and do not count for licenses so you are correct.
If you go to User Management, you will see there is a filter, which will let you show all active or all inactive users. The filter will say: Has site access and No site access.
Do the numbers match the 50 active users you mentioned?
Kind Regards,
Ash
Hi @Ash Yadav - VMotion IT Solutions ,
Thank you for your message. Yes we have 50 active and 42 inactive on our jira server but on the migration tool it is showing the total meaning 92 users to migrate.
I am guessing that it is trying to migrate all 92 as active users and that is causing the issue ! We have same license, meaning 50 active users on the cloud.
Any idea how I can run the migration in this case ? Ideally I don't want to delete the inactive users from jira server.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm,
I just had a read of: https://support.atlassian.com/migration/docs/migrate-users-and-groups/#Migratingusersandgroups-Deletedorinactiveusersanddirectories
"Deleted or inactive users and directories
Any deleted users or users in inactive directories that are referenced in your Jira data will appear as Former user after migration. If you need to migrate the references to these users, reactivate them (or the directory) before migrating.
Users with disabled status in your Server site will be migrated as active but without any product access. This means they will not be counted as active Jira users for billing purposes. Learn how users are managed in Cloud"
You might be correct about it trying to migrate all 92 users as active, only to keep them without product access and not count them towards billing, I just can't seem to find a definitive answer on whether or not you'll need to have 92 licenses allocated for just the migration stage.
Have you reached out to Atlassian Support to query this?
KR,
Ash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ash Yadav - VMotion IT Solutions
Thanks again for helping out. Yea I read those support documents you referrenced and tried to fiddle with the migration tool but could not make it work.
I was also under the impression it will stay inactive and my migration would run normally.
I do have a Move ticket open with atlassian support but it has not been going that fast and thought I could check with the community for a quicker solution.
Best Regards,
Kamal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No problem at all, if you wouldn't mind posting an update from the Atlassian team once they respond to your ticket, I'd really appreciate it (and I'm sure others would for the future).
Many thanks,
Ash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kamal Jebelli any update on that ticket?
I checked with a colleague of mine who has migrated to cloud recently and they encountered the same issue as during the migration inactive users are treated as active so they required a trial license or something along those lines from Atlassian and they also had a ticket open. Just wondering if your outcome was the same.
KR,
Ash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ash Yadav - VMotion IT Solutions ,
Thanks for your update. I am still waiting to get resolution for my ticket. They are apparently checking our cloud site.... Honestly I am not really sure when my issue will be fixed !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kamal Jebelli ,
I'll see if I can get more details tomorrow from my colleague and get them to look at this issue in particular and revert back if the Atlassian team hasn't resolved it for you by then.
As always keep me posted if you still need my help.
Kind Regards,
Ash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ash Yadav - VMotion IT Solutions
Forgot to update but the issue was fixed by atlassian support by removing the limit on our cloud site for the migration to complete ! Seems to be working fine now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.