What to do with skipped records after upgrade to new ServiceNow version

[ceraulo]

Hello!

I am managing our client's upgrade to San Diego. I have created update sets for the skipped records. Should I commit these update sets AFTER the upgrade in our production instance?

Thank you.

[Ankur Bawiskar]

Hi,

you need to review those and decide whether you want to revert to base version or keep your version

good explanation here

What’s the process to review and address skipped changes?

regards
Ankur

[ceraulo]

@Ankur Bawiskar I have reviewed and addressed the skipped changes and saved to an update set. My question is when to commit the update sets to production. Should it be done once the upgrade is completed or before the upgrade starts?

[Ankur Bawiskar · Accepted solution]

Hi,

you can only review the skipped records once upgrade completes.

You need not capture them again in an update set.

You can either revert to base version, merger or keep your version as it is

Regards
Ankur

[ceraulo]

Hi Ankur,

My understanding of the upgrade process is to upgrade first the pre-production instance. After the upgrade, review the skipped records. The decisions made to the skipped records are saved on an update set.

When we upgrade production instance, there will be skipped records. My understanding is I don't need to review this since it is expected that skipped records in production is same as pre-production. I will only need to commit the update set I created in pre-production when I reviewed the skipped records.

My question is should I commit the update set to production BEFORE or AFTER the upgrade?

Thank you.