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!
Hello Neil,
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.
Regards,
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.
Recommendations for SCIM provisioning with Atlassian Access | Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Neil,
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!
best regards
Justin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just so you know, if you choose to NOT migrate all the users and groups on each migration, they will not be in the project roles on the destination and the projects' access will have to be set up again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.