Skip to main content

Planning for end of Pega Cloud subscription term

Updated on February 16, 2023

This content applies only to Pega Cloud environments

This article is part of the Pega Cloud Subscription Documentation.


As the end of the term of a client's subscription approaches, they have a few options.  Most clients will look to renew their subscription for an additional term, in order to continue to leverage the value of their Pega deployment and potential expanded use to new areas.  Some clients may elect to bring their Pega applications in-house and operate on a client-managed cloud Environment.  In this way, clients can continue to leverage their investment in Pega solutions with an alternate deployment model, should they prefer. 

For other clients who elect not to renew or bring Pega in-house:  upon termination of the Subscription Services, and on the client’s request made within 15 days of the termination date, Pega will return the client’s data persisted to their Pega Cloud production Environment stored in Cloud Data Storage in a common industry-standard format such as a database export, encrypted to customary standards.

After the return of client data, Pega will delete any client data persisted to Pega Cloud.  Pega follows a decommissioning standard operating procedure which relies on automation capabilities available to us from our IaaS providers. The process followed by our public IaaS providers is consistent with NIST 800–88, Guidelines for Media Sanitization.  Pegasystems will notify client when decommissioning occurs via standard communication channels.

Pega does not return data for Legacy Web Chat (formerly Pega Chat), Co-Browse, Workforce Intelligence, Digital Messaging services, or Voice AI.  Upon termination of the Subscription Services, Pega will delete any persisted client data, using industry-recognized methods for secure erasure.

Did you find this content helpful?

100% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us