Overview
NIST CSF 2.0 introduces key improvements and broader applicability for modern cybersecurity programs. In Hyver, you can either migrate your existing CSF 1.1 data or start fresh with 2.0. This article explains how to initiate and manage the migration, and what gets carried over.
How to Start Using CSF 2.0
Go to the Maturity page
Open the framework selector
Choose NIST CSF V2.0
From this point, you can immediately begin entering data. You don’t have to migrate data from version 1.1 to begin working in 2.0.
How and When to Migrate Data
When you first switch to CSF 2.0, Hyver administrators are prompted with the option to migrate from 1.1
If you choose “Not now”, the option will appear again the next time you open the maturity page
Admins can also trigger migration when changing the primary framework to 2.0 via Settings > Maturity
Important: You can migrate data only once, so plan accordingly. If you need to finish entering CSF 1.1 data first, it’s okay to delay the migration.
What Happens During Migration?
Hyver maps and transfers the following data from CSF 1.1 to 2.0:
Element | Behavior |
Manual evaluations | Transferred directly or averaged if multiple 1.1 subcategories map to one 2.0 subcategory |
Reasons for ratings | Included if part of manual evaluation |
Comments | Migrated and labeled as imported from CSF 1.1 |
History | Partial; includes notes on what was migrated and from which subcategories |
Findings and Assets | Migrated if mappings are valid; user-modified mappings take priority |
Working with Both Frameworks
You can switch between CSF 1.1 and 2.0 on the Maturity screen at any time
Data between the two frameworks is separate — updates in one do not affect the other
Only the primary framework is used for platform-wide calculations like risk dashboards and mitigation plans
Wrap-up / Next Steps
Whether you’re migrating now or easing into CSF 2.0 gradually, Hyver makes it flexible. Your data is preserved, the transition is smooth, and you can start building maturity in version 2.0 today.