# saved reports

GLOSSARY, read 10 Nov 2026

**Definition.** Saved reports are the dashboards and scheduled outputs that stakeholders already read. They are often the most visible part of a migration, because a missing report is noticed in a week. Nucleus states it maps Kenna reports to equivalent Nucleus views rather than cloning them.

Inventory every report with its audience, schedule and source fields. Retire the ones nobody opens, rebuild the rest, and send the first new report side by side with the old one.

Kenna's API includes a call to refresh reporting data, and only one client report refresh can run at a time, so old and new numbers should be compared on the same refresh date.

## A sourced example

Nucleus's Kenna page, last modified 2026-08-25, says that during the migration assessment it maps Kenna reports to equivalent or better Nucleus views and does not clone Kenna.

## Related terms

- [Kenna risk meter](/glossary/kenna-risk-meter/)
- [SLA carry-over](/glossary/sla-carry-over/)
- [user and role migration](/glossary/user-and-role-migration/)
- [parallel run](/glossary/parallel-run/)

## Sources

- Source for the example: saved reports: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/saved-reports/
