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
    • Paris release notes
Table of Contents
Choose your release version
    Home Paris Release Notes Paris release notes Prepare your upgrade ServiceNow upgrades

    ServiceNow upgrades

    • 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

    ServiceNow upgrades

    The upgrade process moves your instance to a new ServiceNow release version. Understand the difference between upgrading and patching, release definitions, rollback and backup options, and how to test your non-production and production instance upgrades.

    Before you begin the upgrade process, read the Paris release notes and review the upgrade and migration tasks for your applications and features.

    Prepare, upgrade and test the test instance, upgade and test production instance

    System upgrades can be significant projects. Each ServiceNow feature release includes major additions, and you should always consider the impact of new functionality on an instance. Upgrading implements enhancements to all features that are part of the base system or are already active, unless the feature is customized on your instance. For a list of all available plugins and whether they are active by default on the base system, see List of Paris plugins.

    Careful preparation and knowledge of the available software, tools, and resources can contribute to a successful upgrade. In addition to the materials provided by ServiceNow, it is important to understand how your ServiceNow instance is currently operating and the performance level of key business functionality. Set the expectation with IT and business users that time must be dedicated to preparing for, implementing, and testing ServiceNow upgrades.

    If you have any issues during the upgrade process, contact ServiceNow Technical Support. ServiceNow Technical Support is available 24 hours a day, 7 days a week to assist you with any questions or issues.

    For additional help with upgrades, ServiceNow also offers various Production Readiness Services. These services specifically address challenges with instance upgradability, manageability, scalability, and performance. The reviews are performed by a ServiceNow-certified professional consultant, who provide recommendations to align customer configurations with ServiceNow best practices. Contact your ServiceNow sales representative for more details.

    Upgrade and update durations in Paris

    The upgrade process takes a significantly shorter time for both updates and upgrades. (An update occurs when an instance moves from one patch or hotfix to another within the same release family. An upgrade occurs when an instance moves from one release family to another). As always, test your upgrades, but don't assume from the much faster completion time that the update or upgrade wasn't successful.

    Supported upgrades

    You can upgrade directly to the latest release family. If multiple software versions are involved in your upgrade, be sure to consult the release notes for each version between your current version and the target version. For more information about release terminology and availability phases, see the ServiceNow Release Cycle [KB0547244] article in the HI Knowledge Base.

    Upgrades vs. updates

    ServiceNow organizes its releases into families. A family is a set of releases that are named after a major city, such as Paris. Families also contain patches and hot fixes. For example, the following releases are both part of the Orlando family:

    • Orlando Patch 4
    • Orlando Patch 3 Hot Fix 2

    Upgrading is the act of moving to a release that is in a different family than your current release. For example, a move from London Patch 7 to Orlando Patch 3 is an upgrade because London and Orlando are different families.

    Updating is the act of moving from one patch or hotfix to another within the same release family. For example, a move from Orlando Patch 1 to Orlando Patch 3 is a update because both versions are part of the Orlando family.

    In both cases, the target release is Orlando Patch 3. It is the difference between your current and target release family that determines whether you are upgrading or updating.

    Features, patches, and hot fixes

    Each release family contains features, patches, and hotfixes.

    A feature provides a complete solution that customers can implement to add value to their organization. New features are generally only available as part of a feature release. Features are supported with patches and hot fixes.
    Type Scope
    Feature
    • Introduces new features
    • Includes all available fixes to existing functionality
    • Is production-oriented; quality and stability are of the highest priority throughout the lifecycle
    Patch
    • Supports existing functionality with a collection of problem fixes
    • Generally does not include new features
    Hot Fix
    • Supports existing functionality with a specific problem fix for a feature release
    • May or may not include any previous fixes for a given release
    • Does not include new features

    For more information about release terminology and availability phases, see the ServiceNow Release Cycle [KB0547244] article in the HI Knowledge Base.

    Rollbacks and backups

    When you plan an upgrade, remember that ServiceNow does not provide a universal rollback option. Rollbacks are available for upgrades (for example, Paris patch-to-patch and Paris patch-to-hotfix). The rollback window is 10 days by default. You can customize this window by modifying the glide.rollback.expiration_days property. To request a rollback, contact ServiceNow Technical Support.

    Avoid restoring a production instance from backup, when possible, due to downtime and data loss. When a problem cannot be solved using other methods, restoring a production instance from backup is a final option. ServiceNow can restore an instance to any point in time, regardless of when a backup is completed. ServiceNow Technical Support provides support 24 hours a day, 7 days a week for assistance with critical post-upgrade issues.

    Note: ServiceNow does not perform on-demand backups. Instances are automatically backed up daily during non-peak business hours on schedules defined by ServiceNow. The timing of existing backup schedules is not adjusted.

    Testing throughout upgrades

    Testing is an integral portion that occurs after each instance is upgraded. After you upgrade an instance, test and validate it.

    This instance naming convention assumes that you have three ServiceNow instances. If you have three instances, upgrade your instances in this order:
    1. Development
    2. Test
    3. Production
    If you have more or less than three instances, or if you are using Team Development, these instance labels will be different. In general, upgrade your instances furthest from production towards your production instance.
    Instance Type of testing required
    Development Conduct smoke tests.
    Test
    • Use the ServiceNow Automated Test Framework to assist you in testing your non-production instances.
    • You can use Automated Test Framework quick start tests and product testing suites to help you jump start your testing before and after upgrades. For a list of available tests and activation information, see Quick start tests.
    • For extra testing coverage, you can also conduct user acceptance testing (UAT) on your non-production instances.
    Production Conduct UAT.
    Note: The Automated Test Framework is intended for use on non-production instances. On your production instance, conduct UAT only.

    If you encounter any post-upgrade issues, document the issue's conditions, steps to reproduce the issue, and your customizations. Contact ServiceNow Technical Support to open an incident for each issue, and provide this information accordingly. ServiceNow Technical Support is available 24 hours a day, 7 days a week to assist you with any questions or issues.

    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

      ServiceNow upgrades

      • 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

      ServiceNow upgrades

      The upgrade process moves your instance to a new ServiceNow release version. Understand the difference between upgrading and patching, release definitions, rollback and backup options, and how to test your non-production and production instance upgrades.

      Before you begin the upgrade process, read the Paris release notes and review the upgrade and migration tasks for your applications and features.

      Prepare, upgrade and test the test instance, upgade and test production instance

      System upgrades can be significant projects. Each ServiceNow feature release includes major additions, and you should always consider the impact of new functionality on an instance. Upgrading implements enhancements to all features that are part of the base system or are already active, unless the feature is customized on your instance. For a list of all available plugins and whether they are active by default on the base system, see List of Paris plugins.

      Careful preparation and knowledge of the available software, tools, and resources can contribute to a successful upgrade. In addition to the materials provided by ServiceNow, it is important to understand how your ServiceNow instance is currently operating and the performance level of key business functionality. Set the expectation with IT and business users that time must be dedicated to preparing for, implementing, and testing ServiceNow upgrades.

      If you have any issues during the upgrade process, contact ServiceNow Technical Support. ServiceNow Technical Support is available 24 hours a day, 7 days a week to assist you with any questions or issues.

      For additional help with upgrades, ServiceNow also offers various Production Readiness Services. These services specifically address challenges with instance upgradability, manageability, scalability, and performance. The reviews are performed by a ServiceNow-certified professional consultant, who provide recommendations to align customer configurations with ServiceNow best practices. Contact your ServiceNow sales representative for more details.

      Upgrade and update durations in Paris

      The upgrade process takes a significantly shorter time for both updates and upgrades. (An update occurs when an instance moves from one patch or hotfix to another within the same release family. An upgrade occurs when an instance moves from one release family to another). As always, test your upgrades, but don't assume from the much faster completion time that the update or upgrade wasn't successful.

      Supported upgrades

      You can upgrade directly to the latest release family. If multiple software versions are involved in your upgrade, be sure to consult the release notes for each version between your current version and the target version. For more information about release terminology and availability phases, see the ServiceNow Release Cycle [KB0547244] article in the HI Knowledge Base.

      Upgrades vs. updates

      ServiceNow organizes its releases into families. A family is a set of releases that are named after a major city, such as Paris. Families also contain patches and hot fixes. For example, the following releases are both part of the Orlando family:

      • Orlando Patch 4
      • Orlando Patch 3 Hot Fix 2

      Upgrading is the act of moving to a release that is in a different family than your current release. For example, a move from London Patch 7 to Orlando Patch 3 is an upgrade because London and Orlando are different families.

      Updating is the act of moving from one patch or hotfix to another within the same release family. For example, a move from Orlando Patch 1 to Orlando Patch 3 is a update because both versions are part of the Orlando family.

      In both cases, the target release is Orlando Patch 3. It is the difference between your current and target release family that determines whether you are upgrading or updating.

      Features, patches, and hot fixes

      Each release family contains features, patches, and hotfixes.

      A feature provides a complete solution that customers can implement to add value to their organization. New features are generally only available as part of a feature release. Features are supported with patches and hot fixes.
      Type Scope
      Feature
      • Introduces new features
      • Includes all available fixes to existing functionality
      • Is production-oriented; quality and stability are of the highest priority throughout the lifecycle
      Patch
      • Supports existing functionality with a collection of problem fixes
      • Generally does not include new features
      Hot Fix
      • Supports existing functionality with a specific problem fix for a feature release
      • May or may not include any previous fixes for a given release
      • Does not include new features

      For more information about release terminology and availability phases, see the ServiceNow Release Cycle [KB0547244] article in the HI Knowledge Base.

      Rollbacks and backups

      When you plan an upgrade, remember that ServiceNow does not provide a universal rollback option. Rollbacks are available for upgrades (for example, Paris patch-to-patch and Paris patch-to-hotfix). The rollback window is 10 days by default. You can customize this window by modifying the glide.rollback.expiration_days property. To request a rollback, contact ServiceNow Technical Support.

      Avoid restoring a production instance from backup, when possible, due to downtime and data loss. When a problem cannot be solved using other methods, restoring a production instance from backup is a final option. ServiceNow can restore an instance to any point in time, regardless of when a backup is completed. ServiceNow Technical Support provides support 24 hours a day, 7 days a week for assistance with critical post-upgrade issues.

      Note: ServiceNow does not perform on-demand backups. Instances are automatically backed up daily during non-peak business hours on schedules defined by ServiceNow. The timing of existing backup schedules is not adjusted.

      Testing throughout upgrades

      Testing is an integral portion that occurs after each instance is upgraded. After you upgrade an instance, test and validate it.

      This instance naming convention assumes that you have three ServiceNow instances. If you have three instances, upgrade your instances in this order:
      1. Development
      2. Test
      3. Production
      If you have more or less than three instances, or if you are using Team Development, these instance labels will be different. In general, upgrade your instances furthest from production towards your production instance.
      Instance Type of testing required
      Development Conduct smoke tests.
      Test
      • Use the ServiceNow Automated Test Framework to assist you in testing your non-production instances.
      • You can use Automated Test Framework quick start tests and product testing suites to help you jump start your testing before and after upgrades. For a list of available tests and activation information, see Quick start tests.
      • For extra testing coverage, you can also conduct user acceptance testing (UAT) on your non-production instances.
      Production Conduct UAT.
      Note: The Automated Test Framework is intended for use on non-production instances. On your production instance, conduct UAT only.

      If you encounter any post-upgrade issues, document the issue's conditions, steps to reproduce the issue, and your customizations. Contact ServiceNow Technical Support to open an incident for each issue, and provide this information accordingly. ServiceNow Technical Support is available 24 hours a day, 7 days a week to assist you with any questions or issues.

      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