Plan your Cloud migration
Documents to help you prepare to migrate your Atlassian Server or Data Center products.
Prepare sites for a cloud-to-cloud migration
Starting January, 2024, we’re renaming the Jira cloud-to-cloud migration feature to Copy product data. We’re moving this feature to Atlassian Administration at admin.atlassian.com in a unified experience along with Confluence cloud-to-cloud data copy.
We’re rolling out the change slowly, so if you aren’t able to access this feature by logging into your Jira Cloud and selecting System > Settings > Migrate cloud site, we recommend you go to admin.atlassian.com, and select:
Settings > Data management > Copy product data
You’ll need to have organization administrator permissions to access and use the Copy product data feature.
Before you start a cloud-to-cloud migration, there are a few things you need to do to ensure you and your data are ready to go.
Understand what sites and organizations are in Atlassian
An Atlassian organization is where you find your company-wide admin settings. A site contains a single instance of each Atlassian product you’re using. Your organization contains all your cloud sites and products, and multiple sites can be part of the same organization. Sites also have their own admin settings. Learn more about Atlassian organizations
A cloud-to-cloud migration can be performed between sites in the same organization or sites in different organizations.
Understand source and destination sites in cloud-to-cloud migration
In a cloud-to-cloud migration, data is copied from one cloud site, known as the source site, to another cloud site, known as the destination site. The destination site can be a new site or a site with existing data.
Check your permissions
You need to be an organization admin for your source site to access this feature and to migrate. If the destination site lives in a different organization, you’ll also need the org admin roles for this organization. For older organizations, you might be able to use the site administrator role if you’re migrating within one org, but this role has been deprecated for new orgs. Learn more about admin permissions
When selecting your destination site, the sites available for you to select from will be based on whether you have the required permissions (as described above) to perform that migration.
Add Jira products to your destination site
If you’re preparing to perform a cloud-to-cloud migration for Jira, make sure your destination site has the same Jira products as your source site, even if you won’t be migrating data from the other products. This will reduce the chance of your migration failing. If there’s a product you don’t want to use after migrating, set up a free trial for that product, then deactivate the trial after your migration is complete. Learn how to set up a free trial
Example
If you have Jira Software, Jira Work Management, and Jira Service Management on your source site and you want to move data from Jira Software only, you still need to add Jira Work Management and Jira Service Management to your destination site.
Install apps on your destination site
Make sure your destination site has the same user-installed apps as your source site before you run a migration. We don’t move app data yet, but this will reduce your chance of encountering any errors. To move app data, you’ll need to contact the respective Marketplace Partner.
Understand how migration affects your billing
Depending on the number of users you intend to migrate and the subscription plans your source and destination sites are currently on, your billing and experience in the destination site may be affected by a migration. Use the table below to understand what these changes might be. Learn more about Jira Cloud plans
Plan on source site | Plan on destination site | Changes |
|---|---|---|
Free | Free | No change |
Free | Paid | You’ll be billed on your destination site for the additional users that have been added to groups after your migration. You won’t be billed on your source site. |
Paid | Free | You'll be able to move all your users, but you won’t be able to add them to groups. You’ll need to upgrade your destination site to a paid plan to do so. You’ll continue to be billed on your source site. |
Paid | Paid | You'll continue to be billed on both sites. On your destination site, you’ll be billed for the additional users that have been added to groups after your migration. If you don’t want to keep your source site after migrating, downgrade your source site to a Free plan. |
Ready to migrate?
Find out more about cloud-to-cloud migration for Jira:
Was this helpful?