Documents to help you prepare to migrate your Atlassian server products.
Articles to help assess your migration costs license status.
Learn about migration timelines, roadmaps, app and Atlassian Access with these resources.
Look up resources on Jira and Confluence cloud, data hosting regions, LDAP, and ADFS.
Pre-migration checklists for Jira, Confluence, and Bitbucket.
A collection of topics that help prepare you to migrate your apps to the cloud.
Native tools and resources that will help with your migration.
Documents to help you use Jira Site Import to migrate to cloud.
Documents that walk you through using the Confluence Cloud Migration Assistant to migrate to cloud.
Resources to help get started and testing after you migrate.
Documents that walk you through using the Bitbucket Cloud Migration Assistant to migrate to cloud.
Everything you need to know about moving your data from one cloud site to another.
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
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
More details on User management differences in cloud and server
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
More details on Mobile collaboration tools from Atlassian
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(personalised 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
View focused tutorials for end users migrating from Jira server to Jira Cloud. The tutorials describe how to perform common tasks in Jira, highlighting any differences between Cloud and Server. Access the videos playlist
Key changes for Bitbucket
Code review experience
To help reviewers assess changes quickly, we've historically taken a ‘code-first’ design approach for the pull request view (reviewing and working in a pull request). Through several rounds of user testing, we optimized the new design around improving navigability for the reviewer, while reducing the need to context switch.
We’re also working hard to create more parity between our server and cloud products with features like enforced merge checks, task creation, to-do lists, and side-by-side diff view. Check out the Bitbucket Cloud roadmap to stay informed about other features and improvements and when they’ll be available.
Bitbucket Pipelines is CI/CD for Bitbucket Cloud that’s built into the UI and sits alongside your repositories. When using Pipelines to deploy your code, application, or artifacts, Bitbucket provides you with the status of your deployment environments, and visibility over each environment's code changes. You can also configure your deployment environments so only specific branches or admins can deploy to them. Learn more about setting up and monitoring deployments in Bitbucket Pipelines.
Bitbucket Pipes make it easier to build powerful, automated CI/CD workflows in a plug and play fashion without the hassle of managing integrations. We’ve worked with industry leaders including Microsoft, AWS, Slack, Google Cloud and more to build supported pipes that help automate your CI/CD pipeline, and made it simple to create your own to help abstract any duplicated configuration across your repositories. Learn more about using Bitbucket Pipes in Pipelines.
Integrations and app
The Bitbucket Cloud app ecosystem is different from Bitbucket Server. Some Server apps are unnecessary in our cloud product, because they are already essential Bitbucket Cloud features, such as webhooks and snippets.
Bitbucket Cloud also contains a number of popular apps and integrations (and the list just keeps on growing). Bitbucket Cloud integrates with popular code scanning, quality, security, and artifact management tools, such as Slack, SonarCloud, Snyk, JFrog, AwesomeGraphs, and AWS Code Guru to name some of the more popular integrations. Below are Atlassian product-specific integrations available for Bitbucket Cloud. For more information and a more comprehensive list of other product integrations, refer to our Marketplace for the list of supported apps and integrations.
For more information on how Bitbucket Cloud functions differently from Server, refer to Functional differences in Bitbucket Cloud.
Was this helpful?