My group is considering moving from Jira and Confluence Cloud to Server applications. I’ve read the following pages regarding limitations and the steps to carry out the migrations:
https://confluence.atlassian.com/confcloud/migrate-from-confluence-cloud-to-server-724765578.html
I’d be interested in hearing from anyone who has done these migrations and if you encountered problems or have any suggestions. I'm particularly concerned about losing the past record of Service Desk issues (open and closed) from our customers.
Thanks!
David,
The information will come across from your customers. One issue is that the passwords won't transfer correctly. Customers would need to reset their passwords.
I've run into some issues with "bad artifacts" being brought over from Cloud. In particular, I've had issues with avatars not transferring and icons not being pulled in.
Workflows have given me some trouble in the past. In Jira cloud, some functionality is included by default, but on server, you need to purchase an add on to get it (Jira suite utilities). This can lead to workflows not functioning as expected, including tickets being stuck in certain statuses until the workflow is fixed.
I've also encountered frustrations with having additional resolutions brought in, old email handlers/service desk email configurations.
One last thing is that whoever the user was that set up the cloud environment will be called "Admin" in server. All their history will be tied to that user. You'll likely need to rename them when you restore to server.
The migration will do a lot of the work for you, but you'll need to watch out for some of those items.
Kian,
This information will be very useful in our migration.
Thank you for sending it!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
out of interest can you elaborate the reasons that you are looking to move from Cloud to Server? I'm not on the Jira or Confluence teams, but I'd love to understand your use case better.
Thanks,
Marty
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A couple of reasons:
Overall cost would be lower.
We’d like to use Single Sign On, but the current limitations for using SSO in the Atlassian Cloud prevents us from using it.
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.