Other Things to Consider
+
This content applies to On-premises, Client-managed cloud and Pega Cloud environments
Shared Production Databases
If you have multiple applications sharing the same production database, there are additional considerations needed for the Go Live approach. For example, the steps are different depending on whether you have a phased approach or “Big Bang.” Include the appropriate steps in the Migration Project Plan.
These tables are shared between applications running on the same platform:
• PC_ASSIGN_WORKBASKET
• PC_ASSIGN_WORKLIST
• PC_DATA_UNIQUEID
• PC_DATA_WORKATTACH
• PC_HISTORY_WORK
• PC_INDEX_WORKPARTY
• PC_LINK_ATTACHMENT
• PC_LINK_FOLDER
• PC_WORK_SOCIAL
• PR_ASSIGN
• PR_DATA
• PR_DATA_FILE
• PR_HISTORY
• PR_INDEX_ASSIGNMENTDEPS
• PR_INDEX_ASSIGNMENTSKILLS
• PR_INDEX_EMAIL
• PR_INDEX_OPERATORSKILLS
• PR_OPERATORS
• PR_OTHER
• PR_SYS_QUEUE_SLA
• PR_SYS_QUEUES
If you plan to move multiple applications in a phased approach, include steps in the project plan to verify that the data in these tables is mapped to the correct applications.
PegaMarketing/CDH
If you are migrating Pega Marketing or Customer Decision Hub, see Appendix: Migrating Pega Marketing/CDH.
Time Zone Correction
If timestamps in the source database reference a time zone other than UTC, they need to be corrected to UTC as part of the data migration process. The correction must be made for each dataset that is migrated. Include this as a step in the Migration Project Plan, so that the Pega team takes care of it.
Your applications might also have issues with timezone conversion, for more information see the Integrations Involving Date and Time heading in Remediations for Migrating to Pega Cloud.
Previous topic Remediations for Pega Cloud Compliance Next topic Preparing to Migrate your Data