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
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
Inactive users are users that don’t have any product access. In the example below, “User 1 Smith” is an inactive user with no access to Jira Software.
Inactive users after migration
During the migration, inactive users in cloud are migrated as active users with site access but without any product access. This means they will not be counted as active Jira users for billing purposes.
Why do inactive users become active after migration
To understand this, let's say you've both Jira and Confluence present in your server instance. There are 50 users in Confluence server and there are 100 users in Jira server. Out of 100 users, 50 users are common in both Jira and Confluence. Also, there are 10 inactive users among the 50 common users. These inactive users are disabled in Jira, but they do have Confluence access.
You start with Confluence migration using the Confluence Cloud Migration Assistant. 50 users in Confluence server are migrated to the destination cloud site.
When migrating Jira using Jira Cloud Migration Assistant, 10 inactive users are converted into active users in the cloud site. This is to ensure that they are active in cloud with site access and they continue to have Confluence access and no Jira access. Be assured that the active users in cloud will only get site access.
In case the user is inactive in both Confluence and Jira, they will be migrated to cloud with active status and access to cloud site. However, they will continue without any product access in cloud as well.
The table below lists the different multi-product migration scenarios. User “Lisa” highlights the scenario where an inactive user is migrated to cloud. We need to give “Lisa” site access so that we don’t create any conflict with her existing access, which is Jira server in this case.
If you have any questions or concerns, please comment on this post.