Asset referenced fields migration to Cloud

Question

Hello community,

as some of you know, I am not big fan of cloud, so I spent little bit of investigation, but I am stuck and got different project to work on.

One of my ex-clients reached me, that they are planning to migrate into Cloud Jira.

They are huge instance with 12k users, unlimited agents and using Assets extensively since it was Riada Insight.

There are like 300 Assets field and 250 of them are 2-5 level of referenced field.

Questions:

* I did not find a way how to easy do PoC of migration via some assistant (Assets not supported)
* I did not find a way how to present the implementation of referenced fields
* I did not find any documentation how to handle atribute reading and prefiling them into appropriate fields based on rules in another objects. Mostly done in behaviours.

Just point me, will forward to the guys how to handle that.

Thanks Tom

Melbrin NGOUILOU · Answer

Hi,

Not sure about what you asking (maybe because I'm french haha ^^) but you can make an AQL to prefill an asset field based on other objects. In data center you can make the assignation strict., which basically means you can force the value of an asset field based on others asset fields. On the cloud you can only filter it not force the value except via automation.

I am used to migrate asset databases and handling referenced fields in Excel before reimporting it in another database. Can you try adding some examples for me to get it clearer and maybe try to give a hand ?

Marc -Devoteam- · Answer

Hi @Tomáš Vrabec

As the client is sizeable, you the client could reach out to Atlassian for help.

See the Fastshift program, https://www.atlassian.com/migration/fastshift

Trudy P Claspill · Answer

Hello @Tomáš Vrabec

When I last worked with a DC to Cloud migration (in early 2025) that included migrating Assets information we ended up using a third party app.

Insight Assets Backup & Migration

I don't think the Assets implementation I was migrating was as extensive as what you are looking at, so additional vetting of that vendor's app would be required.

As I recall it was possible to try the migration using the apps under trial but only a small number of assets would actually be migrated.

The vendor was very responsive as we were working out the details of how to use the apps.

I'm not sure that I understand what you are trying to express with your third question. Can you provide some additional details about this use case? Are you trying to read data from Asset Objects and fill non-object fields in Jira issues?