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
I migrated both our Jira and Confluence test environments (server) to a Cloud trial and also activated a trial for Access and things have gone pretty well (loving SSO). I migrated all users & groups from Jira, preserving group membership. For Confluence I did not since those users should already exist from the Jira migration. I bolted on Access for SSO and all usernames should be the same email from our server instance and Access anyways. My questions:
Our environment -
Groups - 29
Users - 86
Projects - 220 (6245 issues - 224MB)
Apps - 10
Groups - 69
Users - 204
Spaces - 48 (1950 pages - 839MB)
Hi @Keith Zenoz ,
Just a few question from our end to understand how you are migrating Jira and Confluence:
Are you using the Migration assistance plugin to migrate or the Site import functionality?
If you are using Migration assistance, you can choose to migrate users and group however if the users and groups are already present on the cloud site then the assistance will not reimport it will skip them and only add missing users.
If you are using Site import function you can choose merger user option that will preserve users and group that is there on the cloud site.
One thing to note when you have Atlassian access enabled is during migration it is recommended to disable user provisioning during migration and re-enable it after migration as we have a known issue : [https://jira.atlassian.com/browse/ACCESS-653|https://jira.atlassian.com/browse/ACCESS-653]