You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am planning a migration from Server to cloud for both Jira and Confluence. I'm working on the dates and have a few questions:
University of Washington
I would suggest doing several test migrations. And I think confluence is easier if you don't use too much custom app macros or user macros. Our users love the new confluence cloud experience. You should not compare but see it as another application.
In both cases you have to see the amount of post migration tasks and determine all steps.
Managed accounts are not mandatory but are definetly a preferrable way.
@Christof Hurst Thanks for that info. Yes, we want to identify the post-migration tasks and hope to learn those by doing test migrations! Thanks for the confirmation.
Good to know that Managed accounts are not mandatory.
We purchased a 100 set license. How does Atlassian determine how many seats are used?
I've only done a single migration so far, but based on that my answers would be:
@vthomas9 Are you really sure you want to do that?
Confluence Cloud has so many features and capabilities removed compared to Server that Cloud would be totally unusable for our Server Users ... so we are sticking with Server until we see a need to migrate to Data Centre.
Just be very careful what you wish for!