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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Is there a guideline for "separating the Atlassian "Organizations"? For a variety of reasons we need to separate part of an existing Organization due to the constraints/complexity of implementing SSO "Atlassian Access". Once separated, the new Organization will implement SSO. The current organization has not implemented SSO.
Considerations so far:
Welcome to the Community!
You have nailed a number of the things that need to be considered on the head. I have transferred a Jira Cloud instance from one organization to another and that part isn't very hard provided you are the Org Admin in both organizations.
I have seen other posted on the community about editing the XML Backup to modify various attributes before running an import, however I haven't personally done this so I can't speak to it's success. (Ref: https://community.atlassian.com/t5/Jira-questions/Jira-import-is-saying-You-must-enter-the-location-of-an-XML-file/qaq-p/926466)
As for splitting domains, I have never been a part of this type of activity, but I imagine this will be the most difficult task. But it can be accomplished as one of the other Community Leaders was capable of doing this: https://community.atlassian.com/t5/Jira-questions/Changing-domain-and-user-IDs/qaq-p/407620
You might want to reach out and ask for details in the thread.
I hope that helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.