Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Quebec release notes
Table of Contents
Choose your release version
    Home Quebec Release Notes Quebec release notes Prepare your upgrade Upgrade planning checklist

    Upgrade planning checklist

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Upgrade planning checklist

    Plan and track the activities related to your ServiceNow instance upgrade. To help ensure that you complete all the tasks for a successful upgrade, follow the step-by-step instructions in the upgrade planning checklist to track and plan the upgrade.

    Some optional steps may not be appropriate depending on the number of instances, customizations, and so forth. Mark the ones you do not need in the N/A column.

    Tip: To download a PDF version of this checklist, click here.

    The process for completing steps for self-hosted customers may vary (for example, requesting an instance clone or upgrades). These differences must be considered during planning.

    Customer name:
    Product instance name: https://[instancename].service-now.com
    Other instance names https://[instancename].service-now.com https://[instancename].service-now.com
    Description Yes No N/A
    Phase 1 - Read the release notes and plan your upgrade
    1

    Review the Quebec release notes for the target ServiceNow feature release and patch, in addition to product and release documentation.

    For Quebec-specific upgrade considerations, see Pre- and post-upgrade tasks for various products.

    Phase 2 - Complete these planning tasks.
    2

    Confirm which ServiceNow instances are in-scope for upgrade.

    3

    Confirm the instance hosting model. For example, ServiceNow cloud, on-premise, or off-premise.

    4

    Based on the Quebec release notes and other release materials, determine new functionality or notable changes that need to be validated after the upgrade.

    5

    Confirm plans to enable or disable features introduced in the new product release.

    6

    Review the Browser support to determine browser prerequisites. For example, versions and types supported, and additional requirements for new UI versions. Compare these supported browsers to your corporate standard and identify any gaps.

    7

    Create a project plan for cloning, upgrading, and testing.

    8

    Identify the core team of testers, power users, and key stakeholders required to validate functionality in the ServiceNow instances before and after the upgrade.

    9

    Confirm whether there are any change freeze windows impacting the timing for environment clones or upgrades. For example, end quarter.

    10 Confirm which of the following situations applies to your ServiceNow non-production instances:
    1. Development and testing can be frozen until the production upgrade is completed.
    2. Continued development (and testing) activities need to continue in a non-production instance while upgrade, remediation, and testing activities are performed in parallel on another instance.
    3. Once the final upgrade to your production instance is complete, the cloning of your final production instance to your non-production instance will wait until after the production upgrade is complete.
    11

    Confirm the availability of other systems required for integration testing (key resources and environments).

    12

    Confirm whether there are any restrictions in which ServiceNow instances can be used for integration testing. For example, an interfacing system is only set up to access a specific ServiceNow test instance.

    13

    Confirm the testing scope and approach.

    14

    Create a comprehensive test plan including test cases for all core instance functionality and integrations.

    15

    Confirm the method for tracking any defects identified during testing.

    16
    Create a high-level implementation plan that covers:
    • the sequence and timing to upgrade non-production and production instances
    • the instances to be cloned
    • the instance to be used for integration testing.
    17

    Confirm whether there are any change freeze windows impacting the timing for environment clones or upgrades. For example, end quarter.

    Responsible: ServiceNow or Customer
    18

    Determine whether existing internal training materials, Knowledge Base articles in the customer instance, or other supporting documentation must be updated to align with the upgraded version. For example, changes in functionality or user interface.

    19 Optional: Schedule the ServiceNow Configuration Review, which provides recommendations to align the customer configurations with ServiceNow best practices.
    Note:

    There may be a service charge and require professional services engagement.

    20
    On your production instance, create a system clone and select your development instance as the Target instance. Notify impacted users and internal stakeholders of the scheduled date/time for cloning (from production) and upgrade of the non-production instance.
    Note:

    It is important to test on a system that reflects the production instance as closely as possible. If your non-production and production instances are the same size, include the production audit log and the attachment data, and ensure that you have deselected the exclude options.

    Phase 3 - Verify your upgrade configurations and schedule the development instance upgrade in HI
    21

    Check the configuration of the Check distribution for possible upgrade scheduled job to view how often and when it runs.

    22

    Verify that the Check distribution for possible upgrade sys_trigger is set properly for upgrading.

    23

    Verify that the Check database for possible upgrade sys_trigger is set properly for upgrading.

    24

    Schedule the upgrade in HI.

    25

    If applicable, request a version entitlement.

    Phase 4 - Upgrade and validate the development instance
    26

    Using the Upgrade Monitor, monitor the upgrade to your instance and validate that the upgrade to your development instance is complete.

    27

    After the upgrade for your development instance is complete, process the skipped records list in the Upgrade Monitor.

    28

    Identify your update sets.

    29

    Before and after upgrading, conduct smoke tests on your development instance. Use your comprehensive test plan to perform functional testing.

    Phase 5 - If applicable: Upgrade and validate your other non-production instances, such as your test instance
    30

    On your production instance, create a system clone and select your development instance as the Target instance.

    31

    Schedule the non-production upgrade in HI and verify your upgrade configurations.

    32

    Validate that the upgrade to your non-production instance is complete.

    33

    Install any optional plugins that were installed on your development instance.

    34

    Install any custom applications and post-upgrade fix scripts that you need.

    35

    Install update sets.

    36

    Perform functional testing and monitor the performance of your instance.

    Phase 6 - Prepare to upgrade the production instance
    37

    Confirm sign-off from IT and Business stakeholders that all non-production instance defects have been fixed and validated in update sets.

    Responsible: Customer
    38

    Confirm the core team of key stakeholders required to validate functionality in the ServiceNow instance after the production upgrade.

    Responsible: Customer
    39

    Confirm coverage for Day 1 support post-upgrade.

    Responsible: Customer
    40

    Create a Production Upgrade Implementation Plan that includes all upgrade steps, roles and responsibilities, communication plans, key contacts, support coverage for Day 1, and so forth.

    Responsible: Customer
    41

    Schedule a walkthrough and sign-off of the Implementation Plan with key stakeholders and the core team.

    Responsible: Customer
    42

    Submit and obtain approvals for change records as required by the organization change process.

    Responsible: Customer
    43

    Send a communication to key stakeholders and end users with details for the production upgrade outage, new features, and so forth.

    Responsible: Customer
    44

    Profile the performance of your instance before upgrading.

    45

    Use the ServiceNow Performance homepage to document the performance of your instance before the upgrade.

    46

    On your clone, perform functional testing and monitor the performance of your instance.

    Phase 7 - Upgrade the production instance
    47

    Schedule the upgrade in HI.

    48

    If applicable, request a version entitlement.

    49

    Monitor the upgrade to your instance and validate that the upgrade to your production instance is complete.

    50

    Apply any update sets and post-upgrade fix scripts that you have.

    51

    Validate and test your instance by conducting user acceptance testing (UAT). Verify with all key stakeholders that the system is performing properly after production upgrade, and key functionality is available.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Upgrade planning checklist

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Upgrade planning checklist

      Plan and track the activities related to your ServiceNow instance upgrade. To help ensure that you complete all the tasks for a successful upgrade, follow the step-by-step instructions in the upgrade planning checklist to track and plan the upgrade.

      Some optional steps may not be appropriate depending on the number of instances, customizations, and so forth. Mark the ones you do not need in the N/A column.

      Tip: To download a PDF version of this checklist, click here.

      The process for completing steps for self-hosted customers may vary (for example, requesting an instance clone or upgrades). These differences must be considered during planning.

      Customer name:
      Product instance name: https://[instancename].service-now.com
      Other instance names https://[instancename].service-now.com https://[instancename].service-now.com
      Description Yes No N/A
      Phase 1 - Read the release notes and plan your upgrade
      1

      Review the Quebec release notes for the target ServiceNow feature release and patch, in addition to product and release documentation.

      For Quebec-specific upgrade considerations, see Pre- and post-upgrade tasks for various products.

      Phase 2 - Complete these planning tasks.
      2

      Confirm which ServiceNow instances are in-scope for upgrade.

      3

      Confirm the instance hosting model. For example, ServiceNow cloud, on-premise, or off-premise.

      4

      Based on the Quebec release notes and other release materials, determine new functionality or notable changes that need to be validated after the upgrade.

      5

      Confirm plans to enable or disable features introduced in the new product release.

      6

      Review the Browser support to determine browser prerequisites. For example, versions and types supported, and additional requirements for new UI versions. Compare these supported browsers to your corporate standard and identify any gaps.

      7

      Create a project plan for cloning, upgrading, and testing.

      8

      Identify the core team of testers, power users, and key stakeholders required to validate functionality in the ServiceNow instances before and after the upgrade.

      9

      Confirm whether there are any change freeze windows impacting the timing for environment clones or upgrades. For example, end quarter.

      10 Confirm which of the following situations applies to your ServiceNow non-production instances:
      1. Development and testing can be frozen until the production upgrade is completed.
      2. Continued development (and testing) activities need to continue in a non-production instance while upgrade, remediation, and testing activities are performed in parallel on another instance.
      3. Once the final upgrade to your production instance is complete, the cloning of your final production instance to your non-production instance will wait until after the production upgrade is complete.
      11

      Confirm the availability of other systems required for integration testing (key resources and environments).

      12

      Confirm whether there are any restrictions in which ServiceNow instances can be used for integration testing. For example, an interfacing system is only set up to access a specific ServiceNow test instance.

      13

      Confirm the testing scope and approach.

      14

      Create a comprehensive test plan including test cases for all core instance functionality and integrations.

      15

      Confirm the method for tracking any defects identified during testing.

      16
      Create a high-level implementation plan that covers:
      • the sequence and timing to upgrade non-production and production instances
      • the instances to be cloned
      • the instance to be used for integration testing.
      17

      Confirm whether there are any change freeze windows impacting the timing for environment clones or upgrades. For example, end quarter.

      Responsible: ServiceNow or Customer
      18

      Determine whether existing internal training materials, Knowledge Base articles in the customer instance, or other supporting documentation must be updated to align with the upgraded version. For example, changes in functionality or user interface.

      19 Optional: Schedule the ServiceNow Configuration Review, which provides recommendations to align the customer configurations with ServiceNow best practices.
      Note:

      There may be a service charge and require professional services engagement.

      20
      On your production instance, create a system clone and select your development instance as the Target instance. Notify impacted users and internal stakeholders of the scheduled date/time for cloning (from production) and upgrade of the non-production instance.
      Note:

      It is important to test on a system that reflects the production instance as closely as possible. If your non-production and production instances are the same size, include the production audit log and the attachment data, and ensure that you have deselected the exclude options.

      Phase 3 - Verify your upgrade configurations and schedule the development instance upgrade in HI
      21

      Check the configuration of the Check distribution for possible upgrade scheduled job to view how often and when it runs.

      22

      Verify that the Check distribution for possible upgrade sys_trigger is set properly for upgrading.

      23

      Verify that the Check database for possible upgrade sys_trigger is set properly for upgrading.

      24

      Schedule the upgrade in HI.

      25

      If applicable, request a version entitlement.

      Phase 4 - Upgrade and validate the development instance
      26

      Using the Upgrade Monitor, monitor the upgrade to your instance and validate that the upgrade to your development instance is complete.

      27

      After the upgrade for your development instance is complete, process the skipped records list in the Upgrade Monitor.

      28

      Identify your update sets.

      29

      Before and after upgrading, conduct smoke tests on your development instance. Use your comprehensive test plan to perform functional testing.

      Phase 5 - If applicable: Upgrade and validate your other non-production instances, such as your test instance
      30

      On your production instance, create a system clone and select your development instance as the Target instance.

      31

      Schedule the non-production upgrade in HI and verify your upgrade configurations.

      32

      Validate that the upgrade to your non-production instance is complete.

      33

      Install any optional plugins that were installed on your development instance.

      34

      Install any custom applications and post-upgrade fix scripts that you need.

      35

      Install update sets.

      36

      Perform functional testing and monitor the performance of your instance.

      Phase 6 - Prepare to upgrade the production instance
      37

      Confirm sign-off from IT and Business stakeholders that all non-production instance defects have been fixed and validated in update sets.

      Responsible: Customer
      38

      Confirm the core team of key stakeholders required to validate functionality in the ServiceNow instance after the production upgrade.

      Responsible: Customer
      39

      Confirm coverage for Day 1 support post-upgrade.

      Responsible: Customer
      40

      Create a Production Upgrade Implementation Plan that includes all upgrade steps, roles and responsibilities, communication plans, key contacts, support coverage for Day 1, and so forth.

      Responsible: Customer
      41

      Schedule a walkthrough and sign-off of the Implementation Plan with key stakeholders and the core team.

      Responsible: Customer
      42

      Submit and obtain approvals for change records as required by the organization change process.

      Responsible: Customer
      43

      Send a communication to key stakeholders and end users with details for the production upgrade outage, new features, and so forth.

      Responsible: Customer
      44

      Profile the performance of your instance before upgrading.

      45

      Use the ServiceNow Performance homepage to document the performance of your instance before the upgrade.

      46

      On your clone, perform functional testing and monitor the performance of your instance.

      Phase 7 - Upgrade the production instance
      47

      Schedule the upgrade in HI.

      48

      If applicable, request a version entitlement.

      49

      Monitor the upgrade to your instance and validate that the upgrade to your production instance is complete.

      50

      Apply any update sets and post-upgrade fix scripts that you have.

      51

      Validate and test your instance by conducting user acceptance testing (UAT). Verify with all key stakeholders that the system is performing properly after production upgrade, and key functionality is available.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login