Issue Summary

The Jira pre-migration checklist documentation is outdated and still references the old Assets custom field limit of 20 objects per field. This is incorrect as of July 27, 2026, when the limit was raised to 200 objects per field.

Actual Results

Customers following this checklist during migration planning are being misled. The old threshold is causing confusion and unnecessary remediation work for migrations that are actually within the new supported limit.

Steps to Reproduce

1. Navigate to: [Jira Cloud Migration Assistant pre-migration checklist | Atlassian Support|https://support.atlassian.com/migration/docs/jira-pre-migration-checklist/]

1. Scroll to Section 11 – "Check if you've exceeded asset entities limit"

1. Observe the limit shown is still 20 objects per custom field

Expected Results

The checklist should reflect the new limit of 200 objects per Assets custom field (as announced on July 27, 2026).

References:

• Product release announcement: Assets custom fields, redesigned for scale

Action Required:
Update Section 11 of the pre-migration checklist and all associated SQL queries (e.g., HAVING count("OBJECT_ID") > 20) to reflect the new threshold of 200.

Workaround

Since the new 200-object cap went live on July 27, 2026, no configuration is required — all existing fields auto-scale automatically. In other words, the 200-object limit is the live, any information for fields with limit of 20 objects are false positives and can be safely disregarded until the tooling is updated