# Upgrading Architecture of every new feature is planned in such a way that existing features work as-is. SailPoint suggests that you always have the latest version, however, upgrading is not mandatory unless called out. Versions can be skipped and can be upgraded to the latest version without going through each individual upgrade. > [!IMPORTANT] > > SailPoint's ServiceNow Service Catalog for Identity Now relies on APl's published by SailPoint for data exchange. SailPoint is sunsetting the SailPoint legacy API gateway (Cloud Commander) and V2 APIs. Consequently, all versions of ServiceNow Catalog v3.0 and earlier are being deprecated. > > To address this, we have launched SailPoint ServiceNow Catalog Version 3.1. It is imperative that all customers upgrade to Version 3.1 before June 28, 2024, regardless of any previous information in the SailPoint support calendar. While there won't be a change in setup required by admins, we recommend exercising caution during the upgrade process to ensure a successful transition. > > Key Dates: > > - End of support for versions V3.0 and earlier: March 31^st, 2024 > - Mandatory Upgrade for business continuity: June 28^th, 2024 > [!IMPORTANT] > > ServiceNow admins must check for skipped items during each upgrade. As with other ServiceNow version upgrades, any object that has been customized (updated after application installation) on your instance for the SailPoint app will also need attention. A customized object is not overwritten by a new component during the upgrade, and is treated as a skipped change. In such cases, each of the entries must be reviewed and appropriate action taken. ## Reviewing Upgrade Information Use the following pages to review the information relevant to your upgrade: - [SailPoint API links]() lists the endpoint links for each supported application version. - [Version Upgrade Considerations]() covers versions 2.3.27 through 5.4.