Post-Migration Actions

After you perform the migration to Tenable Core, perform the post-migration action items for all new instances of Tenable Core:

Instances of Tenable.sc

If you changed the Tenable.sc hostname during the migration, update the hostname on your license. For more information, see the Tenable Community Guide.
To continue learning about Tenable Core, see the Tenable Core + Tenable.sc User Guide.

Instances of Nessus Professional

Reset your Nessus activation code. For more information, see Reset Activation Code in the Nessus User Guide.
To continue learning about Tenable Core, see the Tenable Core + Nessus User Guide.

Instances of Nessus Manager

Reset your Nessus activation code. For more information, see Reset Activation Code in the Nessus User Guide.
If you changed the Nessus Manager IP address during migration, you must reconfigure Nessus Manager in Tenable.sc. For more information, see Nessus Scanners in the Tenable.sc User Guide.
To continue learning about Tenable Core, see the Tenable Core + Nessus User Guide.

Instances of Nessus Managed by Tenable.sc

If you changed the Nessus IP address during migration, you must reconfigure Nessus in Tenable.sc. For more information, see Nessus Scanners in the Tenable.sc User Guide.
If you deployed a new instance of Tenable Core, reconfigure any advanced configurations (for example, customized nessusd.rules files or local scan results) in Tenable Core.
To continue learning about Tenable Core, see the Tenable Core + Nessus User Guide.

Instances of Nessus Managed by Tenable.io

If you deployed a new instance of Tenable Core, reconfigure any advanced configurations (for example, customized nessusd.rules files or local scan results) in Tenable Core.
To continue learning about Tenable Core, see the Tenable Core + Nessus User Guide.

Instances of NNM

Update your Monitored Network Interfaces in NNM to reflect your updated NICs. For more information, see NNM Settings in the Nessus Network Monitor User Guide.
If your NNM instance is linked to Tenable.sc, and you changed the NNM IP address during migration, you must reconfigure NNM in Tenable.sc. For more information, see NNM Instance Settings in the Tenable.sc User Guide.
To continue learning about Tenable Core, see the Tenable Core + NNM User Guide.