FAQ
Consider the following frequently asked questions when planning your upgrade.

For more information about local machine, Tenable Nessus, and Tenable Vulnerability Management requirements, see Requirements.

For information on what data is transferred from Tenable Nessus to Tenable Vulnerability Management, see Migrated Data.

All data described in Migrated Data, except for scan history, is automatically transferred to your instance of Tenable Vulnerability Management. You can optionally choose to upgrade scan history.

Tenable® recommends backing up Tenable Nessus regularly as a deployment best practice, but the upgrade assistant does not remove any data from Tenable Nessus. Your Tenable Nessus deployment continues running as configured.

After you upgrade from Tenable Nessus to Tenable Vulnerability Management, Tenable Nessus becomes a managed scanner. You can no longer use that instance of Nessus as a standalone scanner, but you can log in and see scan history for the upgraded scans.

Tenable® recommends running the upgrade assistant only once, from your existing Tenable Nessus deployment to a Tenable Vulnerability Management instance. Once you upgrade your data from Tenable Nessus to Tenable Vulnerability Management, Tenable Nessus becomes a managed scanner, so the option to upgrade again is no longer available.
You can upgrade scan history multiple times, until you disable migration.

The upgrade assistant is currently only available via the Tenable Nessus user interface.

Upgrade time varies depending on the number and complexity of your scan policies.

For more information about Tenable Vulnerability Management, see the Tenable Vulnerability Management documentation.