SecurityScorecard is migrating all v1 custom scorecards to v3. This migration will be performed by our engineering team beginning May 4, 2026. No action is required on your part to complete the migration.
You will receive an email notification when your scorecards have been migrated.
What to expect
When the migration occurs, a duplicate of each v1 custom scorecard is created with "v3" appended to its name. For example:
- Original scorecard: Example Name
- Migrated scorecard: Example Name v3
The original v1 scorecard will be deleted on or after May 4, 2026. The v3 scorecard works the same way in the UI as your previous v1 scorecard.
Required updates after migration
While the migration is automatic, there are two things you need to update after your scorecards are migrated.
API calls
If you use the SecurityScorecard API, you need to update your API calls to use the new scorecard ID assigned to your v3 scorecard. The scorecard ID changes during the migration, so any existing API calls referencing the old ID will no longer work.
You can find the ID in the URL when viewing a custom scorecard. Example:
https://platform.yourorg.com/#/scorecard/e4b1f2e1-ff1e-4015-bcb1-1caa19f3fc1d/company-overview
Rules
If you have any rules configured to use a v1 custom scorecard, you need to update those rules to reference the corresponding v3 scorecard.