Providing a warm welcome and making sure your users are set up for success in cloud is critical to any migration.
Get it right, and your users will be productive faster, and happy with the decision to move.
To help you prepare your users, we’ve put together this quick guide that walks you through some of the key changes to highlight – and excite – your users. Feel free to copy and paste relevant items, or share the entire page.
Key changes for both Confluence and Jira
Change 1: Access your site through a new URL
After migrating, users will access your site through a new URL, which will follow a format like this:
Pro tip 2: Admins can set your ‘site home’ (the product that users land on when they go to yourcloudsite.atlassian.net)
For example, hello.atlassian.net lands on Confluence, but the default is Jira
Change 2: Log in with your email address
A key difference for end-users when they log in is that they’ll use their email address, instead of logging in with their username as they previously did for server products.
If you are using SSO in cloud, users will log in through SSO and have the same password
If you don’t have SSO, you’ll need to select “forgot password” and enter a new password
Email address is mandatory and must be unique in the cloud
You’ll need to add a new avatar
Change 3: Download the mobile cloud apps for access on the go
Guide your users to the Atlassian apps which work together to help them plan, track, and collaborate in real time, all from the palm of their hand.
Learn more about the Jira Cloud app
Key changes for Confluence
Change 1: Find your way faster with a new Home page
The new Confluence home page and navigation features bring together the destinations, content, and activity that's most important to users in one convenient location. Home is the perfect place to start in Confluence as well as reorient before moving on to a new piece of work.
Get back to recent pages - find pages recently drafted, published, visited, or starred.
Dive into spaces most frequented - navigate to starred and recently visited team, project, and knowledge base workspaces.
Keep up to date with activity feeds - browse a feed of activity happening on personal and team sites(personalized relevant feed feature coming later).
Change 2: Enjoy a cleaner page editing experience
New pages will be created using the Confluence Cloud editor. Pages created using the legacy editor continue to use that experience until you convert the page to the new editor.
Key changes for Jira
Change 1: Next-gen projects
All users can create a next-gen project, even non-admins. If you're a Jira admin and you want to restrict this, you'll need to remove the “Create next-gen projects” permission. For more information on global permissions, see Managing global permissions
Change 2: New issue view
You can open issues from a number of places in Jira Cloud—boards, backlogs, search, a project's issues list—and even from Bitbucket if the issue key is mentioned in a commit message. The issue view is something you might look at a few hundred times a day (or more), so it's pretty central to helping you get more done.