nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira cloud-to-cloud migration is getting a new home!

Avishekh Das

Hi Community,

I’m Avi, a content designer working on the Jira cloud-to-cloud migration and Confluence cloud-to-cloud copy features.

From January 2024, we’re moving the Jira cloud-to-cloud migration feature to admin.atlassian.com. We're bundling this with the Confluence cloud-to-cloud copy feature that we rolled out recently.

This also means we've renamed Jira cloud-to-cloud migration (Migrate cloud site) to Copy product data.

Why are we doing this?

Instead of having two separate locations for Jira and Confluence, we’re unifying the experience so that you can move all your Jira and Confluence data from one central location.

What should you expect?

If you haven't used the Jira cloud-cloud migration feature

You won't have access to the legacy experience.

To access this feature:

Go to admin.atlassian.com
Select Settings > Data transfer > Start copying.

If you are currently using the Jira cloud-cloud migration feature

If you've any active migrations, you’ll have the option to opt in and use the new unified experience with an option to opt-out until June 21, 2024. We’ll sync your migration plans so that the transition between opting in and out is seamless.
If you’ve any in-progress migrations, you won’t be able to opt in. You’ll be able to opt in only when you don’t have any ongoing migrations. This is because we don't want to disrupt your work.

We'll sunset the legacy experience on June 21, 2024, so we recommend you opt-in and use the new unified experience.

Any changes that you need to prepare for?

If you’re a site admin, you’ll need to be an organization admin to access admin.atlassian.com and use this feature.

The new unified experience will be similar to the legacy experience with some improvements, so you won’t have to learn how to do a migration again. We’ll also not remove any capabilities.

Give us feedback

Keeping our goal in mind, please let us know how we can make the cloud-to-cloud migration feature better. Here are some ways you can give us feedback:

Leaving a comment below
Emailing my amazing product manager Swarna at smehta2@atlassian.com

We’d love to hear how we can help you.

Comments

Sean Riddle_jgi1rt

https://www.salto.io/jira

Jihan_5l5j6x

Hi Avi - I saw this yesterday but I'm only seeing Confluence in the option. We have a client moving cloud to cloud, both Jira and Confluence. Are both products supported? Thanks for this feature, pretty cool. Will apps and plugins be supported?

Avishekh Das

@Jihan We're rolling out Jira based on some cohorts, so you may not see this feature yet. But rest assured, we're rolling this out very soon. For now, you can use the Confluence feature at admin.atlassian.com and use the Jira feature by logging into your cloud site and selecting Settings > System > Migrate cloud site. Documentation is available here.

Khadjha Constantine

how can you opt out of the new experience? it seems that my experience is locked to opt in as an org admin, although i have legacy migrations and saved migrations on in the previous experience.

Avishekh Das

@Khadjha Constantine Can you please raise a support ticket at https://support.atlassian.com/contact/ and we'll take a look at it?

Paula Hidalgo

I used the Migrations Dashboard to get a snapshot of my cloud stats: number of project, number of issues, storage used, customers, groups, and installed apps. Where can I find that information in a single page visit?

James Webster_w2khgh

Hello,

Has anyone else found that the new data management tool has broken the single project Cloud to Cloud migration functionality?

Previously, only the associated project data (statuses, custom fields etc) from the origin instance was migrated but now it migrates the Project specific config and issues etc but also the whole instances statuses, customs fields, etc, etc).

It makes a big mess!

Nicole Radle

Sorry, but I don't like the new migration tool.
It failed, even though it flagged everything as feasible during the preliminary check.
According to the report, user-specific fields are not migrated and I am supposed to create everything manually and then import the data via CSV.

Norm Lee

This does not support Jira Service Management projects?

Lara Bailey

@Norm Lee Indeed I came to the same conclusion, despite

1) It says here that JSM team-managed projects aren't supported
2) It says here "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"

So #1 indicates that company-managed JSM migration should work, and #2 indicates that if the new way doesn't work, the old should - but it just doesn't.

I've tried to migrate a company-managed JSM project using both, and the old way just redirects me to the new, and in the new way, no JSM projects appear.

Interestingly, it says here "The capability to move Jira Service Management data from one instance of your Jira Cloud to another is only available when you have signed up for our Early Access Program (EAP)."

So I guess that's it - it doesn't work right now / yet.

Would be nice to know when they expect it to be out / how to sign up for the EAP, and it would be great if the documentation was accurate and consistent, so I didn't have to waste 6 hours setting up a new Jira instance, trying to migrate to it, and then figuring out and explaining why I couldn't, despite it indicates I should be able to in some pages.

Lara Bailey

New day, new search, managed to find the EAP for JSM cloud-to-cloud migration:

https://community.atlassian.com/t5/Jira-Cloud-Admins-articles/Early-Access-Program-for-Copy-Product-Data-for-Jira-Service/ba-p/2500826

And in the comments, there's info on when it will be mostly functional and available to everyone, looks like June 2024, but that "Assets and Automation rules may take longer as they are more complex for us internally. But we're on it!"

Now all that needs to be fixed is the many web pages (including this one) that lead you to believe the JSM cloud-to-cloud migration is currently available and working.

Norm Lee

@Lara Bailey Thank you! You helped us dodge the bullet of finding this out on the day of the scheduled migration. We're going to have to do the migration via Export/Import of CSV files then.

Rory Strickler_8epti1

Is there a rough date on when we can expect the JSM migration option will hit GA? We are quite keen to get some of these projects migrated.

Mike Maurer

So far it worked very for me. In had a couple of Cloud-to-cloud-migrations during the last months.

Jimmy Ghostine

Hi Avi,

Can this feature be used to merge multiple cloud sites in one?

Or should we do it by merging it first in a DC instance and then perform a backup and restore in the destination cloud as explaining in the following documentation:

Regards,

Patrick Vijgeboom

We are creating a new instance for test purposes. Can we use this to copy data from our production environment to the test instance?

And is it possible to update the test instance or does it overwrite all data? For example when we configured permission schemes, workflow and automations, will these things deleted when we copy data again to refresh our test instance?

Mathew Lederman

The 'Start copying' nomenclature doesn't make sense here since you go to the same place for existing copies where you may want to check status. Took me nearly an hour of digging and research to figure out there's no separate place to go for reviewing historical data copies.

The button should just be labeled "Copy data center" or "Copy data home" or something that makes it clear this is the place to go for all data copy details, not just to start new copies.

Rune Rasmussen

A bit of late feedback.

Only being able to select Projects is a severe limitation.

We often have the need to copy Jira Schemes or Assets Schemas without moving actual Projects.
We also need to copy a Project with its configuration only without moving Work Items.

The use case for us is testing and PoC work in a Sandbox, or entirely separate site, where we rarely need an entire Project and all its Work Items, but maybe just a couple of Workflows, some Screen Schemes, Automations, and an Assets Schema or two.

Being able to copy individual configuration items would be highly beneficial for us.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

jira-cloud

jira-administration

administration

new-to-jira

cloud-migration

cloud-to-cloud

data-management