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
Last year, we set up a new JSM instance in the Atlassian Cloud. With this, I configured Atlassian Access and tied it to our Azure AD.
Now I'm ready to migrate our Jira Server Software projects to Jira Cloud. We are using an LDAP directory to the same AD users for the Server instance. Do I still need to migrate the users and groups from Server to Cloud? Our permissions structure in Server is admittedly somewhat messy and I was hoping to start fresh in the Cloud.
But I can't seem to figure out how to disable the migration of user and group data from Server to Cloud using JCMA.
Any assistance or suggestions would be greatly appreciated!
You can choose to migrate only groups and users related to the project that you're choosing via JCMA.
Check this page for more info: https://support.atlassian.com/migration/docs/determine-your-user-migration-strategy/
Hope this will help you.
Thank you for the link. I found this additional link at the bottom of that page and it gave some helpful information regarding my situation.
I faced a similar problem during our migration. As far as I know, this doesn't work.
We migrated several hundred users. Some of them were linked to the existing Atlassian account in the cloud, others are orphaned because the naming convention didn't match or were already inactive on the server.
Fortunately, Access does not calculate all users in a policy, but only those who are really active. It's not the cleanest solution, but it works pretty well for us!
It seemed like it was going to force me to migrate the users and groups. It wasn't giving me the option to proceed without selecting to migrate them.
I think I'll move forward with migrating one project as a test and bring along its users and groups just to see what happens. If it will merge the already existing cloud accounts, then this might not be a huge issue. I'll just have to clean up some outdated groups.
Thank you both for your input!