Skip to main content
Gainsight Inc.

Scorecards 2.0 FAQs

What are the capabilities of Scorecards 2.0 and how is it different from Scorecards 1.0?

Scorecards 2.0 is a new version of scorecards, built on top of Gainsight's tech stack (MDA). It is built with Gainsight standard Company and Relationship objects. For more details on standard objects, see Scorecards 2.0 article. Following are the technical aspects of Scorecards 2.0, for both Account and Relationship Scorecards: 

Scorecards 2.0 (Feb. 2017+)
  Account Scorecards Relationship Scorecards
Tech Stack Relational Data Store (Postgres) Relational Data Store (Postgres)
Object Structure Linked with GS Company Object Linked with GS Company, Relationship Object
UI New UI Look and feel of the current UI
  • Previous: Usage Data in SFDC
  • Now: Scorecard Fact and History in Postgres
  • Previous: Scorecard Fact and History in Redshift
  • Now: Scorecard Fact and History in Postgres
Scorecard Mass Edit
  • Previous: UI Views
  • Now: Configure using Report Builder

No change. Configure using Report Builder. 

Group Scoring Yes Yes
Score Overrides (Exceptions) Yes  Yes
Smart Signs No  No
Can I use both the new version of Scorecards and the old version of Scorecards (Account and/or Relationship)? 

Yes. You can configure Scorecards 2.0 and use it alongside Scorecards 1.0 in your org. For more information, see Scorecards 2.0.

Note: If you enable Scorecards 2.0, be sure to add it to the corresponding C360/R360 section. 

Will migration result in loss of data or restrict access to Scorecards 1.0?

There will be no loss of data and you can still access Scorecards 1.0.

Following are some migration scenarios: 

  1. If you want to use new capabilities, like group scoring, exceptions for overrides, and multiple scorecards (coming in Spring release), then our recommendation is to plan to move to Scorecards 2.0. 

  2. If you want to use Scorecards 2.0, but need access to customer's historic data in Scorecards 2.0, then we recommend the following alternatives: 
  • Recommended: Configure Scorecards 2.0 and set it up so that the data is being collected in Scorecard 2.0. Continue using the old version of scorecards for about 2 to 3 months (the period of time for which we believe the value of historic data is valuable).
    • After 3 months, given that there is enough scorecard history available, you can turn off the old version of scorecards and move to Scorecards 2.0. Then you can mark Scorecard 2.0 as primary (For more details, refer Configure Scorecards 2.0).
  • Another Alternative: Wait for the migration utility (for more details on what will be in scope and what will not be in scope, refer the next question) which will help you move your scorecard historic data, and enable you to use all of the current and future enhancements planned for Scorecards 2.0.
  1. If you are happy with the current functionality of Scorecards, no need to worry. We intend to support both versions of scorecards for the near term. However, any new functionality will only be built for Scorecards 2.0. In the long term, we want to help you move to Scorecards 2.0 and will stop supporting other versions.
What is the Scorecard 2.0 migration utility and when will it be available?

Purpose of the utility tool

A migration tool is being built for a future release that will copy the data from the scorecard history table and populate the Scorecard 2.0 tables. When you use Scorecards 2.0, you can use the data which you had already created using Scorecards 1.0 and create reports and see the past data as well as current data. There is no impact on the existing data store. The data from Scorecard 1.0 tables will not be deleted and you can continue to use it for existing reports and manage it.  

What will be possible: 

  • Recreate the measures and scorecard configuration
  • Migrate the historic data (most likely for the last 3-4 months)

What will not be possible:

  • Set Score and Reports - The reports and rules created to support existing account/relationship scorecards will not be migrated and will require manual setup.
Is it possible to maintain historical data in both Scorecards 2.0 and Scorecards 1.0?

This should be possible. The utility's purpose will be to copy the data from scorecard history table and populate for the Scorecard 2.0 tables. You can continue to maintain the data and associated reports, etc. 

Can Gainsight TechOps help us migrate the historic data and start using Scorecards 2.0?

No, this is not possible.

If we choose not to migrate historical data from Scorecards 1.0 to 2.0, how can we run reports to see historical trends?

The recommendation is to use the reports from the old version of scorecards for some period of time until you have Scorecards 2.0 with enough history, and then you can switch over to Scorecards 2.0 completely. 

If we activate Scorecards 2.0 and do not migrate the historical data from Scorecards 1.0, can we do that at a later time?

If you configure Scorecards 2.0 now and start using it, then it will not be possible to migrate historic data in the future.

If we migrate at a later date and the measures in Scorecard 2.0 are different, how would the migration work?

The migration won’t work if the measures created in Scorecards 2.0 are different from those in Scorecards 1.0. If you want to use Scorecards 2.0, and need to access the customers' historic data in Scorecards 2.0, then we recommend that you configure Scorecard 2.0 and set it up so that the data is being collected, but continue to use Scorecards 1.0 for about 2 to 3 months (the period of time for which we believe historic data is valuable). At that point, Scorecards 2.0 will have adequate historic data.

  • Was this article helpful?