Exports

Exports turn the audit UI into something you can share. Use them when findings need to move into QA, reporting, migration planning, or team handoff.

Inventory exports #

Inventory exports are for the table you are currently reviewing, such as Blocks, Patterns, Template Parts, or Navigations.

• Use these when you need a summarized view of filtered inventory rows.
• Block inventory exports include normalized fields for block name, instances, and sources.
• Exports are generated server-side and downloaded directly in the browser.

Source exports #

Source exports begin after drill-down. They are for the exact records behind one block, one pattern, one template part, or one navigation target.

• Use source exports when you need page- or template-level evidence.
• They are the best fit for QA checklists and remediation worklists.
• They are also the most useful export when another team needs to validate real source locations instead of aggregate counts.

Typical uses #

• Reporting current block or entity scope to stakeholders.
• Preparing QA validation for cleanup or redesign work.
• Handing exact affected sources to migration or delivery teams.

Default limit note #

By default, exports are capped to the first 5,000 filtered rows per export action. If you hit that ceiling, narrow filters and export the audit in smaller slices.

If you need larger caps, that is a developer-level setting rather than a standard admin workflow, so it is intentionally out of scope for this guide.

Before exporting for reporting, review Scan Health so you know the latest baseline is current enough to trust.