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; } } }

How to migrate DC to Cloud without Assets

Weronika Hałdaś_Deviniti_

Hi,

Using JCMA, I’m trying to migrate one JSM project and one JSM application from my local Data Center to the Cloud.

Every time the Pre-migration check shows the following error:

image (35).png

I don't select Assets at the 'Choose' step:
image (36).png

I had one issue with an Asset in a project that I didn't migrate (I've deleted it)
I removed all Assets from my DC
I did Jira re-index and Assets re-index (after removing them)

Does it mean that I can't migrate JSM project until I have Jira Premium on the Cloud side? Or is it a bug?

Comments

Charlie Misonne

Hi @Weronika Hałdaś_Deviniti_

If you're not migrating any schemas there should be no need to upgrade to JSM Premium on Cloud.

Does this error actually block you from proceeding?

Weronika Hałdaś_Deviniti_

Hi @Charlie Misonne

Yes, I can't proceed with this error.

Weronika Hałdaś_Deviniti_

I've also:
-tried to reinstall the JCMA,
-asked my colleague to check this on their end (also on the environment without asstests at all) - same result

Charlie Misonne

Ok that's definitely a bug.

I found the report on [MIG-2478] with Assets migration GA, JCMA preflight check blocks the migration if JSM premium is not activated on target cloud - Create and track feature requests for Atlassian products.

There are 3 workarounds on the ticket:

ensure the JSM premium license is enabled on the tenant site or temparorily enable the JSM premium trial on cloud.
If no JSM assets to be migrated, and DC is not using assets, uninstalling JSM assets will also unblock the migration.
If DC needs assets plugin, and JSM premium trial is not able to be added on cloud site, please reach out to migration support team.

So you could start a trial of JSM Premium and revert to standard after the migration. It's probably the easiest way.
Or look into the 2 other options.