Error "Your cloud subscription doesn't support Assets" during migration from data center

[Daniel Witkowski]

During migration setup, initialized on data center on the Pre-migration checks page, the process fails with the following error:

"Your cloud subscription doesn't support Assets."
"Assets is a native feature on Jira Service Management Cloud Premium and Enterprise. To migrate your assets data to cloud, upgrade to Premium or update your selection to remove assets data from your migration."

Our Cloud site does not have Jira Service Management Premium (we have Standard). However:
- We do not use Assets (Insight) in Data Center.
- We do not have any Assets data.
- We do not intend to migrate or use Assets in Cloud.
- In the migration setup, under "Choose your migration options," Assets is explicitly unselected.
- This occurs even when migrating a single project with no issues in it.
- This occurs regardless of whether all projects or only one project is selected.
- The migration stage is set to "Testing." (at the beginning of the migration plan setup)

Despite explicitly skipping Assets in the migration options, the pre-migration check still blocks the migration due to lack of JSM Premium in Cloud.

Expected behavior:
If Assets is not selected for migration and no Assets data is intended to be migrated, the migration should proceed without requiring JSM Premium in Cloud.

Actual behavior:
The migration is blocked at the pre-migration check stage due to Assets capability validation, even though Assets is unselected and not used.

We need clarification on why the Assets dependency check is triggered and what must be removed or adjusted in the Data Center instance to allow migration without requiring JSM Premium.

We plan on having Jira Software in Premium tier and Jira Service Collection in Standard

We have even tried disabling the Assets through REST API on Data Center, to no avail. The assets were in fact disabled, but the migration still fail at the checklist.

[Trudy Claspill · Accepted solution]

Hello @Daniel Witkowski 

For a question about what appears to be a bug in the product you need to contact Atlassian technical support. The site for that is

https://support.atlassian.com/contact/#/

I recommend you select the Migration Support option.

[Daniel Witkowski]

Hi Trudy,

Thank you for the answer.

That indeed appears to be a bug, though I've stumbled upon it on such an early stage of migration, that I thought I must be doing something wrong. I have also read that Assets were to be included in Service Collection Standard

Assets is now part of Service Collection Standard - Atlassian Community

Which confuses me even further. If it really were a part of standard collection, then JCMA must have been not updated to take this into account.

I already created a ticket to Atlassian Support in this matter

[Trudy Claspill]

It would be great is you can report back here what you learn from Atlassian.

The reference you provided does say that it is rolling out, and applies to the Service Management Collection.

Did you subscribe to the Service Management Collection, or just to the JSM app?

If you subscribed to the collection perhaps the change has not yet rolled out to your instance since the article was published on 5 February.

[Daniel Witkowski · Accepted solution]

Hi all,

After meeting with Atlassian Support, and trying basically everything they suggested and what Dr Ankita has suggested, nothing worked. Turns out that Atlassian Support can flag you Atlassian tenant, and all your next migrations in Jira will just skip this assets check. So contacting the support is mandatory. Currently I've done few migrations, since the flag value changed I had no issues

[Ricardo Herrera]

I have the same issue today. Could any of those who created a support ticket paste the URL here for monitoring it, please?

[Trudy Claspill]

@Ricardo Herrera 

You won't be able to access the support tickets raised by other Atlassian customers. I recommend you raise your own support ticket.

And it would be lovely if anybody in this discussion would post back what they learn from Atlassian.

[Adrian Pratt]

Got this from support.

"This is a known issue affecting the non-asset migrations, we have a pending feature request"

You need to contact support, so they can add you to an exclusion list to unblock you. You also will need to clear the plugin cache after that, and re-auth the cloud token, which support will give you details.

[Ricardo Herrera]

Thanks a lot, both.

[Trudy Claspill]

@Adrian Pratt 

Thank you for sharing your update!

Did Atlassian provide you with the feature request ID/link?

[Dr_ Ankita Mehta-OpsHub_ Inc]

Hi @Daniel Witkowski

Hi there,

Yeah, this one trips up a lot of teams. Even if you’re not using Assets, the migration assistant doesn’t just check data. it validates whether the Assets capability exists in the source environment. A few things worth reviewing:

• Make sure the Assets/Insight app is fully uninstalled, not just disabled via REST or UI.
• Check for leftover custom fields, object schemas, or automation rules referencing Assets.
• Look for any system-level configuration that still registers the Assets module.
• After cleanup, create a fresh migration plan instead of reusing the same one.
• The check is capability-based, not usage-based - so even an inactive module can trigger the Premium requirement.

In your case, you may want to explore OpsHub Migration Manager (OMM). It supports phased or full migrations, doesn’t block based on unused feature tiers, and preserves comments, attachments, relationships, and field mappings without downtime or data loss. As an Atlassian Solutions Partner, we’ve helped teams move from DC to Cloud without needing to upgrade just to pass platform validations.

All the best!

[Adrian Pratt]

I've the same problem.

And raised it with support. fingers crossed it can be fixed quickly