We are looking at migration options to bring an acquired company's Confluence Server into the cloud. One option we are considering is keeping it as a separate site under our company's management.
We are Company A and have Site 1. We have acquired Company B.
Company A has Atlassian Access so we have an organisation which contains Site 1.
If we were to migrate Company B and create Site 2, would it be possible to have Organisation A as the parent and sites 1 and 2 in the same org? If we do this, is it possible to manage all user access from Organisation A? What would the experience be like for users with access to both sites?
We are on Confluence Standard.
I hope that isn't too confusing, thanks
Wow, I'm are hilariously qualified to answer this question! :D
Summary: Contact Atlassian Support to help guide you with this. This page gives a good over of having multiple sites under one organisation https://support.atlassian.com/organization-administration/docs/how-many-instances-of-a-product-does-my-organization-need/
Long version:
I can give you a general overview of the difference experiences and pros and cons to managing multiple sites in an single org vs merging the sites into one site vs keeping each site in separate Orgs, but honestly the experience really depends on a few more details:
Scenario 1 - You merge the sites
Pros
Cons
Scenario 2 - You keep the sites separate, but under the same organisation
Pros
Cons
Scenario 3 - You keep the sites AND orgs separate (generally not advised)
Pros
Cons
You made it to the end!? Nice job, have a break and rest your weary eyes...
If you're interested in chatting in more detail, you can contact me via my website smolsoftware.com
-Kieren
Co-Founder @ Smol Software | Ex-Atlassian
Wow! Looks like you just got a gold-star answer, @Jake Ward.
Kudos to you, @Kieren _SmolSoftware_!
-dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kieren, thanks so much for the detailed response! I think based on this I'm still leaning towards scenario two. There are no security concerns around allowing users to collaborate and see each other - they will be on the same IdP, but I'm happy for access to each site to be managed independently.
The main reasoning for considering this approach is that both sites are quite well established and we are expecting to get a fair amount of overlap in groups and spaces and are probably not yet in a position to merge these. In both sites we use groups created in atlassian admin, so no concerns currently about bringing over from IdP. Longer term I think we'd consider some cloud to cloud space migration as we get a better understanding of how we will fully integrate in time.
We're talking fairly small numbers of users. I've done some rough calculations on price from merging vs. keeping separate and it doesn't seem to be too dramatic...
I've tried to keep detail a bit vague for the forum, but thanks again for your help here!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I’m glad it was helpful!
we are expecting to get a fair amount of overlap in groups
This could bite you if you’ve not done enough analysis on what those overlapping groups give access to.
e.g. if you have a confluence-admins group in cloud and on server, when you migrate to cloud (if you’re on the new admin experience) those two groups will merge together. If user A was in the cloud group, and users X and Y were in the server group, all 3 users will be in the merged cloud group. So user A will suddenly have confluence admin to the newly migrated confluence product and X/Y will have access to the established cloud product.
The way to avoid this (if you’re on the new admin experience) is to rename the cloud groups that will clash before migrating the server groups. https://community.atlassian.com/t5/Atlassian-Access-articles/Org-admins-can-now-rename-groups-in-cloud/ba-p/2276321
One more thing, you could have troubles if you’re using the default product access groups and using an IdP, since you can’t sync users into default groups. My team is building an app to help with this, essentially we're solving ACCESS-604. It's about to be released in a free closed beta (around January 2024). If you're interested, contact us via our website smolsoftware.com to be a part of the beta.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just some additional info regarding Scenario 1 and 2.
The ability to connect multiple IdPs to a single Cloud Org is only available to customers on the Cloud Enterprise tier.
As the original question relates to a customer on the Standard tier, multiple IdPs under a single Org would not be possible without upgrading.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
FYI @Jake Ward , the Admin Automation app is publicly available now. It will allow you sync users from one group to another which could help with your IdP setup and getting users into Default Product Access groups.
Hope the migration worked out for you!
-Kieren
Co-Founder @ Smol Software | Ex-Atlassian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.