---
sourceDocument: Xanadu Platform Analytics
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/now-intelligence

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Migrating Performance Analytics scores

# Migrating Performance Analytics scores {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

The Performance Analytics Scores \[pa_scores\] table was split into two tables. This structure
helps with processing large numbers of scores. You can migrate your scores from the old table
structure to the new, using the score migration tool.  
Warning:  
The new table structure is not supported on Oracle databases.

In Istanbul, the Scores \[pa_scores\] table was split into Scores Level 1
\[pa_scores_l1\] and Scores Level 2 \[pa_scores_l2\]. The pa_scores_l2 table contains the
second-level breakdown matrix of scores and the pa_scores_l1 table contains all other scores.
This separation of scores ensures optimal performance when collecting and analyzing scores, and
enables larger sets of scores. New instances created on the Istanbul release or
later use the new scores tables by default.

Instances created prior to Istanbul still use the original Scores \[pa_scores\] table after upgrading.  
Important:  
For full details on migrating Performance Analytics scores to the new table structure, see [KB1294371](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1294371).

## Migration Monitor {#pa-scores-migration__section_nln_2by_k1b}

After beginning the migration, you can track the migration status by navigating to Performance AnalyticsScores Migration Monitor.

If any errors occur during migration, contact Customer Service and Support to resolve the issue.

## Delays in starting score migration {#pa-scores-migration__section_rng_v3d_jhb}

If any of the following processes are running, score migration remains in the Waiting state until they stop:

* Data collector jobs
* Collection cleaner jobs
* Scoresheet editing
{#pa-scores-migration__ul_hhm_y3d_jhb}

## Schedule the Performance Analytics scores migration {#ariaid-title2}

Schedule the automated migration process to move existing scores to the new table
structure.

### Before you begin

Role required: admin. Users with the pa_admin role can view the migration monitor page but cannot schedule the migration.

### About this task

Migrating scores improves performance and scalability of
Performance Analytics. Migration should be performed during off-peak hours.

During
migration you cannot collect, modify, or delete scores. Scheduled data collection
jobs do not run during migration. After migration completes, check any data
collection jobs that were scheduled to run during the migration, as these jobs were
suspended.  
Note:  
* The scores migration can take several hours to complete, depending on the number of scores. Schedule the migration in a non-production instance and then carefully plan the migration in production.
* The original Scores \[pa_scores\] table is truncated 10 days after successful migration.
{#start-scores-migration__ul_ow1_242_pjb}

### Procedure

1. Navigate to AllPerformance AnalyticsScores Migration Monitor.
2. Click the Schedule Scores Migration button.  
   The scores migration is scheduled. The page displays the time that the migration is scheduled to start, and the estimated completion time.
3. **Optional:** Click the Logs or Active Jobs links to view additional information about the migration.  
   If there are any data collection or cleanup jobs running when you start the migration, the migration waits for those jobs to complete before beginning. All scheduled collection and cleanup jobs are paused during the migration.

### What to do next

If the migration fails for any reason, contact Customer Service and Support for assistance. Existing scores remain in place.

*[\>]: and then