Too many objects from Assets

This insight checks whether your total number of objects from Assets is above the hard limit. When you exceed this limit, your migration will be blocked by a pre-migration check in the Jira Cloud Migration Assistant.

What's the problem?

Jira Cloud has a hard limit on the total number of objects, because of the move to the new Assets platform. To make sure that your Jira performance and responsiveness isn't affected, we had to introduce limits in certain areas of Assets.

Hard limit vs. Free limit

Exceeding the hard limit will block your migration. If you're in this situation, you must clean up your objects before you migrate.

Additionally, Jira Cloud also has a free limit for Assets, currently set at 50,000 objects. Any objects above this limit will be billed extra based on consumption-based pricing (either per-object for monthly subscriptions or according to specific tiers for annual subscriptions). It might be a good idea to clean up your archived or old objects before you migrate to reduce your license costs. Objects above the free limit will also require installing an additional Marketplace app (Extra objects for Assets) to store them.

Learn more about licensing for Assets

What’s the recommendation?

If you're above the hard limit, you must reduce the number of objects. If you're above the free limit, we recommend that you review your objects and clean up the ones you no longer need to reduce your license costs.

Clean up objects RECOMMENDATION

Here are some tips and best practices on deleting unused objects.

Prioritize what to delete

Start with:

• Archived objects: Jira Cloud doesn't have the concept of archived objects, which means your archived objects will become regular objects after migration and will be billed extra if you're above the free limit. Reviewing and deleting them is the best place to start.

• Unused objects: Objects not referenced by other objects or Jira issues.

• Orphaned objects: Objects with no inbound or outbound references.

• Objects not updated or used in a long time: Use date attributes to find stale data.

Identify objects using Assets Query Language (AQL)

Assets Query Language is your main tool for finding objects to delete. Here are some useful queries:

• Find archived objects

Status = Archived

(Replace Status with your actual status attribute name.)

• Find objects not referenced by others (orphans)

object NOT HAVING inboundReferences()

Or, to find objects not referencing anything else:

object NOT HAVING outboundReferences()

• Find unused objects (not linked to Jira issues)

"Issue" IS EMPTY

(Replace "Issue" with your actual attribute for Jira issue links.)

• Find objects not updated in the last 180 days

Updated < -180d

Learn more about AQL

Check out the AQL documentation for more queries and details.

Advanced searching: Assets Query Language

Bulk deletion methods

There are a few ways that allow you to bulk delete your objects efficiently:

• Bulk actions in the UI
• CSV export/import to delete objects that aren't included in the CSV
• Assets automation and REST API

For more info on how to use these methods, see How to bulk delete assets efficiently

Order of deletion

• Delete child objects before parents if there are dependencies (to avoid reference errors).

• Delete archived and unused objects first to minimize risk.

• Always check for references: Use AQL to ensure you’re not deleting objects still in use.

Safety and performance tips

• Always back up your data before bulk deletions.

• Test your AQL queries with a small batch before running on all objects.

• Monitor system performance: Large deletions can lock the database or cause UI lag.

• Disable automation rules after use to avoid accidental deletions.