You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Thanks to all of you who have joined our ongoing bi-weekly cloud migration demo! We’ve received so many great questions, so we’ve broken the Q&A recap into two sections:
Pre-migration: Cloud questions, the migration process and trials (click here!)
During the migration: User migration, tooling, app and product-specific migrations (you are here!)
In each post, we’ll cover questions that get asked frequently (or those we couldn’t get to!) as well as highlight resources to bookmark.
The questions in this post are categorized by:
User migration strategy
Product specific migrations
Apps and integrations
We’ll continue updating this post as new questions come through, so be sure to follow the post for updates. If you have more questions around cloud migration, comment below and we’ll get to them as soon as we can.
We also wanted to be sure you were all aware of the top cloud migration resources to bookmark if you’re planning for a cloud migration:
Cloud Migration Center: central hub that includes a resources page, server to cloud migration guide, migration contact form, and more!
Cloud migration trial: a great first step if you want to explore cloud or test your migration without double paying. And once you’ve migrated, the trial instance can become your cloud production instance. The trial lasts for the remaining duration of your server maintenance or a minimum of 60 days, whichever is longer. It’s completely free - no credit card required. Here’s a demo on how to claim it.
Server to cloud migration guide: phase by phase info on how to migrate, with links out to more detailed documentation.
Intro to migrations eBook: recommended reading for anyone starting a migration!
Jira Cloud Migration Assistant and Confluence Cloud Migration Assistant: free apps that help you audit and assess your on-premise apps and migrate users, spaces, and projects. (Here’s a demo on how to use app assessment)
Cloud Migration Toolkit: includes migration communication templates, a cloud migration checklist, and migration runbook template.
Will the Cloud Migration Assistants work with Jira Service Management? What about plugins? Currently the Jira Cloud Migration Assistant does not support the migration of Jira Service Management data, but we are working to have this capability developed soon (see our cloud roadmap for details). If you’re interested in getting early access, sign up here. If you need migrate Jira Service Management now, we recommend the Jira Site Import method, which requires generating an XML backup of the server instance and restoring it in cloud. Automated app migrations within Cloud Migration Assistants are actively being worked on, but are not currently supported (see our cloud roadmap for details).
Does the Cloud Migration Assistant work when users are stored in external directories (e.g. LDAP, AD)? If you’re using the Cloud Migration Assistants, users must be synced to the Jira and/or Confluence user directories (which are internal to the product) for them to be successfully migrated. Users do not need to be physically present in the Internal Directory. Learn more here.
Will the Cloud Migration Assistant import filters and filter subscriptions, as well as project schemes and custom fields? Jira Cloud Migration Assitant only migrates filters for individual projects. Cross project boards filters are not yet supported but are coming soon. You can visit our documentation for specifics on what data the Jira Cloud Migration Assistant migrates here, and what Confluence Migration Assistant migrates here.
How is the data exported and imported by the Cloud Migration Assistants? The CMA will use a mix of processes to export and import data, such as an individual and automatic XML export and import for spaces/projects, and an API for exporting and importing users.
Do the migration assistants work for migrating from our own cloud to the Atlassian cloud? If your own cloud is a server/DC license running on something like AWS, we'd still consider that on-premise so the Cloud Migration Assistants would work in this case.
If my Jira server license expires, will I lose access to the Jira Cloud Migration Assistant and Jira site import too? If you're on an unsupported server version and don't have active maintenance on your server license (which is needed to upgrade), you can use a free trial license via my.atlassian.com to upgrade in preparation for the migration. If you are on a supported version, but your license has expired, you will still have access to the Cloud Migration Assistant and Jira site import. Learn more here.
What additional actions or measures have to be considered after migrating from Jira Server to Jira Cloud using Jira Cloud Migration Assistant? New links to bookmark, such as the link to your new cloud site; Directions on how end users will log in; Anything that users need to reset (i.e. avatars or, if you’re not using SSO, users will need to rest passwords; Changes to apps or functionality; What training will be provided; Who to contact for help. Please review our "Getting started in Cloud" documentation for more info.
User migration strategy
Want to know more? Check out this page on Atlassian Access and cloud migrations.
How can we exclude users from our migration? When using Jira Cloud Migration Assistant, you won’t be able to exclude users and only migrate data. If you’re using the Jira Site Import method, you can have Atlassian Support assist with a manual CSV import of users where you can add a column to your CSV file that says whether a user should be active. If you've already migrated your users or synced your external directory to your cloud site, the Cloud Migration Assistants will not migrate these users but will instead just link their data from server to their cloud ID.
If we are migrating two different server products on the same cloud site, do they need to have the same user count (ie do both Jira and Confluence need to have 200 users?) No, you can still have separate user counts per license. The only caveat is Marketplace apps, which have to be at the same user tier as the parent product.
If my users have different email addresses between the on-premise instance and the new Cloud instance, is there a way to map those users prior to migration? In order for data to be migrated successfully (and because we link data to existing users in cloud), email addresses should be updated in server before migrating. If you’re using the Cloud Migration Assistants to migrate, they will look for email address errors.
What is an Atlassian Organization and how do I create one to manage my team? When you create a new instance of an Atlassian cloud product, you’ll be able to manage your site and users from the Atlassian Organization that is automatically created. An Atlassian Organization is an umbrella over all of your Atlassian cloud sites and products. Jira and Confluence can be part of an Atlassian Organization but currently, Bitbucket cannot be associated with an organization.
We're using a self-hosted LDAP as our user authentication method. Do we need to use Atlassian Access and Okta to integrate this into our cloud environment? Yes you must use Atlassian Access. Access is a separate product, which acts as the bridge between your identity provider and Atlassian cloud products. If you don’t have a supported identity provider, Atlassian offers a partnership with Okta for a free account. Visit Atlassian Access and cloud migrations and Configure user provisioning Active Directory or LDAP to learn more.
Can we still use our on-premise Active Directory or do we need to enable it in cloud? Yes you can still use your on-premise Active Directory, but in order to connect it with your Atlassian cloud products, you will need to purchase Atlassian Access and a cloud identity provider. The cloud identity provider will work as the connection between your on-premise Active Directory and Access.
Can we migrate projects with inactive users? Yes project data mapped to inactive users won't be lost and can be migrated.
I need to migrate Jira and Confluence server licenses and I have an identity provider for SAML, so I’ll need Atlassian Access. Which product should I migrate first and which cloud migration trial should I activate first? If you are planning on setting up SCIM user provisioning, we recommend migrating Jira first or not connecting SCIM until after Jira is migrated. If not, then order doesn’t matter if you’re using the Jira and Confluence Cloud Migration Assistants. Visit determine your user migration strategy and Atlassian Access and cloud migrations to learn more.
What is SCIM user provisioning? SCIM user provisioning integrates an external user directory with your Atlassian organization. This integration allows you to automatically update the users and groups in your Atlassian organization when you make updates in your identity provider. For example, with user provisioning, you can create, link, and deactivate managed Atlassian user accounts from your identity provider.
We use Crowd to manage users and groups. We are integrated with Azure AD and have created accounts directly in Crowd as well. Is there a migration path for Crowd? You'll be able to migrate internal directories to cloud and integrate with Azure AD on cloud, but you'll need to set up Atlassian Access to do so. Crowd is not supported on cloud. Learn more.
Does the cloud assistant setup the ldap/Azure ad link for passwords? With the Jira Cloud Migration assistant you'll be able to migrate internal and external users to your cloud site. Users will be directed to re-create a password upon their first login to the cloud site, but their data and permissions will not be lost.
Can we do a migration via site import but without adding any users? You can perform a site backup without adding the users. You will need to determine your user migration strategy beforehand. You can also refer to this documentation regarding user migration strategy.
Is Atlassian access mandatory for 2FA? Can i manage with Google SAML SSO to access Jira Cloud with 2FA? Yes, Atlassian Access subscription is mandatory for 2FA. But it's possible to Connect to G Suite to Atlassian Cloud as per this page which integrates your Atlassian Cloud site with your existing G Suite user directory. However, you will only be able to enable SSO for your users as this integration does not offer the other features of Atlassian Access.
When is the right time to introduce Atlassian Access to leverage SSO? Before migration or post migration? We recommend setting up Atlassian Access before your user and data migration.
Want to know more? Visit the migration tooling section of the Cloud Roadmap.
What are the steps for migrating Jira Service Desk (Server) to Jira Service Management (Cloud)? Currently the best way to migrate Jira Service Management (Former Service Desk) is to use Jira Site Import. We are actively working to add this feature to Jira Cloud Migration Assistant and it will move Jira Server Management projects in Q2 2021.
Why is all-at-once approach recommended when using Jira Service Management? The migration of Jira Service Management is currently not supported by the Jira Cloud Migration Assistant (but will be soon). To migrate JSM data, you’ll need to use the Jira Site Import method, which only allows for an all-at-once approach. Keep in mind this method will delete any existing data on the cloud site. Learn more about different migration methods here.
What are the plans to support Bamboo? We plan to make Bamboo Data Center available in the near future. Until further notice, you will still be able to purchase new licenses for Bamboo Server. Visit the Bamboo roadmap to learn more.
Is it possible to keep Confluence Server connected with Jira Cloud or vice versa? Yes, if you want to move some products to cloud while leaving others self-managed or migrate in stages, you can create two-way links between your cloud and server or Data Center products. Learn more about using app links here.
I am planing to migrate both Jira and Confluence to the cloud. Will I have to worry about any Jira issues which are linked in Confluence or Confluence links in Jira issues? Links between Confluence pages and Jira issues will be updated automatically as long as the pages are linked using the ‘Link issue' or ‘Link Confluence page’ functionality in the application. If these are linked simply by typing in the URL for an issue in a comment or something similar, those links may break, and our support team's help may be indeed necessary. Additionally, for Confluence pages linked with Jira issues, you can run the Jira Macro Repair process from Confluence once the migration is completed. Running this will identify and fix all broken links from Confluence to Jira. We'd recommend testing your Cloud migration on a Trial site and see if all links work as expected.
What happens with our FishEye and Crucible integrations after we migrate? You will still be able to purchase new licenses or renew existing licenses for Fisheye and Crucible. You can keep both Fisheye and Crucible on-premise and set up applinks to connect them to your cloud products.
Apps and integrations
Want to know more? Watch this demo on completing an app assessment using the Jira and Confluence Cloud Migration Assistants.
Are SVN integrations still supported after migration? The Svn Gateway - Subversion links in Jira app in the Atlassian Marketplace allows for an SVN integration in Jira Cloud.
Is the cost of cloud products different from the cost of apps? Yes, your cloud apps will sit within your cloud site. You will need to purchase your apps separately from your cloud products.
Do I need to purchase a new license for my Marketplace apps in the cloud while I run test migrations? You will have a 30-day trial period for your Marketplace apps. After the trial concludes for the app, you will need to purchase in order to continue using the product. You can also reach out to the Marketplace app vendor to request an extension of your trial.
I have apps for my server products that are not available on cloud. I was told that the API functionality in cloud doesn't support a migration. How is this problem tackled? We are working actively with our Marketplace Partners to develop the cloud apps that are currently available in server today. We’re also building APIs (currently in early access) that make it possible for server apps to be automatically migrated to cloud using the Cloud Migration Assistants. We recommend asking the app developers if they plan to use this functionality once it’s widely available.
Will app licenses automatically be extended to our cloud products? No, you will need to purchase a new cloud app license. You can install them as part of the prep phase.
Is there a way to migrate all 3rd party app data with the Cloud Migration Assistants? Currently, additional steps will need to be taken to migrate 3rd party apps - learn more here. We are working on making 3rd party app data migration available in the Cloud Migration Assistants. Learn mmore and sign up for the EAP program from here.
Can you migrate custom created apps to the cloud? Custom apps will need to be re-created, and you will not be able to upload the app via Manage apps for cloud environments. Refer to our documentation on Atlassian's framework for writing add-on's for cloud for more support.
Are there port redirects in Atlassian cloud to redirect ports used for Atlassian apps? Please check all ports used by Atlassian apps here.