Skip to main content


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

Clone Source Production Database

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.

It is strongly recommended that you create a clone of your source production database to use for the data migration dry runs.  This ensures that the dry run does not impact your source production application or any of the users of the production application.

 

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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