Splitting Atlassian cloud setup: Migrate part of Jira, JSM, and Confluence

Hey everyone,

I’m looking for advice on moving some of our Atlassian stuff to a new cloud setup. We need to split off a few Jira and JSM projects, plus some Confluence sites. They’re going to a totally separate company with its own Atlassian account.

Has anyone done this before? I’d love to hear about your experience. Did you use any special tools to help? Were there any big problems or things to watch out for? How long did everything take to get back up and running?

Any tips would be super helpful. Thanks!

I’ve been through a similar process recently. We utilized Atlassian’s Cloud Migration Assistant for Jira and Confluence, which streamlined much of the process. However, be prepared for some manual work, especially with custom fields and workflows. Our migration took approximately two weeks, including thorough testing.

A word of caution: pay close attention to user permissions and license management during the transition. We encountered some unexpected issues with Service Management queues and SLAs that required additional configuration post-migration.

For Confluence, ensure you have a clear content strategy before migrating. We found it beneficial to clean up and reorganize our spaces beforehand, which saved time and confusion later.

Overall, proper planning and communication with stakeholders were key to our successful split.

hey Nova56, been there done that! we split our setup last year. used the jira cloud migration assistant - lifesaver! took about a week to get everything sorted. biggest headache was user management, so plan that out carefully. good luck with ur migration!

I went through a similar split about 18 months ago. One thing I’d strongly recommend is thoroughly documenting your current setup before starting. We spent a good chunk of time mapping out dependencies between projects, workflows, and custom fields. This prep work saved us countless headaches later.

For the actual migration, we used a combination of Atlassian’s native tools and some scripts our dev team cooked up. The process took around 3 weeks from start to finish, including a full week of testing and fixes.

A word of caution: be prepared for some data inconsistencies post-migration. We had to do quite a bit of manual cleanup, especially with linked issues and some custom fields that didn’t transfer perfectly.

Also, don’t underestimate the importance of user training. We held several sessions to get everyone up to speed on the new environment. It really helped smooth the transition.