Migration to the new verinice generation

How the import works

1. Export VNA file

   From verinice Single-User / verinice.PRO, as usual.

2. Specify destination and credentials

   URL of the target instance, along with username and password. The remaining parameters are pre-filled.

3. Perform a Dry Run

   The import runs without actually transferring data and reports errors before they affect production. A Strict Run performs an even more rigorous check.

4. Start import

   Success or errors are acknowledged; the log file can be copied or saved.

Tip: Save the log file along with the VNA file. This will save you the trouble of reconstructing later what was transferred and when.

What You Should Plan For

• Preparatory Work Before Export: The new generation documents the implementation of a requirement in the link to the target object, no longer in the requirement itself. To ensure this deduplication works, check the modeling, building blocks, building block owners, and risk definitions beforehand. The specific adjustments required are listed in the documentation for the VNA Importer.
• One-way street: SerNet supports migration to the new generation, but not the reverse.
• Legacy fields: A few fields from verinice Classic no longer exist in the new generation, such as tags. They are intentionally not transferred.
• User-specific fields: The import of data from a custom configuration can be supplemented in consultation with the verinice.Team.
• Unit quota: If the maximum number of units has been reached, first delete a unit or purchase additional ones before running the import.
• Sample Check After Import: Check the data for completeness. Refer to the documentation to see what has changed due to the version update.

For verinice.onprem without net access

For importing into other target environments, such as airgapped verinice.onprem, the VNA Importer is available as a Java client. Please contact verinice Support at support@verinice.com for further information.

Availability