Hello Community,
I'd be very happy about your advice on how best to approach the following scenario:
There is some technical documentation for the migration itself which seems to be feasible. But I have a feeling that, apart from the technical migration, there are many other things we should plan and be aware of before the migration. Will all spaces and projects be mixed up in one large list afterwards (so we have to find and implement kind of naming convention for each of them)? Will it be somehow possible to separate the user management of both organizations? Are there any obstacles like breaking links or anything not described in the documentation?
Just a few examples of questions spontaneously coming to my mind.... But more general: Can you probably recommend some Atlassian internal or external resource to support us with this project?
Thanks and best regards,
Jakob
Hi @Jakob B_
There's a whole range of things to consider when merging Cloud instances.
It's difficult to give you a definitive list as it can simply depend on the scenario - for example...
---
Perhaps responding to your final question - internal/external resources for support - is the best approach.
I'd recommend checking out the Atlassian Cloud Migration Program as a first step - and seeking advice from:
Solution Partners can provide hands-on support. You can also find local Partners via: https://partnerdirectory.atlassian.com/
Ste
Hi Steven,
thank you for reaching out. We have now chosen to give it a try and do the merge on our own by going through the documentation step by step. Atlassian Cloud Migration Manager support is not applicable for our showcase for some reason (number of users to low or something like that...) but we've arranged with the regular Jira and Confluence support team to be of assistance in case we can't get ahead on our own.
We've already successfully done the migration of oragnization B to A. This afternoon we will go ahead and move the Content which will surely be the more tricky part. Let's hope for the best! :)
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.
Thank you! Unfortunately we had to give up. Atlassian recommends smaller teams do it on their own but this is really near to impossible. For example the migration of a test project failed because there are differences in the permissions scheme. Of course there are. The Atlassian DIY documentation might work for sites without any changes of the default settings on both sides. But this is really utopian.
*frustrated*
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.