Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Submit CC for Data Migration

Updated on December 12, 2023

+

This content applies to On-premises, Client-managed cloud and Pega Cloud environments

Attention: This documentation has been moved to the new documentation site:
https://docs.pega.com/bundle/migration-modernization/page/pega-cloud-migration-modernization/migrating-pega-cloud-overview.html
This documentation is no longer being maintained. It is out of date and pending deletion. Please update your bookmarks.

Enter a Cloud Change (CC) ticket for the final data migration into your production Pega Cloud environment, roughly five days before the Go Live date. Create a Task in the ticket that specifies the type of Pega Cloud Migration Activity (OnPrem or Client Cloud), source environment details, the schema, and the list of tables to migrate.

Attach your Cutover Runbook that includes the list of required activities, personnel, and order of operations.  

The Pega Change Advisory Board reviews and approves your Cloud Change request. Pega uses this CC to track the migration of your data from your source production system to your Pega Cloud production environment.

For more information, see Change Management process.

 

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us