Plan Your NNM Appliance Migration

The Tenable Appliance to Tenable Core migration process varies depending on your current Tenable Appliance deployment and your desired Tenable Core deployment. To confirm you meet the application version requirements, see Version Requirements.

NNM Standalone Instance

Tenable Appliance + NNM standalone instances can migrate to Tenable Core via the backup and restore method. For more information, see Perform a Backup and Restore Migration.

NNM Instance Linked to Industrial Security

Industrial Security is end-of-life (EOL). For information about EOL dates and policies for Tenable products, see the Tenable Software Release Lifecycle Matrix and Policy.

Tenable Appliance + NNM instances linked to Industrial Security can migrate to Tenable Core via the backup and restore method. For more information, see Perform a Backup and Restore Migration.

NNM Instance Linked to Tenable.sc

Tenable Appliance + NNM instances managed by Tenable.sc can be migrated by the backup and restore method or by deploying new instances of Tenable Core, depending on the needs of your organization.

  • If your highest priority is to retain your NNM instance configurations, you must migrate via the backup and restore method. For more information, see Perform a Backup and Restore Migration.

  • If you prefer a faster migration and you are willing to reconfigure your NNM instance configurations after migration, you may prefer to deploy new instances of Tenable Core instead of migrating. For more information, see Deploy a New Instance.

    Note: Tenable recommends retaining the same IP address before and after your migration. If you use the same IP address for your appliance and for Tenable Core, Tenable.sc stays connected to the instance.

    If you change the IP address, you must reconfigure the NNM in Tenable.sc.

NNM Instance Linked to Tenable.io

Tenable Appliance + NNM instances managed by Tenable.io can be migrated by the backup and restore method or by deploying new instances of Tenable Core, depending on the needs of your organization.

  • If you do not know the appliance's Tenable.io scanner group or your Tenable.io linking key, you must migrate via the backup and restore method. For more information, see Perform a Backup and Restore Migration.
  • If you know the appliance's Tenable.io scanner group and your Tenable.io linking key, you may prefer to deploy new instances of Tenable Core instead of migrating. For more information, see Deploy a New Instance.