• Products
  • Documentation
  • Resources

Get your users started in cloud after migrating

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 1: You can apply a site-wide banner in Jira or Confluence to redirect users to the new URL

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

Pro tip 3: Have users update their url bookmarks

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.

If your team is already using the mobile apps, make sure they download the cloud versions after the migration. The server versions of the apps won't work.

Learn more about the Jira Cloud app

Learn more about the Confluence 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.

Home features:

  • 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.

Pro tip 1: Keep any eye on the Atlassian blog where product changes are announced weekly

From March 31, 2021, we're transitioning all users on the old issue view in Jira Cloud products (Jira Software, Jira Service Management, Jira Core) to the new issue view — which means no one will be able to switch back to the old view anymore. For a limited time, you'll still be able to temporarily click through to the old view before we remove it from Jira Cloud altogether. After that, the new issue view will be the only experience available in Jira Cloud. Learn more about the new issue view

Key changes for Jira

Change 1: Team-managed projects

All users can create a team-managed project, even non-admins. If you're a Jira admin and you want to restrict this, you'll need to remove the “Create team-managed projects” permission. For more information on global permissions, see Managing global permissions

Change 2: New issue view

The new issue view is where your users resolve issues, which means they may look at it a few hundred times a day (or even more). Good news: admins can customize where fields live on the new issue view for each issue type. There's no need to accept the default issue layout; you can optimize your team's issue experience. Learn more about configuring issue layouts

Learn more about Jira issues view

 

 

Last modified on Apr 15, 2021
Cached at 1:20 AM on Apr 19, 2021 |

Additional Help

Ask the Community