Post Migration Steps
This content applies to On-premises, Client-managed cloud and Pega Cloud environments
Time Zone Correction
If needed, the data migration team reconciles all time stamps to UTC as required on Pega Cloud.
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.
Previous topic Data Migration – Production Dry Run Next topic Validate Production Application