Jira server to cloud migration FAQs
- What are the differences between Jira Server and Jira Cloud?
- Will the design and layout be different in Jira Cloud?
- Can I switch back to the old look and feel once I'm in Jira Cloud?
- Can I connect Jira Cloud to my other Atlassian server products?
- Which apps are available for Jira Cloud?
- What is the user limit in Jira Cloud?
- How frequently will updates happen in Jira Cloud?
- Will I be notified before updates are released in Jira Cloud?
- How do I pick my site name (URL) for my Jira Cloud site?
- What's the difference between classic and next-gen projects in Jira Software Cloud?
- How do I manage users in Jira Cloud?
- How do I plan my migration?
- How long does migration take?
- How do you handle testing and staging?
- How much downtime should be expected during our migration?
- When is the best time to run a migration?
- What migrates over and what doesn't?
- Will the migration overwrite existing data on my Jira Cloud site?
- What happens to my apps when I migrate?
- I have Jira linked to other tools – what happens to my links when I migrate?
- What happens to my users when I migrate?
To understand the full complexity of migrating and plan your approach, start by creating your migration plan. Then, when you're ready you can find step by step instructions for migrating your data in the Atlassian documentation.
Currently, the only supported migration path is to export the full Jira Server site and import the data into Jira Cloud. Project by project migration is not yet supported.
No. There's no additional fee to migrate from Atlassian's server to our cloud products.
You simply pay the standard fees for your Jira Cloud subscription and any Jira Cloud apps you install.
No. However, you may need to upgrade to a newer version of Jira Server before you can migrate. To find out which versions are currently supported, take a look at our migration documentation.
If you're on an earlier version and don't have active maintenance on your Jira Server license, which is needed to upgrade, you can use a free evaluation license as a workaround. You will need to:
- Sign up for a free server evaluation license from my.atlassian.com.
- Use that license to set up a new instance on the latest version of Jira Server.
- Import your existing Jira Server instance into the new instance.
- Then use the new, upgraded instance to migrate.
Server evaluation licenses last for 30 days and can be extended to 90 days upon request.
You can track major changes that affect all users of the Jira Cloud products in the Atlassian Cloud Documentation blog. This includes new features, bug fixes, and other changes across all Atlassian Cloud products.
Once you're a cloud admin, you'll have immediate access to our latest features and bug fixes.
Atlassian Access provides IT administrators enhanced security and administration across all Atlassian Cloud products. It includes a global view of all Atlassian accounts in your organization and the ability to secure them with SAML single sign-on or mandatory two-step verification, user lifecycle management with SCIM provisioning, and priority support across your enterprise.
Site Administrators have the highest administration privileges on an Atlassian Cloud site. The following permissions are currently available to site admins:
- All permissions assigned to the 'administrators' group for Jira Cloud
- Access to user management (the ability to invite new users, create groups, assign users to groups, grant product access, etc.)
- Access to billing information
Yes. The storage limit for Jira Cloud products is 250 GB, regardless of your user tier. However, storage limits are not currently enforced. We are revising our storage policy in cloud and will roll out more options for purchasing additional storage, along with enforcing the limits sometime in 2019. We will notify customers in advance before we roll out these changes.
Learn more in our Atlassian Cloud storage policy documentation.
You can set up single sign-on and automatic user provisioning for your organization with Atlassian Access. All of Atlassian's supported identity providers offer connectors to your on-premises ADFS (LDAP). We support SAML SSO and user provisioning with SCIM for the following cloud identity providers:
- Azure AD
- Google Cloud (coming soon)
- Onelogin (SAML only)
- Centrify (SAML only)
Learn more about security best practices, including setting up SSO and provisioning for Atlassian Cloud.
Trust and security
Jira Cloud sites enforce the following security standards:
- SSL by default
- Hosted on a secure hosting facility
Jira Cloud sites adhere to the following standards and regulations:
- ISO/IEC 27001
- ISO/IEC 27018
- PCI DSS v3.2, SAQ A
- CSA CCM c3.0.1
For more information on compliance and security in Atlassian Cloud, check out Trust at Atlassian.
Atlassian hosts data for Jira Cloud in six different AWS regions: US (East and West), Europe (Germany and Ireland) and Asia Pacific (Sydney and Singapore).
Atlassian will optimize where customer data is located based on how it's accessed around the world. For example, if the majority of your users access your Jira Cloud site from Europe, then their data will be migrated to Europe.
Learn more about our cloud hosting infrastructure.
For more information on Atlassian Cloud security and compliance, check out Trust at Atlassian.
Jira Cloud subscriptions are charged per user on a monthly basis, or annually with a discount that equates to two months free.
Use our pricing calculator to help determine your monthly or annual subscription fees.
With Atlassian Cloud products, including Jira Cloud, Atlassian handles the security, upgrades, hosting, mobility, support, and more for your sites.
Since the hardware, database and file systems running Jira Cloud are maintained by Atlassian, your total cost of ownership may be lower with Jira Cloud.
You can use the Atlassian Access pricing calculator to estimate your cost.
Atlassian Access is billed by the total number of unique users accessing any of the Atlassian Access supported cloud products. You only pay once for each user, even if that user has access to multiple products.
No, your existing Jira Server license and maintenance do not transfer to Jira Cloud. These are two separate licenses and are paid for separately.
You can also compare Atlassian Cloud and Server to choose the right solution for you.
Yes. The design and layout are different across Jira Server and Jira Cloud.
We recommend trialing Jira Cloud before migrating to get comfortable with the differences and identify any communications or training needed to help onboard your users.
No. The design and layout is not the same across Jira Server and Jira Cloud, and you cannot switch between the two.
Yes, you can connect Jira Cloud to your other Atlassian server products using Application links. You'll need to set these up after you migrate.
To see which of the apps you use are available in Jira Cloud and discover new cloud-only apps, check the Atlassian Marketplace. Keep in mind while you're evaluating that Jira Cloud may have some functionality that replaces the need for your server apps. For example, Jira Cloud includes a number of workflow validators and conditions, SSO (available with a paid Atlassian Access subscription), and advanced integrations with Bitbucket Cloud and Github.
Note that some apps are only available for cloud, and some are only available for server. If an app you need isn't available for Jira Cloud, reach out to the app developer to request availability in Jira Cloud or discuss your migration options.
You may also have custom apps that you've built for your specific needs. If that's the case, we suggest looking for an app in the Atlassian Marketplace that can provide similar functionality, or you can recreate your custom app using our cloud APIs.
For additional assistance migrating app data, you can visit our Atlassian Partners page to find one who can help with your migration.
Jira Cloud currently supports up to 5,000 users per site.
Note that for Jira Service Desk Cloud, this limit does not apply to customers (end users submitting requests). You can have a free and unlimited number of customers.
We regularly deploy updates to all of the Atlassian Cloud products, including Jira Cloud. Major changes are announced weekly in the Atlassian Cloud Documentation blog. This includes new features, bug fixes, and other changes.
No. Because updates are deployed regularly, Site Administrators aren't notified of upcoming changes. We recommend following the Atlassian Cloud Documentation blog to keep up with changes and find out what's new.
Site names are chosen for an entire Atlassian Cloud site at the time you sign up for your first Atlassian Cloud product – for example, when you first sign up for Jira Software Cloud or Confluence Cloud.
The format for the site name is https://example.atlassian.net, where example is a unique character string that you specify.
There are a few things to be aware of when choosing your site name:
- Your unique character string must be at least three characters.
- It can only contain letters, numbers, and hyphens.
- Hyphens can't be the first or last character.
The new Jira Software experience is easier to configure and grows more powerful every day. Part of the new experience is next-gen Scrum and Kanban project templates. They provide a streamlined experience, are easier to use, and quicker to set up than classic projects. Learn more.
You manage users and groups across all products you've subscribed to on an Atlassian Cloud site, including Jira Software Cloud, from the Users and Groups pages of the site administration. See Managing users and groups for more.
You can also create an organization for your company from your site. With an organization, you can view and manage all Atlassian account users at your company with your verified domains.
Through Atlassian Access, you can set up SAML single sign-on and configure automatic user and group provisioning from your identity provider, like Okta or Azure AD.
If you use G Suite, you can automatically sync users from your G Suite directory to your Atlassian Cloud site and your users will log in with their G Suite accounts.
Check out our Jira Server to Cloud migration planning guide for step-by-step instructions on how to plan and execute your migration.
No two migrations are exactly alike. Depending on the amount of planning, change management, and the complexity of your migration, the entire process could be a matter of days or months.
The best way to determine this is to plan your migration in advance and execute a test migration.
Based on the complexity of the data and migration, our support team can help you conduct a test migration, during which we'll help you prepare and create a migration plan.
These test runs help ensure there is minimal impact to your business processes during your live migration and will help your admins and project owners work out the steps and timeline required.
No two migrations are exactly alike. We recommend running a test migration to assess your plan and how long your migration will take.
We recommend scheduling your migration for a weekend or other downtime to reduce the impact on your users.
When you migrate from Jira Server to Cloud, the following data is imported:
- Users, groups and permissions.
- Site data, including projects, issues, and Jira configuration.
- Any custom mail handlers you've set up in server.
- Application links.
- Attachments, project avatars, and logos.
The following is not imported:
- The migrator's user information: If you're the person doing the migration, you'll need to re-add yourself to your previous groups after migrating.
- Apps: App data is not included in the backup when migrating from Jira Server to Jira Cloud. Some apps do have the capability to export and import their data but you'll need to check with the app developers or their documentation to confirm if this is possible. Your licenses for Atlassian Marketplace apps can be viewed on https://my.atlassian.com/.
- User avatars: Users will need to update their avatars at id.atlassian.com after migrating.
- Passwords: Users will need to reset their passwords in Jira Cloud after migrating.
- Timezones: Timezone information on a per-user profile will be lost.
Yes. Performing a Jira import will overwrite all data associated with projects and replace it with project data from the backup file.
You can also choose to either overwrite all cloud users, or to merge server users with your existing cloud users – for example, if you have users in an existing Confluence Cloud site.
If you have existing project data in Jira Cloud and want to import more data from Jira Server, you'll need to follow the steps outlined here.
Apps are not migrated when you move from Jira Server to Jira Cloud.
After migrating, you will need to re-install any compatible apps or work with the app vendor to migrate any relevant data.
For more information on migrating apps, refer to the Jira Server to Cloud migration planning guide.
All links within the Application Links section in Jira Server will be migrated. As long as the links are accessible via Atlassian Cloud sites, they will continue to work after migrating.
When you import a site, you can choose whether or not your users are imported along with the rest of your data.
Learn more about importing users in the Jira Server to Cloud migration planning guide.
While we do not offer professional services for migrations, our support team can help you plan your migration.
For help with a full end to end migration, we also have a wide network of partners globally that are experienced in Atlassian migrations. Visit our Atlassian Partners page to find one who can help with your migration.
Our migrations support team can help with technical questions or issues related to your migration.