ServiceNow CPG and Cloud Services Catalog replacement

Yes, it is on the way out. ServiceNow's Cloud Provisioning and Governance documentation states: starting with the Brazil release, Cloud Provisioning and Governance is being prepared for future deprecation; it will be hidden and no longer installed on new instances but will continue to be supported. The Deprecation Process article KB0867184 in Now Support has the detail, and the Cloud Services Catalog applications that grew out of CPG are part of the same product line. The CIS-CPG certification and courses were retired in June 2025. Treat it as a product with a finite runway and plan the move while you have time to do it properly.

Cloud Management (CMP) was renamed Cloud Provisioning and Governance (CPG) in the Paris release. CPG was then being reshaped into Cloud Services Catalog (CSC), with the legacy CPG workflows deprecated in Zurich. ITOM Cloud Accelerate is the subscription they are sold under, not a product you build on. If you run any of them, the deprecation applies to you.

For governance and billing, ServiceNow points to the Cloud Governance Suite, Cloud Account Management and Cloud Insights Billing. For discovery, pattern-based cloud discovery replaces the Cloud API. For the provisioning engine itself there is no like-for-like ServiceNow successor, which is why customers look at OneCloud, HashiCorp's catalog for Terraform, a cloud management platform in front of ServiceNow, or a custom scoped application.

OneCloud is our ServiceNow Store application for ordering and governing cloud infrastructure from Employee Center, with your Terraform doing the build and every resource recorded in the CMDB. It does not call CPG, Cloud Services Catalog or the Cloud API at run time. IMGO was our earlier Store offering, built as an implementation on top of CPG. OneCloud replaces it, and IMGO and CPG customers can move with the importer.

It uses them when you have them. OneCloud reads the platform's own cloud service accounts and discovered datacenters, and after a build it runs a targeted discovery so the resources it created become discovered, reconciled CIs. It works without Discovery, writing resources to the CMDB itself through IRE. If you want provisioned resources discovered and kept in step by ServiceNow, ITOM Visibility is the dependency.

Yes. That is the design principle. Templates run as they are, through OneCloud's runners or through one generic wrapper pipeline in your existing Azure DevOps, GitHub or GitLab setup. Day 2 operations that already run as pipelines keep running; only the trigger changes.

It is a good fit if you run HCP Terraform or Terraform Enterprise and want ServiceNow as a front door to workspaces. Approvals, change, CMDB reconciliation, leases, drift checks and Day 2 actions then sit outside it unless you build them. OneCloud keeps all of that in ServiceNow and supports Terraform CLI or OpenTofu on a MID Server as well as HCP Terraform and Terraform Enterprise. We will tell you if the HashiCorp catalog is the better answer for your estate.

The assessment is two weeks. A three-provider estate behind a mature portal takes about four months in eight sprints to replace the provisioning core, with one production switch per provider. Discovery migration, legacy retirement and historical data migration are separate pieces with their own owners and are priced separately.

No. Requests, orders and stacks stay as read-only records in the old tables. New requests create records only in the new application, and a service built under CPG is adopted the first time someone runs a Day 2 operation on it. Confirm with ServiceNow that the CPG tables stay on the instance after end of support, and have the historical migration costed as an option.