Note the product name, current version, and upgrade version for each product that you're upgrading.

Product name Current version Upgrade version
  1. Validate upgrade scope requirements:
    Pre-upgrade task Assignees Completion Date

    Identify the number of deployed environments.

    Identify the number of nodes (admin plus runtime) per deployed environment.

    Read the upgrade guide and release notes for your target upgrade version.


    If you skip versions (for example, if you’re upgrading from version 2.0 to version 5.0) we recommend reviewing the upgrade guides, release notes, and system requirements for versions 3.0 and 4.0, as well as version 5.0, to ensure that your upgrades go smoothly.

    Review the differences between current and target versions. Note any incompatibilities or dependencies.

    Read the tuning guides for your target upgrade version to ensure that you're aware of significant changes and new tuning recommendations, especially when Java versions have been upgraded.

    Review the new JDK defaults and make and relevant changes.

    Collect and review the deployment requirements, use cases, and architecture and design documents.

    Accept the changes and features from the release notes.

    Obtain a new license key for upgraded version.

  2. Identify external services that might be affected by the upgrade:
    External Service Type External Service Name



    Application integrations

  3. Assess upgrade readiness.

    Do you have the team and tools to complete this upgrade successfully? If not, please reach out to your Ping Account Team to discuss resources.