Domande frequenti sulla migrazione da Jira Server a Cloud
- What are the differences between Jira Server and Jira Cloud?
- Will the design and layout be different in cloud?
- Can I connect Jira Cloud to my other Atlassian server products?
- Which apps are available for Jira Cloud?
- Is there a user limit in cloud?
- How frequently will updates happen in cloud?
- Will I be notified before updates are released in Jira Cloud?
- How do I pick my URL for my cloud site?
- How do I manage users in Jira Cloud?
- Is there a storage limit in cloud?
- How do I plan my migration?
- How long does migration take?
- How do you handle testing and staging?
- How much downtime should we expect during our migration?
- When is the best time to run a migration?
- What migrates over and what doesn't?
- Will migrating overwrite my existing cloud data?
- 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 to make the switch, you can find step by step instructions for migrating.
No, there's no additional fee to migrate from Atlassian's self-hosted products to cloud. To help you explore or migrate without paying twice for both server and cloud, we also offer free extended cloud trials to existing self-hosted customers.
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 self-hosted license to upgrade, you can:
- 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 migrate from your new, upgraded server instance to your cloud site.
Server evaluation licenses last for 30 days and can be extended to 90 days upon request.
Atlassian Access provides IT administrators with 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. Learn more.
Site Administrators have the highest administration privileges on an Atlassian cloud site, including:
- 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
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 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.
You can track major changes weekly in the Atlassian Cloud Documentation blog. This includes new features, bug fixes, and other changes across all our cloud products. Or cloud platform and services roadmap is another great place to see what we feature today, along with a glimpse of what’s to come.
Protezione e sicurezza
Our cloud hosting infrastructure for Jira Software, Jira Service Desk, and Confluence includes AWS regions across the United States, Germany, Ireland, Singapore, and Australia.
Our platform optimizes where customer data is located based on origin of access, ensuring more reliable performance and reduced latency. As an example, if the majority of users access your organization's Jira or Confluence cloud instances from Europe, then their data will be migrated to and stored in Europe.
Learn more about our cloud hosting infrastructure.
The Atlassian Trust Center connects you to the latest information on the security, reliability, privacy, and compliance of our products and services. The Trust and Security Community group is another great space to share information, tips, and best practices for protecting your data and using Atlassian products in a secure and reliable way.
Our Cloud Platform and Services Roadmap provides at a glance visibility into the features we offer today, as well as what's in the works.
Use our cloud pricing calculator to calculate your total monthly or annual cost, including any apps you may want to install. Unlike our self-hosted products, cloud subscriptions are charged per user on a monthly or annual basis.
Atlassian's cloud products are offered as monthly or annual subscriptions rather than licenses and maintenance renewals. Pricing is per-user, allowing you to spread costs over time and scale efficiently.
To see what our cloud products and apps might cost for your organization depending on which plan, payment schedule or apps you choose, use our cloud pricing calculator.
The Atlassian Access pricing calculator can help you estimate your costs.
Atlassian Access is billed by the total number of unique users accessing any of the supported cloud products. You only pay once for each user, even if that user has access to multiple cloud products.
No, your current self-hosted license and maintenance won't transfer to cloud. These are two separate licenses and are paid for separately.
However, we do offer extended cloud trials that provide a free cloud site for your remaining self-hosted maintenance period (or minimum 60 days, whichever is longer). These trials are designed to help you transition to cloud at no extra cost.
You can also compare Atlassian Cloud and Server to choose the right solution for you.
Yes, the design and layout are different than what you and your users may be accustomed to in server. To help you get comfortable with the differences and identify any communications or training needed to help onboard your users, we recommend trialing or even piloting cloud with a small group of users before migrating.
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.
Atlassian cloud sites currently support up to 5,000 users.
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, so you and your users are always on the latest and greatest version – no upgrades required. 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 (your site's URL) 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.
When choosing, keep in mind:
- 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.
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.
This depends on which plan you choose. Standard plans currently have a storage limit of 250 GB, while Premium plans offer unlimited storage. Learn more.
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.
Start by reviewing our guide to testing your 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, including any expected downtime.
We recommend scheduling your migration for a weekend or other downtime to reduce the impact on your users.
If you do plan on migrating over a weekend, let us know in advance so we can be prepared to support you if needed.
What is migrated:
- Users, groups and permissions.
- Site data, including projects and issues.
- Jira configuration. This includes things like project setup, custom fields, and workflow schemes.
- Custom main handlers.
- Application links.
- Project avatars.
What isn't migrated
- The migrator's group permissions. 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 after migrating.
- Passwords. Unless you've set up SSO, users will need to reset their passwords 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'll need to re-install any compatible apps or work with the app vendor to migrate any relevant data.
All links within the Application Links section in Jira Server will be migrated. As long as the links are accessible to Atlassian cloud sites, they will continue to work after migrating.
When you import from server, 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.