Skip to main content


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

Post Migration Steps

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.

Time Zone Correction

If needed, the data migration team reconciles all time stamps to UTC as required on Pega Cloud.

Data-Only Update

After the data is migrated, Pega performs a data-only update on the data schema migrated from the source environment. In this step, any deltas in the data structures between the source environment are updated to match those required for the Pega Cloud environment. This is done by Pega and requires no effort on your part.

Update Strategic Applications

If required, Pega updates the strategic applications in your environment after the data is migrated. Application specific data structures and rules are updated to match the latest strategic application version.

Import Environment-Specific Application Configurations

Export and import a RAP file as described in Import Environment-Specific Application Configurations

Perform Post-Update Steps

Perform any post-update procedures on the Pega Cloud environment that are required. These were identified as part of your Migration Project Plan and may be required when updating between certain platform versions or using some strategic applications.   For more information, see Version-Specific Update Guides.

Update Custom System Name and PDC URL

The system name is set to the default (“pega”) during migration.  If your source system has any other system name, manually update it on Pega Cloud after the migration.  Also manually update the PDC URL on Pega Cloud after the migration.  Then, restart the system on Pega Cloud.

If the name of your source system is “pega,” you do not need to update either the system name or the PDC URL, and you do not need to re-start the system.

 

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