Splitting a Confluence Instance- some key questions
Asked by Nancy S_ Bennett:

Hi! I have a client that has a situation I need a quick answer on, I think I have most of this worked out but need to confirm a few things. Any help with any of the below questions will be appreciated.

This client has the following setup:

1 person owns company A and company B. They have Confluence, Jira and Bit Bucket under an instance named after Company A (companya.atlassian.net).

Company A uses Confluence (companya.atlassian.net/wiki) only. They have the majority of spaces in Confluence,(maybe 50 out of 57). They have nothing in Jira or BitBucket as they are not a software company. They are novice users.

Company B also uses the same instance of Confluence ( same companya.atlassian.net/wiki). They also use Jira (companya.atlassian.net/jira) and Bit Bucket . As for Confluence they far fewer spaces (about 7 out of 50) but the ones they do have have several links to Jira issues. These are engineers and far more advanced users.

The desired end state is to have separate instances for the 2 companies:

* companya.atlassian.net instance (Confluence only)
* companyb.atlassian.net instance (Confluence, Jira and BitBucket)

Here is my plan

* **Step 1: Dedicate the current instance to Company B by renaming URL for Company B:** Rename the current companya.atlassian.net product URLs to companyb.atlassian.net changing the URLs for Jira, Confluence and BitBucket. I am thinking this is the best route for company B because even though they have far fewer spaces, they have pages that have links to Jira so I thought they should stay in the current instance instead of getting cloned to a new one.
  * **Question 1:**Is my logic good for keeping Company B in the current instance because of their links in Confluence pages to Jira
  * **Question 2:** I am also assuming (please confirm) that all links will be preserved between Jira and Confluence (both URLs will be changed)
  * **Question 3:** Changing Product URLs is an admin function, correct? No need for Atlassian support on this step?

<!-- -->

* **Step 2: Purchase a second Confluence Instance for Company A:** Pay for a new instance of just Confluence under company A's name companya.atlassian.net.
  * **Question 4:** Can the new instance for Company A carry a name previously used in the recently renamed Company B's instance? I am guessing the answer is no and we'd have to slightly tweak the name to avoid conflicts (ex: newcompanya.atlassian.net instead of companya.atlassian.net).

<!-- -->

* **Step 3 "Clone" companyb.atlassian.net's Confluence into companya.atlassian.net**

<!-- -->

* **Question 5:** I say "clone" in quotes because it looks like site clone is not an option. It looks like I would have to move each space individually due to the fact the source is not a confluence only site but the destination is. Quote from Atlassian's docs: "*If you have both Confluence and Jira in your cloud site, the site import method outlined here will not be available in your Confluence Cloud site. Instead, you'll need to import all of your spaces individually. "*That's a bummer since the spaces I want to move are the ones that don't tie to Jira. Do I have all of this right?
* **Question 6:** Will cloning/importing individual spaces in confluence from one instance to another instance like this just "work", meaning are there any issues with internal Confluence links in the cloned instance?

<!-- -->

* **Step 4: Content Cleanup and User :** Once it is confirmed that both the renaming of the instance for Company B and the clone of company A's confluence was successful, now delete Company's A's spaces from company B instance, and company B's spaces from company A's instance. Deactivate company A users in Company B site, Deactivate company B users from Company A's site.
  * **Question 7:** Can Atlassian support help with this part?


Answers:
author: David at David Simpson Apps
body: Aside: If it was more convenient, you could clone the whole thing - Confluence and Jira, and then just remove Jira entirely at a later date.


Tags: cloud

confluence-cloud